You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would appreciate your feedback if you have any. Here is the description of the issue we just started seeing with our commercial app in the Stores:
Using MS AppCenter in the past, we have successfully performed CodePushes on our both our iOS and Android app builds (written with Ionic on Cordova) that reside in the Apple and Google Stores, including a December 19, 2019 (target version 2.18.1) and January 27, 2020 (target version *) CodePush noted in our App Center account.
When we chose to do a new CodePush yesterday, September 21 (target version *), for either iOS or Android, we experienced the following steps:
The app did not recognize the update if the user was already logged in from a prior session (V2.18.1 noted in the app info)
When the user logged out of the app, killed the app (swipe up), restarted the app and logged in, CodePush was recognized and completed the update (V2.33.0 noted in the app info – correct update)
User logs out and kills the app, or just kills the app and restarts it, the app reverted back to V2.18.1 again with no user interaction
Subsequent log outs and restarts of the app still remained at V2.18.1 and no prompts for CodePush ever came back a second time
Thank you!
The text was updated successfully, but these errors were encountered:
We would appreciate your feedback if you have any. Here is the description of the issue we just started seeing with our commercial app in the Stores:
Using MS AppCenter in the past, we have successfully performed CodePushes on our both our iOS and Android app builds (written with Ionic on Cordova) that reside in the Apple and Google Stores, including a December 19, 2019 (target version 2.18.1) and January 27, 2020 (target version *) CodePush noted in our App Center account.
When we chose to do a new CodePush yesterday, September 21 (target version *), for either iOS or Android, we experienced the following steps:
Thank you!
The text was updated successfully, but these errors were encountered: