Existing Facebook API permissions not working - ios

As of last Saturday we started having problems with our Facebook API permissions on an existing app, which allows the user to upload photos taken through our app to their personal Facebook pages. A message appeared on the Login permissions screen that said our app may break after April 30, 2015, and that some permissions below have not been approved for use by Facebook. But it still allowed the user to post a photo to their page. However the next time someone logged into Facebook to upload a photo [taken through our app] the login screen said 'This does not let the app post to Facebook', and the photo did not appear. Since then we have also had the odd instance where another screen appears, which says the app will break after April 30, 2015 but it does not let the photo upload. We are in the process of updating the code for the updated FB API permissions, however as this takes time, we would appreciate any assistance anyone can offer to help us get our current permissions working again in the interim. Can anyone help?

if you are using the api v1.0 it will available until April 30, 2015 .. https://developers.facebook.com/docs/apps/changelog
My advice to you is to update your app and use and read the latest version of facebook api because there are lot of changes.

Related

After review, we still get "sign in with google temporarily disabled for this app"

We have a mobile app and our users got a
"sign in with google temporarily disabled for this app"
When they tried to login their YouTube account with iOS (There's no problem with Android devices).
We submitted a verification request long time ago, and we got from YouTube an email (May 26th 2020),(May 26th 2020):
"Hi Adam,
Thanks for working with us on the YouTube API Services compliance review. We have completed your review and do not require any further actions from you at this time.
We may reach out again to re-review your API Client for compliance with YouTube API Services Terms and Policies.
We appreciate your time working with us on this and please continue to comply with the YouTube API Services Terms and Policies."
Since then, nothing had changed and our app hasn't been verified yet, and our users can't connect with their youtube accounts.
What can we do? We are just waiting and we don't even know how to contact YouTube and ask about our specific case/project.
Thanks you,
Adam.
sign in with google temporarily disabled for this app
Means that your application has not been verified by google. You need to go through the verification process.
You can use a project for development without verification. However there are some limitations (more information here). Basically, you have now reached the limit of 100 users accessing the application.
If you still havent heard anything from google after they say they have verified your application I think the only thing you can do is to submit it again and double check that you are using a client that was created under the project that you requested verification for there's really nothing else you can do.

Graph API not returning all tagged in photos

So when I query the graph api with this
GET /v2.5/me/photos
It only returns 9 of my tagged in photos. All of them but one have been uploaded by me. On my Facebook account I have many more photos in which I am tagged. This test was done in the Graph API Explorer with a user_photos permission token.
The primary place that I am using this is in my iOS app using the FB iOS SDK. This used to work as expected, returning all my tagged in photos. However something changed when I upgraded to the FB iOS SDK version 4. I have a feeling that doing this may have bumped up my apps minimum graph api version in my apps dashboard. And now I am in this position where I can't retrieve all my tagged in photos. My app has been approved for user_photos permission.
Any help would be greatly appreciated!
Thanks to #Vizllx for providing a link to another answer that enabled me to work it out.
The linked answer suggests using an additional user permission. This permission didn't have an effect however this lead me to try turning on and accepting all permissions which worked! I then disabled them all again and went through and figured out which had the effect. Turns out it was the user_friends permission!
So to get a tagged in photo that was NOT uploaded by the user you are querying, there are two conditions:
the user you are querying has to have accepted the user_friends permission
their friend who owns the photo in which the user is tagged has to also have accepted the user_photos & user_friends permission
Therefore their friend also has to be using your app too :/
P.S as for the "All of them but one have been uploaded by me" photo in the original test, this new information does not account for it. I don't know why it was returned but it could have been a bug. Who knows?

What will happen with my app if I not get permission from FB to use "publish permissions"

I have a iOS application with more that 20k users. All current app versions are asking for publish permissions from user, but I never used it.
I'm already working on new version without this permissions, but I wonder what will happen with my app after April 30, 2015 without FB review? I don't have to go thru it if I'll remove publish permission from my app.
User can be still able to log in using facebook?
Mariusz
What will happen after April 30th, 2015 is that the login dialog won't show this permission anymore to people who are not in the roles tab of your Facebook Application Dashboard Settings (meaning the general public).
If you are 100% sure you are not using this permission, you should be good to go. It is great you're already creating a version with this stripped. Remember to remove it from your Facebook Application Dashboard Settings as well.
If for some reason, you are using this permission (Any Graph API or Facebook Dialog to publish), your Facebook Integration will be broken.
More information can be found here:
https://developers.facebook.com/docs/apps/review/login#pre-f8-apps

Post on friend's wall from october 2013 onwards

I am developing an iOS and android app in which I have to give a functionality to user so as he can post on my App's wall from their account. I have found in Facebook developers forum that this functionality has been removed.
Can anyone please suggest me how to achieve the same anyhow.
Please provide a link if possible.
Thanks In Advance :)
Apps don't have a 'wall' since February of 2013 or so - your app can have a Page, but there's nothing special about that page or how users can write posts on the page's timeline via the API - it's just the normal documentation for posting to /<page>/feed on behalf of your app's users

FBLoginButton not requesting permissions

Firstly, apologies for the vague question!
At short notice I've been handed an app which has started failing when posting Facebook status updates. It seems to be using a very old version of the Facebook SDK so none of the code examples I have found work.
The error message when trying to post implies that facebook.users.setStatus endpoint is deprecated.
Accordingly, I updated the code to call facebook.stream.publish which seems to be the currently supported.
This results in a permissions error (code 200).
I then changed the Facebook app record to request the publish_actions permission. This looks good on the Facebook preview page:
...but doesn't seem to be reflected onthe in-app Facebook logon screen:
http://s13.postimage.org/d5sf8j0zr/i_Phone_No_Permissions_Request_Redact.png
I have waited several hours now so I don't think the problem is Facebook propogating the
app settings. Can anyone tell me if I'm on the right track here?
Plan B would be rewrite Facebook access using latest Facebook SDK, but this will require an upgrade for XCode and Mac OS, which I'm keen to avoid.
The publish_actions permission is used when dealing with Open Graph actions. From what I've read you'll need the extended publish_stream permission.

Resources