[FIXED] Changing app id for Facebook login. Downsides?

Issue

I'm working to fix the Facebook login for a website.

Apparently the login doesn't work anymore because the Facebook app is not configured correctly. Now, I'm having a hard time to get access to said Facebook app from the previous developers and I am considering my options.

Could there be troubles if I create a new Facebook application with a brand new app id? For sure users will need to grant access again but that should not be a major issue. Could there be other downsides?

Solution

There are a few downsides to changing the App ID, especially if the app was created a while ago. However, it's important to have control of your application, so these are just for reference:

1. User IDs between old app and new app will be different (this is related to app_scoped User IDs, with newly registered Facebook apps)
2. Permissions will need to be reviewed by Facebook again
3. You will lose access to Graph API v1.0 if your app was created before April 30th 2014 (but this will be depreciated in April 2015).
4. You will need to get your App Center listing approved again

Having made the above points, it's important to have control of the application. If you're not using a lot of extra permissions its recommended that you create a new App ID and update your application. If you have an existing database of users, their IDs will no longer correlate to the same user, so it's also best to start with a fresh Database, or find a way to migrate the data to the new User ID by matching Email addresses.

Answered By - Niraj Shah