I have an app running on SoundCloud's PHP API.
Today when I or anyone else tries to authorize the app, the callback returns Error Code 429, which I found meant too many requests. After waiting about an hour it works again for a few minutes.
The app has always had the same amount of users, and today authorizing seems to no longer work 80% of the time.
I also tried registering a new app and the same problems occured.
Is there an issue on SoundCloud's side? Is there anything I can do to fix this?
Related
Does anyone also experienced this type of problem? Webhook works perfectly fine with the rest but just with 1 certain user I'm not receiving anything from the webhook. It's not even called from facebook
The user already tried to uninstall and install back the messenger application but still the same result. Maybe there's something in their settings that need to be turned on or what
I somehow confirmed that facebook API has some traffic issues and sometimes have a delay in showing messages that are sent through their APIs. So patience is a virtue :D
So the situation is as follows, I used 3 different packages from pub.dev all for the purpose of user authentication with Twitter (3-legged Oauth). My main package which I was using in my app was flutter_twitter_login. This worked flawlessly until today when I run my app everything was still working (launched the sign in page and signed in successfully) until the authorisation function was triggered when then I was redirected to the 'Sorry, that page doesn't exist' page with a search bar on Twitter (error code 34). I thought maybe this is a problem with my package like a new bad update, simply not the case, all 3 most known packages for user authentication failed in the exact same way. The other 2 I tested were twitter_login and flutter_twitter.
Keep in mind that 2 days ago I had a successful login within my app with a confirmation message and valid HTTP message returned. Most of my code were examples given by the flutter package creators.
I made no changes to my code, yet it broke seemingly on its own
After seeing some relevant problems over the years reported on stack overflow and the Twitter developer forums I suspect that the problem may be with the API endpoints (which my flutter packages manipulate, not me). Any opinions/directions?
PS: I have seen issues that say about the app becoming deactivated, disabling 3-legged Oauth by accident and account getting blocked all 3 of these are not the issue I checked/tested thoroughly.
Relevant Twitter forums post: https://twittercommunity.com/t/flutter-twitter-login-stopped-working-with-authentication-error-sorry-that-page-doesnt-exist-code-34/152435
It seems that the issue was on the API side and it has been resolved without me changing anything to my code. The issue lasted 48 hours.
I am facing strange problem, I have created two facebook apps, one about 2-3 months back and one recently 4-5 days back.
The strange problem is when I try to use graph api feed method to post to one of my pages from my old app (or default graph api of facebook) it works fine and post message to my page wall, but when I try the same with my new app it gives this error
An unexpected error has occurred. Please retry your request later.
I searched for it and found that this error comes sometimes and goes away automatically, so I waited but it is keep on coming while old app is still working on the same time.
I am using the same set of permission on both the apps
Any idea?
I have an iPhone app that's using facebook connect via the ios-sdk to upload videos to facebook. It's been working fine until today. Most users are able to upload ok but one particular user gets this dialog first:
permissions ok
Once he hits ok he gets this dialog:
error dialog
I looked in the diagnostics for any errors and I didn't see any. The only thing I did notice was under feature requests it says "requests 1.0 - 30" for limit per user per day. I don't know if a particular user is running up against some limit or something else is going on.
The other interesting thing is that we have a full version and lite version. He can upload via the lite version but not the full version. Both versions use the same api calls for uploading videos.
update: User deleted the app from privacy settings in his facebook account. Then the app re-authorized and it all worked.
How did it get into this state? Is there a way to detect via the IOS app and resolve it?
Occasionally Facebook will return that error and most of the time (for me) there is nothing I can do to fix it except try again.
This error happens to me not only in this similar situation but also everywhere like Feed Dialog, Request Dialog, etc...
I'm pretty sure it's Facebook server error.
My app is currently on beta testing, so a few people are actually using my app to connect to Facebook through either WiFi, 3G, or EDGE.
However they are reporting that it's very slow. I checked out my API response time, and it turns out that it's 31,546ms. How can it be so long? That means that users of my app has to wait about half a minute before they can post their stuff successfully to Facebook... Anyone has any idea how to speed it up?
P.S. I checked this out from going to the inisights of my app.