For over a year, I have had stability issues with either the PhoneGap Build API or PGB itself. I have a c# winform program that unlocks the keys, uploads new .zip files, and monitors the build state. I have another program that monitors the build state and downloads the .ipa and .apk files. I have 6 apps with multiple keys (yes, I am paying for this service).
My c# programs have not changed, but OFTEN the build process fails. Usually, we just wait for our next build cycle and it "magically" works.
Today, I have been unable to get it to work. I get (500) Internal Server Errors (from PGB). So, I try again. I keep getting the (500) Internal Server Errors, but always on a different API call.
When I check the "BuildBot Status" it ALWAYS says BuildBot looks healthy. I have not found any status page for the API.
Does anyone else have random/intermittent stability issues with the API ( or PGB itself)?
My c# programs have not changed, but OFTEN the build process fails. Usually, we just wait for our next build cycle and it "magically" works.
Today, I have been unable to get it to work. I get (500) Internal Server Errors (from PGB). So, I try again. I keep getting the (500) Internal Server Errors, but always on a different API call.
When I check the "BuildBot Status" it ALWAYS says BuildBot looks healthy. I have not found any status page for the API.
Does anyone else have random/intermittent stability issues with the API ( or PGB itself)?
- 29 Posts
- 0 Reply Likes
- frustrated
Posted 4 years ago
- 29 Posts
- 0 Reply Likes
After trying about 8 times...it finally worked!
But, some of the build were slow. So I checked the "BuildBot status...it says "There might be something wrong". Even though my apps built just fine.
But, some of the build were slow. So I checked the "BuildBot status...it says "There might be something wrong". Even though my apps built just fine.
JesseMonroy650 (Volunteer), Champion
- 3325 Posts
- 122 Reply Likes
- 29 Posts
- 0 Reply Likes
Yeah...When my builds failed, the status was OK. Then, when the build finally worked, the status said there might be an error...makes so I don't trust the status page.
JesseMonroy650 (Volunteer), Champion
- 3325 Posts
- 122 Reply Likes
@Shawn,
the status fluctuates from minute to minute. You need to recycle page to see the actual status. The page is not live; it is a snapshot. If the status remains "in error" for more than two (2) minutes, take a break and come back to it. Below is the "canned answer" most people get.
Canned message
Sometimes it is a transient error. First, retry your build after some time, 10-20 minutes is good.
Occasionally, the webbrowser hangs, restart your webbrowser and see if that helps. On very rare occasions, clearing the cache helps; try this last.
You can always check the status of the build servers at: http://status.build.phonegap.com/
If it appears like you can solve the problem, check the documentation under: Failed Builds
You can also check the Error Log (see attached image).
If all else fails, post your App Id. And also use some HTML (like <code></code>) to post your Error Log

the status fluctuates from minute to minute. You need to recycle page to see the actual status. The page is not live; it is a snapshot. If the status remains "in error" for more than two (2) minutes, take a break and come back to it. Below is the "canned answer" most people get.
Canned message
Sometimes it is a transient error. First, retry your build after some time, 10-20 minutes is good.
Occasionally, the webbrowser hangs, restart your webbrowser and see if that helps. On very rare occasions, clearing the cache helps; try this last.
You can always check the status of the build servers at: http://status.build.phonegap.com/
If it appears like you can solve the problem, check the documentation under: Failed Builds
You can also check the Error Log (see attached image).
If all else fails, post your App Id. And also use some HTML (like <code></code>) to post your Error Log

