search

microsoft / code-push

A cloud service that enables Cordova and React Native developers to deploy mobile app updates directly to their users’ devices.
https://microsoft.github.io/code-push/
Other
4.36k stars 495 forks source link

Is the service down? Im getting a 503 and xhr.statusCode = 0 was returned. #665

Closed glenskie16 closed 4 years ago

glenskie16 commented 4 years ago

Hello, is the service currently down ?

yaronlevi commented 4 years ago

Yes... it seems that the service is not working as usual. We get lots of 503 and occasionally the bundle does get downloaded properly but it takes couple of minutes.

ronilitman commented 4 years ago

Any update?

alexandergoncharov-zz commented 4 years ago

Hi @glenskie16 and @yaronlevi, Thanks for reporting!

Could you please share your versions of plugins?

ronilitman commented 4 years ago

@alexandergoncharov I am using react native code push 5.3.2. I don't think it's related to react native at all. I, for example, get 503 when trying to call to CodePush.checkForUpdate. I am expecting to get null if there is no update, and object if there is update. I got none.

absoutherland commented 4 years ago

Also having this issue

stumpc commented 4 years ago

Also having this issue.

digital-tcbs commented 4 years ago

Also having this issue with cordova code-push. And when user can update app, appcenter dont update active user, install or download. API return 500 internal error.

dogcity commented 4 years ago

Also having this issue.

ButchMonkey commented 4 years ago

This is happening too frequently recently and causing major issues for us. Why is the updatecheck not hosted with the rest of the appcenter api? It's just a script that queries the API, which is much more stable Can we have access to the source for the updatecheck to self host and monitor issues ourselves?

bberzinskas-tw commented 4 years ago

Also having issues with this. This is introducing app init delays in the minutes!

ButchMonkey commented 4 years ago

This called all be done inside of the codepush code. As long as you know the packagehash, deployment key and maybe the label. You would just need to call the API and get all the updates for the deployment and then find the one that you need to download.

yaronlevi commented 4 years ago

This is critical. I think the engineering team should be more transparent about those issues. They have a serious impact on our business. If the community will get more insights about what's happening at your end, maybe we can better help pinpoint the problem.

mcrichards commented 4 years ago

@alexandergoncharov - Can you update us please? Your status site does not indicate any issue, but your service has introduced app load times of 2-3 minutes for our users.

decadX commented 4 years ago

503 error, the app pool down? This should be on the monitoring service.

https://codepush.azurewebsites.net/

yuri-kulikov commented 4 years ago

Hi all,

Sorry for this. We are investigating the issue right now. The problem is related to the acquisition service (the part which is used by SDK), the management service (CLI/App Center portal) is working fine. We expect this issue to be resolved within a few hours or less. In case of any changes we will let you know.

ronilitman commented 4 years ago

@yuri-kulikov Thank you for your response. is there any status site that we can monitor to see when this will be resolved? By looking at https://status.appcenter.ms/ everything seems normal.

ozzstrich commented 4 years ago

FYI this was heavily affecting our test suite so for now we've changed checkFrequency from .ON_APP_START to .MANUAL and it's working fine.

dogcity commented 4 years ago

We continue with the problem, we use react-native, approximately 5 minutes of waiting for the API response

yuri-kulikov commented 4 years ago

@ronilitman Sorry for the long wait, the status page is updated.

ronilitman commented 4 years ago

@yuri-kulikov it starts to look good on my side, can we officially say that it's behind us? Im in the middle of a deploy to the App Stores 😆

yuri-kulikov commented 4 years ago

It seems that the main issue is resolved! 🎉 Once again, we apologize for the inconvenience. We will continue to monitor the service.