microsoft
CodePush.updateCheck returns 503
Thanks so much for filing an issue or feature request! Please fill out the following (wherever relevant): Hi,guys When I request an updated interface, it returns 503 who can help me?
Same here
<HEAD>
<TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii">
</HEAD>
<BODY><h2>Service Unavailable</h2>
<hr><p>HTTP Error 503. The service is unavailable.</p>
</BODY>
Same here this is what I'm seeing on Sentry
POST https://codepush.azurewebsites.net/reportStatus/deploy [503]
GET https://codepush.azurewebsites.net/updateCheck [503]
Same here 502 and 503 errors Can someone look into this? its affecting production apps.
Hello everybody, and sorry for late response.
Recently we had an incident on Azure side that lead to 503 errors when requesting CodePush server. Do you still experiencing such problem?
@ruslan-bikkinin Its still happening for us today (I have sent the curl call to anvesh kasani from the support appcenter team) See the screenshot below, this is the same XHR that the codepush cordova plugin sends and randomly, it will take a back a 503.
Thanks for you comment, looking further it may be related not only to underlying Azure issue but also to some of backend services recycled. Our team actively looking for root cause and possible mitigations steps.
We're getting this issue now across all our apps. It happens way too often. We may have to think to move away from code push or investigate ways to host our own code-push server. It's very frustrating :(
Apologise for the inconvenience the issue causing, unfortunately no root cause is found yet but we continue our investigation.
Couple of hours ago we deployed the change which may(or may not, we need to gather some statistics to estimate it) mitigate(not fully fix unfortunately) impact by how frequent this happening.
So far I recommend you to stay tuned to this issue where we definitely would post update when we expect full remediation and would ask you for helping us to confirm this.
@snowpardx absolutely. I'll let you know once it's resolved on my end. Are you guys seeing the issue on your end? And is it under investigation?
Yes, we are still investigating this: 1 change which may mitigate this was deployed recently, and in addition we also investigating what could be possible root cause (probably tomorrow CET time, additional telemetry changes could help us to confirm one of the issue would be ready for deployment).
By the way unfortunately right now we don't have understanding on why this is happening, and so have no ETA. Once we learn more, we definitely return back to this issue.
@snowpardx we've been having issues with code-push throughout the day. We've checked recently and seems like all the issues are gone now. The code-push is now working as expected for us. We're happy that everything is resolved, would be good to know the root cause to avoid it in the future. Thanks!
@snowpardx and Andrei we are still facing this code push issue drastically and can't send builds to production application. Can we have any workaround so that the builds could be sent ? Please suggest
Service Unavailable
HTTP Error 503. The service is unavailable.
Unfortunately we don't see any indication that deployed change helped a lot, I can confirm that error rate is somewhat about the same as before, so issue persists for some part of requests.
But it definitely appear only for small part of requests, so some subsequent retries would probably succeed.
Right now, we don't understand the root cause of the issue (it just started to happen at some moment, without directly related code changes). So there is no workaround available right now (except of retrying in some time).
Thanks for bearing with us while we investigating what's going on.
Thank you @snowpardx , I understand, just hope the team is actively working on this one. Facing too much heat from customers about the failing code updates. Will wait for an update from you. 👍
@snowpardx @VrajSolanki I can confirm that the issue is back this morning. It was working well last night which makes me think, if it's simply a high load issue.
Are you guys able to scale out code-push services?
At the moment its 80-90% fail rate; Maybe try and restart the blades on azure? If that fixes it, maybe setup Azure Autoheal to detect 503 and restart the instance?
We are running two apps in service. However, we only find the issue in the only one of our apps. Another one works just fine. Our app heavily depends on the update check code, which make whole app unserviceable. We just deployed new application which can run with the 503 error. Hope the issue gets fixed soon. Let me know if you need more details of packages or settings.
@tedkimzikto I am currently sending the code push to check. Still the same issue persists.
- the 503 error
- check code push coming up too late for the app, because the api is not responding. I would say it has the same fail rate even now.
@VrajSolanki yes, it's not working at all. It's hurting our business badly, especially considering it's been down for couple days now. Customers are seeing an older app version because updates are not coming in...
deploy new version to the playstore and app store for now, and hope for the best :0
@tedkimzikto :) easy to say, we have about 100 apps that we'd need to deploy.
https://status.appcenter.ms went back to normal, is it relative to the issue?
@tedkimzikto it was green all day yesterday. It doesn't reflect the real status of the service as far as I can see
https://status.appcenter.ms went back to normal, is it relative to the issue?
easy to check, https://codepush.azurewebsites.net/updateCheck?deploymentKey=&appVersion=9.2.10&packageHash=&isCompanion=false&label=v145&clientUniqueId=1123412341234
@tedkimzikto @andrei-m-code even if we push the app to app store it is going to take couple of days for the apps to be live, until then all the applications would break. Can we have a hotfix or workaround so that we can send a hotfix and then freeze the use of code push until it is fixed ? @tedkimzikto as you suggested on app is working, won't the same setup solve for this one too ? @snowpardx Want to know your thoughts here
@VrajSolanki to be honest I don't think that it going to be fixed in short frame like couple of days, given the fact we don't understand the underlying issue, so no ETA so far.
Interesting thing here is that with url you provided I'm able to reproduce the issue way more frequent that "around 5% of total requests" we seeing in the telemetry, while it doesn't repro at all for the app I created by my own.
@snowpardx can we get the details from your test app ? maybe some miss on our end for the setups ? that can be a good starting point, for us to try and fix it ?
Same issue here. Testing using the @decadX suggest. Some evolves from App Center team?
@snowpardx The issue is clearly periodic. Right now code-push works very well for me. If the issues start to happen again tomorrow morning, it would support this theory. Therefore I believe the periodicity of the issue happening could only depend on the load, unless you guys do something funky with the services every day during business hours :) ?
Possible solution: scale the services out and see if it fixes the issue. As you're hosted on Azure, you must have AppInsights connected to this app service? What is memory and CPU use? Is the service running hot between 8am-6pm EST? I'm sure you guys have already checked it. Regardless I'd still try to scale the services and see if it fixes the issue.
We heavily rely on code-push and really need it to be fixed. I'm happy to jump on a call and show you what we experience or run some tests from my app as needed. Please feel free to reach out.
Hi, Same issue here. All our production updatechecks are failing and no one is able to install the build. Does anyone have any update on when the issue will be resolved?
