Using the Facebook 2.0 plugin

4
  • 18 favourites

Index

Stats

10,793 visits, 24,713 views

Tools

Translations

This tutorial hasn't been translated.

License

This tutorial is licensed under CC BY 4.0. Please refer to the license text if you wish to reuse, share or remix the content contained within this tutorial.

Facebook Developer Application Settings

Let's take a little more in depth look at your newly created Facebook developer app account. Open up the newly created account and you will see a menu on the left. I'll go over the menu items one at a time. So if a spot isn't covered, come back again in a ay or two. Better yet subscribe to my tutorial. :)

Dashboard

The dashboard shows you the app id and if you click show, the app secret. The app id and in specific circumstances the app secret will be routinely used by your app so keep them in a handy spot. Do not share your app secret with anyone, doing so will cause your application to be less secure. Finally, you can review some stat's on your application via the dashboard.

Settings

Here you can also find the app id and app secret. The Display name should be the human readable title for your application. namespace will be used when accessing your app via the Facebook canvas ie apps.facebook.com/yournamehere.app domains should be the domains you can access your app on. Please note that you can set this field and the url fields to localhost for testing your app via Construct 2 preview over localhost. Contact email is just the email where Facebook users can contact you regarding this application. The last section under basic is Add platform. This is where you would add your IOS apps and Facebook canvas app details........ It flows basically the same as the first section of this tutorial so I will not cover it twice.

Advanced Settings

A quick rundown of each of these options:

Native or desktop: Leave this set to no unless you know what you know what this means.

Deauthorize callback: You really should be setting this. Anytime a user removes your application they will visit this website url. This should be used to list reasons a player should re-install your app.

App restrictions: Does your app cater to young children? You can restrict your allowed audience here. If possible, create an app for everyone to maximize your user base.

White list and notification options: If you are unsure at all, leave these spots blank. For your reading enjoyment however visit developers.facebook.com/docs/ApplicationSecurity

Client token and yes/no boxes: Unless you know what these mean, leave them alone. For a better understanding visit the link just above this text.

User ID sharing and Advertising Account: Unless you have an actual registered business account on Facebook you will not use these features.

Last two boxes: Set to yes by default. Leave them set to yes and follow the links next to the boxes to read more about those great features.

Migration

Stream Post security: If you will post links to sites other than your own site, leave this set to no.

Enhanced Auth Dialog: Leave this set to Yes unless you have a very specific need for this to be no and know what you are doing.

Decouple app installation for realtime updates from page tab app installation: This is very specific and unless you understand what it is saying, leave this set to no.

  • 0 Comments

  • Order by
Want to leave a comment? Login or Register an account!