Welcome to Geeklog Thursday, October 18 2018 @ 01:46 am EDT

Geeklog Forums

Facebook App Review


Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/05
Posts: 1308
It looks like Facebook is sending out Developer App Review email Notifications. If you have the OAuth Login Facebook method setup for your Geeklog site you can probably expect this notification soon if you have not got it already.


App Review required by August 1, 2018 to retain existing permissions and features

The Facebook App Review process and API permissions model have been updated. Learn More.

In order to maintain your current API access, your app will need to be submitted for review by August 1, 2018. If your app is not submitted for review, you will lose access to these permissions and features.

• user_friends
• user_link
• user_gender
• user_age_range

The Facebook Platform APIs have been updated with these changes. Please review the FAQ to ensure you request the correct permissions and features with your app review submission.

If access to the permissions and features is approved, the app may need to be associated to a verified business to complete App Review.


Once I go through the process and confirm what permissions Geeklog requires I will post the results to this topic.

One of the Geeklog Core Developers.

Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/05
Posts: 1308
I've started looking into the process and see that for Geeklog Facebook Oauth Apps, you will most likely need to request the follow permissions for the review:

user_link - Provides access to the Facebook profile URL for another user of the app.

user_location - Provides access to a person's current city through the location field on the User object. The current city is set by a person on their Profile.

All other fields we use are considered default fields and do not require special permissions.

For some reason when we request this information when creating an account from a Facebook profile we also request the user_friends. We don not need this so our oauth class needs to be updated (along with a few other small issues) to reflect this. Here is the issue in github:

https://github.com/Geeklog-Core/geeklog/issues/881

If you don't go through with the review in time I am not sure what happens. Hopefully the app continues to work but the information that requires permissions will bot be passed. If that is the case Geeklog's Oauth Facebook login will continue to work, the Geeklog profiles will just be created with less information.

One of the Geeklog Core Developers.

Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/05
Posts: 1308
Well on July 31 Geeklog.net was approved for user_link but not for user_location Facebook permissions. I clearly stated in the screencast how it would be used but it was not approved. Here is what Facebook said:

This permission is not required for your app's intended function, or it doesn't appear to enhance the user experience. Please review this reference for more details about all different permissions, including common and invalid use cases.


There is a lot of confusion at the moment around the Facebook App review process so I am going to leave this for now. It also appears that a lot of the approval process is up to the individual Facebook reviewer as my other Geeklog site was not approved for either permission even though it was pretty much the exact same screencast. If you search the net you will find other webmasters with similar problems.

So for now the Geeklog OAuth Facebook login will continue to work with out extra permissions. All that will happen is the location will not be filled in. Currently Geeklog does to create a link to the Facebook profile but it does not work at the moment so I am not sure if we are grabing the right field. Clicking on the Facebook link we get will give you the following message on Facebook:

Sorry, this content isn't available right now
The link you followed may have expired, or the page may only be visible to an audience you're not in.


I will have to look into user_link and user_location to make sure all is okay for the next version of Geeklog since for some reason we get the above error message.
One of the Geeklog Core Developers.

All times are EDT. The time is now 01:46 am.

  • Normal Topic
  • Sticky Topic
  • Locked Topic
  • New Post
  • Sticky Topic W/ New Post
  • Locked Topic W/ New Post
  •  View Anonymous Posts
  •  Able to post
  •  Filtered HTML Allowed
  •  Censored Content