I encountered a problem with my facebook application, when I tried to switch it to live mode, the app's rights and features were not displayed, in development mode, the permissions and features show normally. I'm sure the application and the permissions (manage_pages, publish_pages) have been evaluated and verified by the business, can someone help me, I'm really worried, i have posted some pictures below:
Related
I am working on a FB app for creating Facebook Ads. In the past I was able to debug the whole FB Ad creation process in a development mode but suddenly I started getting this error that I was not able to find documentation for.
Request:
https://graph.facebook.com/v2.2/act_foo/adcreatives?access_token=bar
Response:
{"error":{"message":"Invalid parameter","type":"FacebookApiException","code":100,"error_subcode":1885183,"is_transient":false,"error_user_title":"Ads creative post was created by an app that is in development mode","error_user_msg":"Ads creative post was created by an app that is in development mode. It must be in public to create this ad."}}
I've searched Facebook API documentation but haven't found anything about this error error_subcode: 1885183.
Anyone has experience with this error or a hint how to deal with it?
EDIT
Bug is already reported to FB: https://developers.facebook.com/bugs/1605648466391176/
For completeness of this question, the answer from the resolved bug report is as folows:
Across our entire platform, Marketing API included, content created by apps is only visible to users that can see the app
We had a bug which was allowing ads to be created which were promoting posts created by apps that are in development mode - such ads would not be visible to anyone other than Admins, Developers or Testers of the app - this caused multiple issues in our ad delivery system and the correct validation is now in place to prevent such ads being created
If you want to create ads from an app which is in development mode, this is possible, but the post you're going to promote must have been created by an app which isn't in development mode - i.e if your app is in development mode it's OK provided you're promoting existing page posts from a page's /promotable_posts endpoint and the app that created those posts is not itself in development mode
If you're not using existing page posts, and are creating them inline/implicitly as part of an ad creation, the app used to create the ad must be visible - you can change this for your app using the "Do you want to make this app and all its live features available to the general public?" toggle on the Status & Review tab of the app dashboard for the app
https://developers.facebook.com/bugs/1605648466391176/?comment_id=1039672816061177
We had the same issue and found a workaround that fixed it.
We created a new basic facebook-app with no additional permissions and published it right away.
We then added ourselves as admins and could create creatives through the marketing api again.
Hope this helps you
For my company I am developing an automated photo-booth. The goal is to capture a photo and after a quick review publish the photo to the company's Facebook page, all automated.
To this end I registered an app, and the application is conceptually done and works.
However only the developers of the app can see the photos, which seems to be because the app is not "reviewed by facebook" yet.
When I read what is required to get it reviewed, facebook needs to be able to test and verify the app. This is however impossible because the app only works in combination with the hardware on site, and it is not meant for anyone else to use it.
Am I solving this the right way? Can it be approved just for some users, like a "private" app? I'm not sure where to go from here.
If no user authorization is involved and you only use an Extended Page Token for that Page (that is valid forever), you don´t need to go through review. Just set the App to public in the "Status & Review" section of your App settings.
The App will work without review for everyone with a role in the App (Admin, Developer, Tester).
If this is the wrong place to ask this - I super apologize in advance, I'm at a loss here.
I'm trying to develop a simple Facebook PHP app and I'm having trouble getting publish_actions. Here's how the app will work:
You enter your email address
Periodically, you receive emails like this ("Hey nice person, here's a video we think you might be interested in, click here to share it on your wall")
You click the button, it takes you to the app site, which asks for your publish permissions
You enter a message and share the video to your wall.
My problem: all of that requires publish_actions permissions, but FB won't grant them to me until I can show a working app (I applied for permissions and was denied because "Canvas
Your app isn't loading properly and errors appeared while testing your app").
My question: How do I get access to publish_actions without being able to show a working app (which requires publish_actions)? Can I use PHP to post to my own wall in development mode somehow to test it out?
Again - I apologize for the dumbness of this question, I am a PHP dev who is very new to FB, and I've looked everywhere for answers on this.
Try using the Facebook Graph API Explorer
You will be able to simulate some of the app permissions as if it was production.
Just go and select your app, then select Get User Access Token, finally select all the permissions you want to test.
Use the given token to develop and test things out and when you have a semi finished version, submit it through the app review section, following the Facebook App Review Guidelines
I submitted screenshots, a video of my app working, and step by step description on how to reproduce the publish action.
Hope it helps.
I want to get approval for my app id only for the like and share buttons of facebook but it seems that it got more complicated then before.
When I go to my app then javascript sdk to create the code of javascript for my site it shows
This app is in Development Mode and not available publicly.
Modo público can be enabled in the App Dashboard.
So then I go to the app dashboard and it is asking a lot of information I don't have because it's only to have the like button in my site I don't want to read more likes of users.
So anyone can help me to find the right way to do this.
The only thing you should have to fill in to make the app public is the Contact Email on the main Settings page:
(source: infused.org)
Found this thread whilst having the same problem. In addition to infused's post, you have to go to "status and review" and turn "Do you want to make this app and all its live features available to the general public?" to Yes.
Furthermore, I noticed that removing the app id (as per the code you get if you are not logged in and go to the plugin generator page), then the code does not work at all.
Also, if the app is not set as live, then it will still sometimes work - just to make things harder to debug.
I am not sure if anyone has ran into the problem but it is really bugging me and affecting our uploading from our iPad to facebook.
I have a local server running XAMMP with a gallery of images displayed via a local web page. These images are from our Photobooths and automatically get added into the gallery when a photo is taken in the booth.
These can then be accessed on the local network via the iPad. Users can then login to facebook and share this images.
Because this is a shared iPad being used by multiple users, is there any way of getting users to login without having to answer security questions?? It used to be fine but now Facebook says the login is suspicious as it does to recognise the device.
I have created an App to post the photos to facebook through the Facebook Development site and it works perfectly from my account and many users, but some seem to get the suspicious login attempt and have to identify friends and date of birth etc.
Is there a correct way to do this?
Thank you Richard.
Is there a correct way to do this?
What you are experiencing is the “correct” way.
Facebook offers this as a security feature – a user can add his devices to his list of “known” devices, from which he will be able to login straight away, and have to answer additional security questions when logging in from a different, “unknown” device.
If users have this feature enabled, they should not be surprised by this happening in your scneario. It’s what they explicitly want, and they’re getting it.
So you should in no way try to mess with that, just because you might think this to be “uncool” or a “nuisance” – it’s not, it’s a feature offering extended security that the user wants and has explicitly chosen.