Developer: Missing Privacy Policy‏ - Did not update in time - facebook

I recieved two emails from facebook to put privacy policy link but I couldn't do it in time. I had over 8000 active users and now none can connect onto my forum. I guess they terminated the app? I did add the link onto my app but still it isn't working. I have looked around to see If anyone else went through the same. How do I contact Facebook and get this resolved.

I guess they terminated the app?
Check your app dashboard – usually, as a first measure, your app gets put into sandbox mode.
Add the missing policy links, and then try taking it out of sandbox mode again.

Related

Parse iOS facebook login fails

I am using parse facebook login for new users of my app. Most users are able to use it without a problem and I have successfully tested all Facebook login scenarios. Some users, however, report that when they press the login button they see brief activity indicator and then nothing happens. In code, no error is registered but the user is not brought beyond the login page to the app's initial screen. The problem resolved if the user deletes the app from their Facebook app settings and then tries again. Has anyone else experienced this and/or found a solution? Thanks
Not sure if this ever got resolved for you.
There are multiple possible causes for this of course including your own code. However, we've seen a similar issue with 2 causes / solutions.
UX-wise we detect multiple failed logins (typically with no error code) and then pop a notification telling the user how to solve. Still digging for a code-level solution that'll solve either of these issues permanently (if you found one, please post!) but hope these help & let you know you're not crazy.
Issue #1: User is logged into multiple Facebook accounts from the same device (e.g. a primary account and an org or 2ndary account).
Fix #1: Have user log out of all Facebook instances (app, safari, iOS settings) and then log back in.
Issue #2: User has rejected Facebook permissions.
Fix #2: For iOS, make sure Your App is toggled on in Settings -> Facebook -> Your App

Sandbox mode will not disable - app cannot be seen on page

I am trying to help my sister with her facebook business page. She created an app some time ago, but did not disable sandbox mode, so it has never been visible.
She made me an administrator of the page, and the app. But when I try to disable sandbox mode to make the app visible on her page, I get the following error message:
Error
There was a problem saving your changes. Please try again later.
Before this error, I believe facebook directed me to set up a category for the app in the app details, where "other" had been selected. I tried changing this to "app for pages" but it didn't help.
I created another app some time ago where all the same fields are filled in as with my sister's app, and had no trouble disabling sandbox.
I do no understand why facebook is not allowing me to disable sandbox and make the app live. I have googled this question but been unable to find an answer.

Facebook - Cannot disable sandbox mode after Privacy Policies update

After a few Facebook alerts about my app lacking privacy policies (totally forgot about it and the email address was not my own), my app was taken down. So, I updated the apps Privacy Policy and ToS, saved changes and tried to disable sandbox mode so my app became visible again.
Nothing happened.
It keeps showing me an error message:
Is there something I might be doing wrong? The Privacy Policy URL and ToS URL are the only things I changed, and the app worked fine before.
Thanks in advance
UPDATE
It is not a problem with the privacy policy update, but with the basic app settings. Whe I try saving the app without removing sandbox mode, it still shows me the error. Has anything changed since, or the Facebook service is having problems?
Turns out Facebook no longer accepted the tilde (~) as a valid url character.

Facebook Login Error iOS Application

My iOS application allows me to login using my own facebook account successfully. But when I send it on test flight to a friend, the app downloads but when he presses connect to Facebook (which works on my simulator and personal device), it won't let him log in. Doesn't even give him the option to, just spits out an error (com.facebook.sdk error 2). What am I missing? What would cause it to work for me, but not for others? I'm just looking for a general answer here because I followed all the facebook tutorials and I can't imagine what kind of thing could be going wrong.
I just figured out the problem. Should have been SUPER obvious, but being new to development I didn't realize I needed to change the sandbox setting to disabled in order to allow others to access facebook through my app.
This error pops up when your app is not authenticated properly.
You need to keep your BundleId the same at all places.
Change your bundleId in the app that you have registered on Facebook as com.asdad.casd instead of < teamId >.com.asdad.casd

Facebook ios sdk 3.0 active session FBiOSSDK error2

I am getting "com.facebook.FBiOSSK error 2" error when ever try to login with my app by using device.But its working fine with the simulator.
I am using iOs SDK 3.0 Beta. any solutions?
I had the same problem on authententication with "com.facebook.sdk error 2". And i think solved it on my part. Just make sure on your app definition on "https://developers.facebook.com/apps/.."
on "IOS Bundle ID " section, that you put your app id like this com.domainname.appName and not X792739.com.domainname.appName
Yes, after you see this error, if you go to Settings, you will see that the setting for this app is turned "OFF". But the problem in this case is that the user was never prompted to allow access -- i.e. the setting was turned to OFF automatically on first time access. If the user was asked, then of course that is understandable, but this is not the case (it's as if the SDK silently and automatically pressed Don't Allow for the user). That's why this is a problem.
Before you read any further, I want to note that once the setting is set, you cannot simply repeat the process to test it, because once the setting is set, it will never ask the user (even deleting and reinstalling the app does not help). To test this issue, you need to reset the permissions by going to Settings -> General -> Reset -> Reset Location & Privacy, before you can try to replicate this again.
From testing, I've discovered that if you have offline_access in the permissions you are requesting for the first time, then it will give this login error (and not prompt the user and set the permission to OFF). The SDK does not check and tell you that this permission is not allowed; it just fails to login.
We were seeing the com.facebook.sdk error 2 error only for certain people. The problem ended up being that our Facebook App was still in Sandbox Mode. Disabling that at developers.facebook.com/apps/{ourfacebookid} instantly fixed the problem.
Turns out it was working for those of us who were set up as admins for the FB App, but not anyone else.
This error is received when the user chooses "Don't Allow" when asked to give the app permissions.
I suggest that you replace the default error message (copied from Facebook SDK sample code) with a user friendly message, telling him to make sure he granted your app the required permissions.
To fix this at iOS 6, go to Settings -> Facebook and turn your app's switch ON.
I got the same problem when I tried to follow the tutorial (http://developers.facebook.com/docs/tutorials/ios-sdk-tutorial/authenticate/)
It seems to work fine when I followed the instruction in the 'howto' section, and it's a little bit different : https://developers.facebook.com/docs/howtos/login-with-facebook-using-ios-sdk/
I faced with the same problem. It turns out that if the Sandbox is enabled than the users should be admin. If it is disabled then works for everyone.
In my case this error was the result of asking for 'publish_actions' permissions at authentication. Write permissions have to be gotten separately: https://developers.facebook.com/docs/tutorial/iossdk/upgrading-from-3.0-to-3.1/