I've been researching all over trying to fix this issue to no avail. I followed the SwiftyDropBox tutorial thoroughly and had everything working. It's now not working and I'm not sure why. Based on this post and this link, the error is supposed to be related to not having the DropBox app installed. That's fine. In the tutorial it says:
If you wish to authenticate via the in-app webview, then set browserAuth to NO. Otherwise, authentication will be done via an external web browser.
I set that parameter to false and still get the same error.
Turns out the issue was that I already had a viewcontroller being presented. It looks like the dropbox authorization acts as a "presentation". It worked once I dismissed the viewcontroller. Those error messages still appear but according to this post it's normal behavior. I wish they'd have more descriptive messages.
This error message is displayed when native Dropbox app is not installed in the phone and can be ignored. See response from Dropbox forum
Related
I'm using the Facebook Share Dialog by using URL Redirection, followed this documentation:
https://developers.facebook.com/docs/sharing/reference/share-dialog/#:~:text=for%20Webmasters.-,Share%20by%20Using%20URL%20Redirection,-To%20share%20a
When submitting a private message via mobile, the next error arises: "Attachment Not Found: The attachment could not be found". It only happens in mobile. When I try it from desktop everything works fine.
I tried contact Facebook support but their support channel in no longer available for this feature.
Any idea?
Thanks!
I'm using Facebook Marketing API. Starting from last week I get an error message when I try to send a request from my local machine.
The exact error I'm getting on my screen is the following:
RequestException in RequestException.php line 154:
(#3) App must be on whitelist
When I send a request from production server, the app is working fine and creates a campaign.
I went through all the possible settings in the app, to see if I'm able to configure it from there, but seems like the app is configured well.
App is also public:
This app is public and available to all users
Appreciate any help or tips!
App suddenly started working without making any changes to code or configuration. Must be an Facebook issue...
I had this issue when provide 'is_autobid' property to new campaign
We have a Facebook app that publishes URLs to a user's newsfeed via the Facebook iOS SDK. These URLs are for pages that have OpenGraph attributes defined and we've verified in the Facebook Linter that it's correctly defined.
However, periodically we are seeing that Facebook won't correctly parse the OpenGraph attributes and have less than a stellar post to Facebook:
We will most often get posts parsed correctly resulting in posts like these:
We'll periodically get posts like these:
However, you can see this later post works correctly in the FB Url Linter: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fchewsy.com%2Fr%2Fa%2F1bhLT.
However, sometimes the URL Linter will report a 503 but I see nothign in our logs. And even more odd, when the URL Linter reports the 503, it will shows that it can read the OpenGraph attributes defined. See this screenshot:
Since this is inconsistent, my first guess was this was a Facebook issue so I opened a bug. However, since I'm not seeing this issue rampant in the newsfeed with other apps, I'm starting to wonder if we aren't following the right steps to publishing FB content.
For example, are we supposed to post to the URL Linter first, then publish via the Graph API? This seems like a ridiculous extra step, but I'm grasping at straws here...
It's probably due to fact that in a time Facebook Linter visited your site it wasn't accessible, just couple of refreshes on a Linter Tool with URL you've provided resulted in Bad Response Code error, returning 503 status code:
http://chewsy.com/r/a/1bhLT"">
You should dig in logs of your application/site to discover the real reason why this happen and fix it.
Just a quick note that this should no longer be happening for CloudFlare users. We pushed a fix for the 503 debugger issue moments ago that appears to have fixed the problem. Please contact us if you see any other issues with the Facebook Debugger.
I'm using the 'feed dialog' with my Facebook desktop appliaction to recommend my app (and not using prefilled text).
This dialog worked well before, but since Sunday after trying to post I'm redirected to an error page which requests captcha filling, and once it's done I receive an error page.
At the beginning I replaced the URI, which worked and I was able to post normally, but since yesterday Replacing the URI or the URL doesn't work anymore.
Do you have any idea what can cause this?
even i have been getting the same problem. the feed dialog directs me to a captcha and even if i enter the correct words it gives me an error that the words did not match. i was using the feed dialog to publish on my wall through an app. the legacy rest api is however working flawlessly.
This started happening over the last weekend that FB notification page is no longer embedding the [app_id] in the acceptance URL and throwing a 404 when clicked on the "request" link on this page:
(Sent Today)
http://apps.facebook.com/224695104250620/?request_ids=161817803905540&ref=notif
Notice that how it is different than what we used to get earlier (and the working version):
(Sent September 21)
http://apps.facebook.com/piratesapp/?request_ids=10150329048068535&ref=notif
I've gone back and re-checked Facebook documentation on "Requests Dialog":
http://developers.facebook.com/docs/reference/dialogs/requests/
and found that it clearly states the working version:
http://apps.facebook.com/[app_name]/?request_ids=[request_ids]
None of the app settings changed on our part and all on a sudden, the strange # started showing up in place of [app_name]. We've verified that it's not app_id as it doesn't match with any of our registered apps. The behavior appears to be the same across apps, apps across different Facebook developer accounts and so on.
Is this a bug? Should I file a bug with Facebook? I wanted to check with the experts here before logging a bug.
Appreciate a prompt response on this.
Ok looks like this is a bug:
https://developers.facebook.com/bugs/209695662429264