Create Twitter app - Rate Limit Exceeded - twitter

When creating a new Twitter app at https://apps.twitter.com/ I receive the following error upon clicking submit.
"Error: Rate Limit Exceeded"

According to other developers on twittercommunity.com, it seems to be recent bug affecting all new apps... hopefully there will be some solution soon
EDIT: I was trying to create new application for past two days and now I finally succeeded... It looks like it was just some bug and hopefully it's ok now... try it :)
https://twittercommunity.com/t/rate-limit-exceed-in-creating-new-app-at-apps-twitter-com/34985
https://twittercommunity.com/t/rate-limit-exceeded-when-i-try-to-create-an-application/21453/3

Related

iTunesConnect "We can't process your request." when going to "App-Specific Shared Secret"

Whenever i try to navigate to App-Specific Shared Secret within ItunesConnect the dialog box attempts to load briefly then I get directed to a crash page titled
"We can't process your request".
I've reset safari clearing all website data and also used other computers.
I've contacted Apple who are sending an email shortly requesting more information but wondered if anyone else had come across a similar fault?
Another very easy solution which worked for me:
Use safari
SOLVED
The problem was due to not previously having created a master shared secret.
Once I did this then I could generate the shared secret for the specific application.
I has a similar issue, when I was getting invited to join Apple Developer Program. I tried joining through the invitation link and I would always get the "We can't process your request" message.
The solution was to:
Log in to an iPhone/iPad with that particular Apple id.
Try to install an app.
You will get a terms and condition pop up that you should accept.
Install the app
Wait for a while until Apple fast servers update your status (around 1 hour for me)
Now you should be able to proceed without the weird message.
I think need to update Mac OS to latest will solve problem. Alternatively you can use google chrome browser.

Do iOS App Short Links Take a While to Activate?

I know that once your app is ready for sale, it can take a while to propagate to all of Apple's servers. Is the same thing true of short links of the form http://appstore.com/myapp?
I can find my application on the store through search, and it can be downloaded. Direct links using the Application ID lead to the app perfectly. However, using the short link created following the directions here gives me an "Item not Found" error.
My app has been up for about 7 hours. This is rather important, because I use the short link from within the app to invite new users.
Thanks in advance!
It seems that it does indeed take a few hours for Apple to link the short URL to the full one. In my case, it took 12 hours.

Unable to retrieve objects from Parse due to error on iOS

I have been using my app during the day with no issues but I am now getting the following error on all requests I make to Parse to get objects:
2014-09-03 20:24:21.913 App[3407:332f] Error: Failed to initialize mongo connection (Code: 159, Version: 1.2.20)
Has anyone else experienced this and if so know the reason behind the message.
Thanks in advance.
EDIT:
Parse is down once again (no surprise) Here is the link to the new bug if you are having the same problem of mongo DB going down. The twitter and status website should be the same. Hopefully they fix this sooner rather than later.......
https://developers.facebook.com/bugs/665440236886829/
I am having the same problem and posted on the developers website you can follow it here.
https://developers.facebook.com/bugs/300758356778621/
Edit: They are experience a lot of different problems it sounds like right now. Facebook was down for awhile but is now up. They are still working on parse errors and crashes according to what the developer left on the link above.
So it is coming up slowly but people are still experiencing errors on top of following the bug at the link above here is there twitter account.
https://twitter.com/ParseStatus
Also their status website.
http://status.parse.com/incidents/m9k6y5qbz2dk
Should be up shortly (hopefully).

Flurry log event updation is quite late as compared its session in iPhone SDK

I integrated flurry with my iPhone app, Its working fine but its log event section update quite late as compared its session updating. It show me 3 days previous log event history but in session its showing me today session history also. I reched my code which was fine. I don't know why this happen. Kindly help me on this if some one already face this. Thanks in advance.
It initially takes sometime to update custom events. If it is actually taking a lot of time regularly. You must reach out to support#flurry.com . They would respond back in 24hours and provide support.

Creating new app on Twitter causes "Rate limit exceeded" error

I have been trying to create an app for my Twitter developer account. Everything has been going good for a while now but now when I create a new app, I get a "Rate limit exceeded" error. I think this error comes with the API but I am only creating a new app. Any idea why I might be suffering from this problem?
UPDATE: Bug seems resolved. I was able to create an App.
OP is creating an App and seeing this error in the Web UI. The App is used to get the required OAuth credentials. Only after you have those credentials you can start to use the API.
Apparently there is currently an error which prevents creation of apps.
Twitter acknowledged the problem and is investigating: https://twittercommunity.com/t/does-not-allow-me-to-create-a-new-app/32528/9
The HTTP Headers mentioned by DWRoelands are sent back when one is actually using the API and exceeding rate limits (as described in the document he linked)
You'll want to start here: REST API Rate Limiting
Definitely take some time to read and understand that document. It will help you a great deal.
The responses that you get back from Twitter contain headers with important information about your current rate limit status:
X-Rate-Limit-Limit: the rate limit ceiling for that given request
X-Rate-Limit-Remaining: the number of requests left for the 15 minute window
X-Rate-Limit-Reset: the remaining window before the rate limit resets in UTC epoch seconds
By examining these headers, you can help your application make smart decisions about how often it makes requests.

Resources