I manage a few Meteor-based apps that use the Facebook login functionality provided through accounts-facebook.
For one app, a week ago, Facebook emailed me saying this app was in violation of their Platform Policy, and that I had to respond to the email to prevent logins from being shut down within a week. Specifically this was the offensive clause:
Platform Policy 8.2: Native iOS and Android apps that implement
Facebook Login must use our official SDKs for Login.
I immediately responded, but (of course?) got no response from Facebook. And, yesterday, I got another email saying Facebook logins have been blocked for this app.
I updated to the latest version of accounts-facebook, appealed the block, and got a response:
We have reviewed your iOS and Android apps and they are still in
violation of the Platform Policy 8.2: Native iOS and Android apps that
implement Facebook Login must use our official SDKs for Login.
So, does this mean that all Meteor apps can get their Facebook login restricted at any time?
How to resolve this?
Today, Facebook went further, telling me that:
Your app has been restricted for creating a negative user experience
that is in violation of our Platform Policies.
Your app cannot be installed by new users.
What are they smoking?
But, whatever they are smoking, how do I resolve this?
I've sent them an email, twice, explaining that, like tens of thousands of others, I'm using the off-the-shelf Meteor package for allowing Facebook logins to my Meteor app. But, all I get back are canned responses that don't respond to my bafflement.
Related
We have a multiplatform service and we give our users a 30 day trial. A user can sign up on iOS, use the web version and finally do the payment on Android... even if it's weird, its a possible. The database is shared between all platforms
We are using Facebook Ads to generate App installs but we don't know how to do the conversions' attribution properly. The main problem is that if, for example, a user install the app from a Facebook app but he end up paying from the web version we lost track that the origin of this user was the ad.
I would like to know if it's possible to determine using the Facebook SDK, on the first run of the app, if the user comes from a Facebook Ad and in that case I would store that information in our database to do the attribution once the purshase is done. Any ideas?
Many thanks in advance!
Regards!
According to this: https://developers.facebook.com/docs/apps/changelog
All new apps after April 30,2014 now require approval to use publish_actions. I have a desktop application that posts to user's facebook walls. The users used to be able to create their own apps buy simply naming it, adding their contact email, setting it to a desktop app and taking it out of sandbox mode. Now, it seems they will need to submit their apps for approval in order to post. The problem is the approval submission requires a platform selection. The FB app doesn't use any of the platforms listed. It's not a mobile app and it's not a website. The app is merely a way for desktop users to post to their wall once they log in. So what needs to be done in order to get new apps approved for this?
Here you go https://developers.facebook.com/docs/apps/review?locale=en_GB
Desktop apps should submit a Web platform and include detailed screenshots or a screencast of the integration.
I have the same issue as described here: Corona facebook.logout() when the Official Facebook app is installed on device
The answer says that this is by design, but lot's of apps allow you to logout of Facebook and log back in as another user. Any idea why facebook.logout() doesn't do what the function implies it should do?
As a user of the Facebook native app, I would be highly agitated if another app I ran logged me out. I've been working with someone in the Corona forums asking the same question (Perhaps it's your post) who's building a Kiosk app, so I can see a need in that circumstance to want this feature. But given that mobile devices are highly tied to individuals, this is not a behavior that most people would want to see.
The Corona SDK facebook.logout()'s purpose is to disconnect the Corona SDK app from Facebook, cancelling the access Token. It was never intended to terminate the facebook app's user login.
In some iPhone 5 devices we have an error when trying to call Facebook login:
The error is:
"the facebook server could not fulfill this access request invalid application id"
I many times checked that application id is specified correctly.
Strange, that on other devices same app is working correctly.
Please, could you help, what the reason of that?
All developers of a particular app, should be known to Facebook. While the application is in Sandbox mode (i.e. developer only access), all every user who want to use the Facebook platform, for testing/developing the application, will have to be added as a developer (as shown below) -
Just goto https://developers.facebook.com/apps/, and add the user, in the list of developers/admins.
More than likely the app is "sandboxed", so only developers have access. If this is the case you'll have to use a developer account on the iPhone.
Go to iOS settings > Facebook
Log out with your "personal" account
Log in with the developer account (to be safe us the dev account that you created the app with)
This worked for me.
I faced this problem. For me the issue was that I hadn't added the iOS platform for the app. Go to the Facebook developer page, then select your app. In the left nav bar go to settings. Then add platform. Ensure that your bundle identifier is correct. Then it should work.
If you have been testing with a sandbox facebook app and then receive this error when switching to the production app make sure you have published the app in the status & review tab.
I have integrated Facebook functionality into my applications. By using the link https://github.com/facebook/facebook-ios-sdk, I have integrated the Facebook. In this application, at the time of login, it's opening Safari and at the same time the application is going to the background and then after login again it's coming back to the application. My intention is that this flow can accept the application store or not.
This is the official Facebook iOS SDK and many apps in App Store already use it. So you can use it inside your app.
Also, the flow in your question is exactly what the documentation of the library describes and is, again, used by apps that are already in App Store:
If the device is running in a version of iOS that supports multitasking, but it doesn't have the Facebook app of version 3.2.3 or greater installed, the SDK will open the authorization dialog in Safari. After the user grants or revokes the authorization, Safari redirects back to the calling app. Similar to the Facebook app based authorization, this allows multiple apps to share the same Facebook user access_token through the Safari cookie.
So, yes, there is nothing wrong with this flow.