App conflict with joocial

I have an app conflict beteen jfb connect and joocial. Can you please advise how to solve this issue.

Here is the response from joocial.

Many thanks!

We have found an internal error in your site caused by multiple App Ids in the page. Specifically, JFBConnect's App id.

Joocial and JFBConnect work with Facebook SDK. Facebook SDK is designed to work with an App Id.

If both App Ids are initiallized in the same page, then the first App Id "wins". In the following authization steps, Joocial executes the operations based in its own App Id and finds the error "The access token does not belong to application".

To solve the case:

You could implement the same App Id to all extensions
You could separate the App Ids included in each page. Joocial only initializes FB SDK in the authorization page. JFBConnect should not be loaded in this Joocial page (however JFBConnect is a system plugin loaded in all page before anything else).
In both solutions, we recommend to ask to JFBConnect support for their advice.

I have no used the same app, It seems to be working now, but getting 0 - Invalid appsecret_proof provided in the API argument.

I was using separate apps, because I did not want to mess up the JFB connect and thought different aps would keep things separate.

Many thanks for your response

I was able to resolve the issue by removing the actions from JFB, but now when a member tries to post to JS they are getting, the user hasn't authorized the application to perform this action type oauthexception code 200.

Any ideas?
Thank you
Colin