- 29 Posts
- 0 Reply Likes
The real issue is NOT the build status page (other than I don't trust it). Yes, I know it is not a live page. If you would like, we can start a new thread specific to the build status.
- 29 Posts
- 0 Reply Likes
To get back to the REAL issue...the API is unstable. Occasionally, I will have the actual build fail. But, recently, most of the time, it is an API call that fails. Since the API call failed, there is NO error log on my app. In re-reading my original post, I can see how there could be confusion. So to clarify, I have 2 different build processes. This is not the same as the PGB's "build" process.
My testing process:
I have a c# program that uses to PGB Developer API to unlock keys, upload new zip files, and check the PGB build status for my apps. Yesterday, my first attempt uploaded all my zips correctly. But the actual PGB build failed (a connection issue getting one of the plugins). It then took around several tries for my c# program to do upload/trigger a new build. The API kept giving me server errors. It took me roughly 2 hours to get a good build. VERY frustrating!
My full Product Build:
Our mobile apps are a small part of our product line. My department manager will do an automated build process (for the entire product line) that takes roughly 40 minutes. Early in this process, my c# program is called to upload/trigger new PGB builds. Later in our build process, another c# program is a called to check the PGB builds and download the new APK/IPA files. Yesterday, our build process was started twice. On the first one, the API failed.
My testing process:
I have a c# program that uses to PGB Developer API to unlock keys, upload new zip files, and check the PGB build status for my apps. Yesterday, my first attempt uploaded all my zips correctly. But the actual PGB build failed (a connection issue getting one of the plugins). It then took around several tries for my c# program to do upload/trigger a new build. The API kept giving me server errors. It took me roughly 2 hours to get a good build. VERY frustrating!
My full Product Build:
Our mobile apps are a small part of our product line. My department manager will do an automated build process (for the entire product line) that takes roughly 40 minutes. Early in this process, my c# program is called to upload/trigger new PGB builds. Later in our build process, another c# program is a called to check the PGB builds and download the new APK/IPA files. Yesterday, our build process was started twice. On the first one, the API failed.
- 29 Posts
- 0 Reply Likes
When I am coding/testing a mobile app, I have an environment where I can test on my computer. But, occasionally, like yesterday, I need to push a test build out to an actual device (iPad). Then I use PGB to create ipa/apk files. It is so frustrating to waste a couple of HOURS fighting the PGB developer API.
Brett, OFFICIAL REP
- 547 Posts
- 54 Reply Likes
hi shawn, if you get a 500 please mention the date and time so we can check the logs for those specific errors.
- 29 Posts
- 0 Reply Likes
I have noticed a LOT more build errors. Of the six apps I am building, Quite often at least one of them fails. I don't have time to report every failure.
My process to check/download completed builds will rebuild the apps if there was a failure. This time, I got a build failure, the "retry" worked (no new code was uploaded). But I got a "The remote server returned an error: (429) Too Many Requests." error.
I got the error at 09/03/2016 23:18:18.690 MST (UTC-07:00)
As a reminder...we are PAYING for this service, so we can have multiple apps.
PLEASE FIX THE BUILD SERVICE!
If it is a matter of your servers not able to support the demand...Set up a different server group for paying customers.
My process to check/download completed builds will rebuild the apps if there was a failure. This time, I got a build failure, the "retry" worked (no new code was uploaded). But I got a "The remote server returned an error: (429) Too Many Requests." error.
I got the error at 09/03/2016 23:18:18.690 MST (UTC-07:00)
As a reminder...we are PAYING for this service, so we can have multiple apps.
PLEASE FIX THE BUILD SERVICE!
If it is a matter of your servers not able to support the demand...Set up a different server group for paying customers.
- 29 Posts
- 0 Reply Likes
Here is a snapshot of my logs:
[Verifying Builds] - 09/03/2016 23:17:31.466
================================================
ManagerPlus Mobile (1281700): android...Success
ManagerPlus Mobile (1281700): ios...Success
ManagerPlus Mobile (1302879): ios...Failed
M+ Logs (1280433): android...Success
M+ Logs (1280433): ios...Success
M+ Logs (1302870): ios...Success
M+ Work Requests (839455): android...Success
M+ Work Requests (839455): ios...Success
M+ Work Requests (1302878): ios...Success
[Rebuilding Apps] - 09/03/2016 23:17:32.338
================================================
ManagerPlus Mobile (1302879): ios
Rebuilds Queued
[Waiting For Builds To Finish] - 09/03/2016 23:17:32.876
================================================
Checking Build Status...
Pending Builds: 1
Pending Builds: 0
[Verifying Builds] - 09/03/2016 23:18:18.690
================================================
ManagerPlus Mobile (1281700): android...Success
ManagerPlus Mobile (1281700): ios...Success
ManagerPlus Mobile (1302879): ios...Success
M+ Logs (1280433): android...Success
M+ Logs (1280433): ios...Success
M+ Logs (1302870): ios...Success
M+ Work Requests (839455): android...Success
M+ Work Requests (839455): ios...Success
M+ Work Requests (1302878): ios...Success
The remote server returned an error: (429) Too Many Requests.
Processing Complete - 09/03/2016 23:18:19.740
[Verifying Builds] - 09/03/2016 23:17:31.466
================================================
ManagerPlus Mobile (1281700): android...Success
ManagerPlus Mobile (1281700): ios...Success
ManagerPlus Mobile (1302879): ios...Failed
M+ Logs (1280433): android...Success
M+ Logs (1280433): ios...Success
M+ Logs (1302870): ios...Success
M+ Work Requests (839455): android...Success
M+ Work Requests (839455): ios...Success
M+ Work Requests (1302878): ios...Success
[Rebuilding Apps] - 09/03/2016 23:17:32.338
================================================
ManagerPlus Mobile (1302879): ios
Rebuilds Queued
[Waiting For Builds To Finish] - 09/03/2016 23:17:32.876
================================================
Checking Build Status...
Pending Builds: 1
Pending Builds: 0
[Verifying Builds] - 09/03/2016 23:18:18.690
================================================
ManagerPlus Mobile (1281700): android...Success
ManagerPlus Mobile (1281700): ios...Success
ManagerPlus Mobile (1302879): ios...Success
M+ Logs (1280433): android...Success
M+ Logs (1280433): ios...Success
M+ Logs (1302870): ios...Success
M+ Work Requests (839455): android...Success
M+ Work Requests (839455): ios...Success
M+ Work Requests (1302878): ios...Success
The remote server returned an error: (429) Too Many Requests.
Processing Complete - 09/03/2016 23:18:19.740
Brett, OFFICIAL REP
- 547 Posts
- 54 Reply Likes
http://httpstatusdogs.com/429-too-man...
Seems you have hit our undocumented api rate limits. To view those limits please read the headers of any api request.
eg. "curl -v https://build.phonegap.com/api/v1/cur..."
Seems you have hit our undocumented api rate limits. To view those limits please read the headers of any api request.
eg. "curl -v https://build.phonegap.com/api/v1/cur..."
- 29 Posts
- 0 Reply Likes
Unbelievable! We pay, so we can have more apps, which means we need to make more calls to the API. The API has SERIOUS STABILITY ISSUES, which means we need to do more retries....generating more calls to the API
Then I'm told its an "undocumented" rate limit...No help!
Is this a new "feature"? I have not received this specific error before and have had to do retries (as the API is UNSTABLE).
Rate Limit? I figured that myself. Stating the obvious doesn't really help.
Then I'm told its an "undocumented" rate limit...No help!
Is this a new "feature"? I have not received this specific error before and have had to do retries (as the API is UNSTABLE).
Rate Limit? I figured that myself. Stating the obvious doesn't really help.
Brett, OFFICIAL REP
- 547 Posts
- 54 Reply Likes
in terms of the stability what status code are you getting? if they are 500 errors then please tell me a date/time range and i can investigate the issue.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Did anyone mention 'api rate limits' when we signed up for a paid PGB account?
Brett, OFFICIAL REP
- 547 Posts
- 54 Reply Likes
im open to a rate limit that people find comfortable with. if anyone has any suggestions.
JesseMonroy650 (Volunteer), Champion
- 3325 Posts
- 122 Reply Likes
@Brett,
I suggest separate VMs (virtual machines) for paid accounts - if possible. I further suggest these VMs have beeper accounts tied to this. The account could have quick response (10-20min) from 6am to 11pm (PDT/PST) and lagging response in other hourse. _OR_ these hours could be schedule to accomidate the most popular and active time zones.
NOTE, this would mean that the *free* accounts are subject to 60+ minute delays during ALL hours of the day - regardless of time zone.
A more flexible "quid pro quo" for service respones should be made for "pro bono". In short, paying should have better service, and therefore a more stringent response as part of the "quid pro quo".
Personal note, I have the free account.
Jesse
I suggest separate VMs (virtual machines) for paid accounts - if possible. I further suggest these VMs have beeper accounts tied to this. The account could have quick response (10-20min) from 6am to 11pm (PDT/PST) and lagging response in other hourse. _OR_ these hours could be schedule to accomidate the most popular and active time zones.
NOTE, this would mean that the *free* accounts are subject to 60+ minute delays during ALL hours of the day - regardless of time zone.
A more flexible "quid pro quo" for service respones should be made for "pro bono". In short, paying should have better service, and therefore a more stringent response as part of the "quid pro quo".
Personal note, I have the free account.
Jesse
- 29 Posts
- 0 Reply Likes
I hit the 120 limit. It seems this mostly happens when it takes longer to build the apps (more calls to see if it is done). Typical calls, like checking the status of an app, takes a certain amount of time. So, Increasing the Calls per minute to 180 should be sufficient (at least for my situation).
A couple of options for API call limits. Some of these may require separate servers for paid vs free accounts:
1. 180 calls for everyone.
2. 120 for free and 180 (50% more) for paid accounts. (most favored solution)
3. Or, 180 call for paid accounts...don't let free accounts use the API (incentive to upgrade to a paid account). (Least favored solution).
As for throttling the actual builds...no, don't do it! People expect better service when they upgrade to a paid account. So put paid members on separate servers or give them higher priority in the queue.
A couple of options for API call limits. Some of these may require separate servers for paid vs free accounts:
1. 180 calls for everyone.
2. 120 for free and 180 (50% more) for paid accounts. (most favored solution)
3. Or, 180 call for paid accounts...don't let free accounts use the API (incentive to upgrade to a paid account). (Least favored solution).
As for throttling the actual builds...no, don't do it! People expect better service when they upgrade to a paid account. So put paid members on separate servers or give them higher priority in the queue.
Brett, OFFICIAL REP
- 547 Posts
- 54 Reply Likes
240 for everyone. done.
we'll never throttle builds and i cant see that happening.
we'll never throttle builds and i cant see that happening.
- 29 Posts
- 0 Reply Likes
Thank you Brett, for be willing to expand the call limit.
- 29 Posts
- 0 Reply Likes
I got more errors today trying to do a build. For the last 3 days, I think I've been at about 50% success rate. About 50% of the time, at least one of my apps won't build or I get an exception trying to check on the status. If I click the [Rebuild] button, for the app, it usually works. So, I know it is not on my end...keys are correct, zip file is correct, config.xml file is correct.
Really, from my point of view, I don't care what part of the service failed. Whether it is an API call, build process, download, or whatever. The end result is still the fact that I did not get a good IPA or APK file.
Really, from my point of view, I don't care what part of the service failed. Whether it is an API call, build process, download, or whatever. The end result is still the fact that I did not get a good IPA or APK file.
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers
-
Programming (Others)
- 1167 Conversations
- 23 Followers



