I'm trying to set up an iOS 6.0 and up app on Facebook developers, everything's hooked up and working fine using the latest SDK. The problem is that, though authentication works fine, later in the app it's requesting post permissions and when a Facebook account is not a member of the Facebook app in the Dev center, these permissions aren't requested, the screen just pops to Facebook and back to the app again without doing anything. When I try to use the app with my account that is an admin on Facebook Dev, then it works.
The posting action in question is a Facebook Graph post and it works fine for the admin account.
In previous apps I haven't requested publish permissions through the Facebook developer portal in the app settings (you know, the app review bit by Facebook), so that can't be it either. Those apps work with accounts that are not a member.
I know the code is fine, the code is re-used from previous apps.
I think it's because I am unable to enter the proper Facebook app ID in the Settings. Could that be the cause? Though the app ID is in iTunes Connect, Facebook can't find it yet because the app in review at Apple.
Any thoughts on this nightmarish user rights issue?
Since API v2 was introduced, with every new app you need to go through review for any permission apart from the three “basic” ones (those are public_profile, email and user_friends) – see https://developers.facebook.com/docs/facebook-login/permissions/v2.1
Otherwise you will only be able to ask users that have a role in the app (admin/developer/tester) for permissions – that is helpful either during testing, or for an app that is for a limited user base only; f.e. if you want your app to publish updates from your website to your Facebook page, which requires manage_pages – in such a case you should not submit for review, but just use that permission with your admin/developer/tester account associated with the app. That is further explained here – https://developers.facebook.com/docs/apps/faq#apps-all-users-are-developers
Related
Now I'm developing an APP that uses Bluetooth functions on iOS/Android.
It's not published yet since it is under development.
As you may know, the simulator on iOS doesn't have the Bluetooth module.
However, Facebook requires us to submit the APP that can be launched on the simulator to authorize the Facebook login API.
I guess that is the reason why Facebook login API was working but now it's returning the error.
The beta test for the APP is planned, but I don't know how to get this API authorized by Facebook for the closed beta test.
I asked this on the Facebook forum, but got no reply there, so am asking here as well.
Any comments will be welcome (ex: I have to write down about xxx).
Best
Facebook can review and revoke your public app permission and suddenly require an iOS store ID. This means you will need to use approved test user accounts to login, that have been authorised in the Facebook developer console, until your app is published on the AppStore.
You can add test users two ways in the Facebook Developer console (select your app first):
Roles -> Roles - Add your own Facebook account to the approved testers.
Roles -> Test Users - Create fake test accounts for the purpose.
Hi I'm developing an iOS app where I'm using Facebook login integration.From facebook i want to get user birthday for that i need to submit my app to facebook but my app is still at starting stage can I submit my app in development stage to get details or is there any other way to get details from facebook in development?
In your Facebook developer dashboard, go to the roles section for your app. You will have to set roles for user to be able to access your app while its still under development. You can add roles as "Testers", "Developer" or "Administrator" and all these users will have access to your app while its still under Development and hasn't been approved by Facebook.
Edit:
From the facebook requirements page-
We ask that you provide test users with your app submission so that we
have the necessary credentials to test and access your app. This way,
our review experience is equivalent to your app's experience.
For further information regarding facebook acceptance criteria and their processes, checkout this link
Edit:
If you want just the basic information, you can open your app dashboard on Facebook. You will see App Review button. Click on it and it will show a page where there will be an option to make the app public. Turning it on will allow other users to use your app without you having to submit it to Facebook. This however allows you limited integrations from Facebook. From the docs:
If your app asks for more than public_profile, email and user_friends,
Facebook must review it before you release it. Learn more about the
review process and what's required to pass review.
I am in the last stages of creating a new iOS app which uses Facebook login api. The Facebook app I created for that (in Facebook itself), is not yet approved by Facebook since they are demanding to provide them with the Apple App ID (which currently does not exist as my future app is yet to be submitted to Apple). At this point, I am able login using Facebook inside my iOS app, however, I am wondering if other people will be able to do so once my iOS app will be approved by Apple (while it's not yet approved by Facebook)...
I already got my app id in the itunes connect but Facebook requires active app id which I cannot provide at the moment.
However, I got my answer, as long as the basic permissions part is approved by Facebook, the login process will work just fine. Thanks!
my iOS app uses the Facebook SDK and users can interact with my iOS app via Facebook. EX. Send friends scores, invites etc etc
I made a new app within the Facebook Developer page, hooked everything up and it works just fine. I turned off sandbox mode within Facebook and I submitted my app the other day to Apple. Today, I noticed there is also a submit app for Facebook.
Am I required to have Facebook approve my iOS app in order to use Facebook services in my iOS app or is this only if I want my iOS app to show up in Facebook App Center?
Thanks!
When you registered your app to facebook.
Facebook provide only three permisson , these permission is by default approved
email
Provides access to the person's primary email address. This permission is approved by default.
public_profile
Provides access to a person's basic information, including first name, last name, profile picture, gender and age range. This permission is approved by default.
user_friends
Provides access to a person's list of friends that also use your app. This permission is approved by default.
If you want to use more feature apart from them , then you need to submit your app to facebook for use other feature
like if want to get user photo then you have to submit your app for get user_photo permission
facebook check that how you are using user_photo in your app
And you also need to upload screen shot with submission that show you are using facebook photo
To submit an app using Facebook services, even the integrated Facebook system account you don't need to do anything special, only apple has to approve your app, off course Facebook has their rules, and if you don't respect them, they can decide to turn off some services that your app doesn't respect
So I've searched for this topic a lot and may be over complicating things but would love some clarity on it. So here's the issue.
I have a web app that uses Facebook Graph (FB Login, friends invite, sharing through FB, etc). We've just built an iOS app for the website and now want to implement all the above FB actions on the iOS app as well. I looked up the Facebook documentation and have tried using that to getting just the Facebook login to work for a user that's already registered on our website (and has their Facebook account connected as well) but it doesn't seem to work.
Use case - A user registers on the web app and connects their FB account with us. They then download the iOS app and want to use FB login to login to the iOS app or share objects on their timeline. A vice versa case should also apply.
Question - What should be the workflow between the ios App, web Server and Facebook for the use case above? Basically, how is the token and the secret passed so all three know we're talking about the same user and same FB account?
Any links or advice would be highly appreciated! Thanks!
In the case when a facebook authed webapp user first starts the native app, you won't know who they are. So they need to be prompted with a "login with facebook" button. When they hit that button, the facebook-ios-sdk will figure out who the logged in user is and then check if that user has already granted your application access. If the web app and the native app both point to the same facebook app, then the facebook-ios-sdk will simply store the authed access token, and you'll have access to everything your web app does on the native app.
The key here is that your web app and native app must point to the same facebook app (ie. same app id in developers.facebook.com). If it didn't, then the native app user would be re-prompted to grant permissions when they click the "login with facebook" button. Additionally, it's important that the user is logged into the same facebook account on the web app (which is based on cookies in the browser) and on the phone itself. The facebook-ios-sdk uses a couple of different ways to look for the active facebook account on the phone. It tries the iOS 5+ system facebook account, inter-app calls to facebook's own native app, the browser cookie for the web view instance running in your app, or bounce you out to safari and use the browser cookie in safari. Which ever one comes back first saying they have an active facebook account needs to have found the same facebook account as the one on the web app. In most cases, they will match up because most users only have a single facebook account and are logged in everywhere with the same account, but they certainly can be different. In the off chance that the web app facebook user is not the same as the native app active facebook user as detected by facebook-ios-sdk, then the "login with facebook" button will simply prompt the native app active facebook user to log in and grant permissions.
Once the access token has been granted to the native app, you can send it back to the server, find the associated facebook user id, and now the web app user and the native app user can be linked to be the same person operating both apps. Additionally, any graph api calls you want to make on the server can be made on behalf of the user using the up-to-date access token you just got from the native app. Any sharing/posting/api calls made directly in the native app through the facebook-ios-sdk will be done as this user and will be handled by the sdk (ie. you won't need to worry about it... it should just work seamlessly and integrate all posts to their timeline just like the web app's graph apis can).
In the case where you have a facebook authed native app user going to the web app, you also won't know (on the first request) who this user is. You can present them with a facebook js sdk login and, again, once the same facebook user logs in, you can associate this current web app user as the one who was on the native app earlier.
Specifically addressing your question, you really have no way of knowing who a migrating user is on either the web app or the native app when they first come to the app. That's where the "login with facebook" comes in. Assuming the user is logged into the same account on the browser as well as on their phone (as determined by the facebook-ios-sdk), then the process of logging into your app is seamless. They won't be prompted to grant permissions a second time (unless your permissions set is different between the web app and the native app) and you'll be given the user's access token immediately. The role of the server is to reconcile the two users by using the granted access token. With the access token, the server can make a simple call to the graph api and get the user's facebook user id. Using that facebook user id, you'll be able to match up the "true" identities of the users on your apps (ie. you now know that the web app user and the native app user are one and the same). Once you know who the user is, you'll be able to provide a personalized experience to that user, based on his identity, regardless of whether he's using your web app or your native app.
Hope this helps. Happy to answer more questions that you may have.