Error 503. The service is unavailable #511

Activity

1. atticoos commented on Sep 11, 2017

   

   Atticus White (atticoos)

   on Sep 11, 2017

   Last edited by atticoos

   More actions

   We started to see this spike on Sept 9, and it continues today
2. claykohut commented on Sep 11, 2017

   

   Clay Kohut (claykohut)

   on Sep 11, 2017

   Last edited by claykohut

   More actions

   I've been seeing my builds occasionally hang / never finish loading on the codepush sync step recently -- any way I can confirm that its related to this and not something on my end?
3. JAStanton commented on Sep 11, 2017

   

   Jonathan Stanton (JAStanton)

   on Sep 11, 2017

   Author

   More actions

   Clay Kohut (@claykohut) My app aborts after N seconds if I don't think codepush will return in time so that my boot process of the app isn't dependent on if CodePush servers are alive. I recommend something similar.

   👍React with 👍1Reacted by Atticus White
4. claykohut commented on Sep 11, 2017

   

   Clay Kohut (claykohut)

   on Sep 11, 2017

   More actions

   How many seconds are you using as N in that case, Jonathan Stanton (@JAStanton) ?
5. JAStanton commented on Sep 11, 2017

   

   Jonathan Stanton (JAStanton)

   on Sep 11, 2017

   Author

   More actions

   I wait 5 seconds for the download / apply step. If it doesn't happen by then I let my app continue to boot. I then apply any updates on next app launch.
6. patniko commented on Sep 12, 2017

   

   Patrick Nikoletich (patniko)

   on Sep 12, 2017

   Contributor

   More actions

   Hi Jonathan Stanton (@JAStanton), we have been experiencing a few load issues with our production environments. A permanent fix should be implemented over the next 30 days as we finish up the re-architecture of our backend services, but for now we are monitoring the current problems and making adjustments to rectify them.
7. max-mironov commented on Sep 15, 2017

   

   Max Mironov (max-mironov)

   on Sep 15, 2017

   Contributor

   More actions

   Hey all, closing this as we don't see any problems with this currently, please let us know if you see this issue again.

   👍React with 👍1Reacted by Atticus White
8. Max Mironov (max-mironov)

   closed this as completedon Sep 15, 2017
9. prayuditb commented on Dec 18, 2017

   

   Prayudi Tirta Bayu (prayuditb)

   on Dec 18, 2017

   Last edited by prayuditb

   More actions

   Hello everyone, I just got this error today. I use react-native-codepush.

   Here is some of my code

   const codepushConfig = {
     checkFrequency: codepush.CheckFrequency.ON_APP_RESUME,
   };
   ...
   
   componentDidMount() {
       codepush.sync({
         installMode: codepush.InstallMode.IMMEDIATE,
       });
     }
   
   ...
   const myApp = codepush(codepushConfig)(MyApp);
   

   12-18 23:27:39.854 13537 15879 I ReactNativeJS: [CodePush] Checking for update.
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: [CodePush] An unknown error occurred.
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: [CodePush] 503: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: <HTML><HEAD><TITLE>Service Unavailable</TITLE>
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: <BODY><h2>Service Unavailable</h2>
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: <hr><p>HTTP Error 503. The service is unavailable.</p>
   12-18 23:27:42.298 13537 15879 I ReactNativeJS: </BODY></HTML>
   

   What should i do to fix this error?
10. prayuditb commented on Dec 18, 2017

    

    Prayudi Tirta Bayu (prayuditb)

    on Dec 18, 2017

    Last edited by prayuditb

    More actions

    In my case, I got this error after terminating release process by pressing ctrl + c (because I forgot something). I think this error reproduced by unfinished release process.

    To fix this error, you can try clear deployment history by running this command
    appcenter codepush deployment clear -a <ownerName>/<appName> <deploymentName>

    Warning, this command will clear all of your release histories

    hopefully can help
11. sergey-akhalkov commented on Dec 18, 2017

    

    Sergey Akhalkov (sergey-akhalkov)

    on Dec 18, 2017

    Contributor

    More actions

    Hi Prayudi Tirta Bayu (@prayuditb), please take a look at #547 and let's move the discussion to the one common place.
12. ghost locked as resolved and limited conversation to collaborators on Dec 11, 2021