Mover of the moment:

Now online:

1stMovers on Twitter

AutoTweet Community 4ik has updated user data - more...
AutoTweet Community Angola has updated user data - more...
AutoTweet Community promocjaaygge has updated user data - more...

Create PDF Email Print

Tips and Tricks for using AutoTweet with your own Facebook App

Hits:
3193
Rating:
 
Vote for this:
Good - Bad

Answer

Update 2012-01-27: Update for new setting with offline access.

Creating your own app on Facebook and get it work with AutoTweet needs deep knowledge in Facebook app handling and many users have problems with the setup for the app. This FAQ shows the needed settings. Please read also the chapter "Use your own App/API with AutoTweet" in the AutoTweet documentation.

First of all: If you have no idea what a Facebook App is or if you need some basic information about Apps, please visit the FacebookDEVELOPERS site.

 

When your app is created and all settings are done, the main page of your app should look like this:

 

On this page you will find all the information you need to configure a channel in AutoTweet NG backend for use of your own app. Please copy the App ID/API Key, the App secret and the Canvas Page to the corresponding fields in AutoTweet NG backend channel dialog and enable the own app feature. For the Canvas Page "https" is mandatory so take care that the URL does start wie https and not http. As showed in the image the Canvas Page URL is using the symbolic name of your app and NOT the app id or something else. Also do not forget to copy the ending "/" with the URL. In the image example the correct Canvas Page URL is "https://apps.facebook.com/moversnewownapp/". In your case "moversnewownapp" is replaced by the name of your own app.

Now we will have a more detailed look at the settings: Click on "Edit or Create" (depends on if you will edit an existing app or create a new one) on the right site of your apps main page and go to the tab "Settings / Basic". The following two images are showing examples for the data you have to enter as basic settings:

 

First make sure that you enter an App Namespace. The App Namespace is the unique name for you App in Facebook and it is also used for your Canvas Page URL. In the example the name of the App is "moversnewownapp". You must choose your own name.

Next you have to enter a site URL. You must set this URL to "http://www.1st-movers.com/" (If not, Facebook does not allow redirections to 1st-movers.com what is needed within the authorization process). Finally you have to enter the Canvas ("http://www.1st-movers.com/facebook/autotweetnewapi/") and Secure Canvas URL ("https://www.1st-movers.com/facebook/autotweetnewapi/") as showed in the image. Do not forget the ending "/":

 

 

Now go to the tab "Settings / Advanced" and make it look like this:

You should enable everything under "Migrations" except the option "Stream post URL security" and "deprecate offline_access".

 

If you use an older app with AutoTweet, the options under "Migrations" may vary and you have to enable some more options like the iFrame parameter. The following two images shows some other possible options:

 

That's all! - Now your app should work and you can start the authorization process as described in the AutoTweet documentation.

Note 1: Do not forget to enter the App-ID and the App-Secret in AutoTweet backend for each channel you will use with this app (See the AutoTweet documentation for more information about AutoTweet channel configuration and setup).

Note 2: Facebook tokens for each app are different. So you have to reauthorize your channel(s) also when you have used another app before! Also Facebook does sometimes invalidate the tokens (e. g. when you have changed your password). In these cases you have to reauthorize the app and copy the new tokens...

Note 3: Sometimes the Facebook canvas page is "looping" after logging in when you do the Facebook authorization. In most of these cases you have entered a wrong "Facebook canvas url" in AutoTweet backend channel dialog. So please check the app data in AutoTweet backend. Especially you should check the prefix of the url: "https" is correct and NOT "http" (Facebook does no longer accept non SSL connections for authorization).