Live Update always fires rollback (v6) #517
Replies: 3 comments 2 replies
-
|
You have to call the "ready" method as soon as possible directly at app start. Feel free to share code if you want. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Robin, thanks for answering. Even when I set a timeout in order to make sure "sync" gets called later than "ready", I am still having the same problem. Should "ready" event fire a log in LogCat that I can search for? I will try to make a repro. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, what made all of this clear for me is that "sync" result will be null if the app is up to date. This fixed my loop problem, thanks once again for responding. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have a feeling that I'm doing something wrong while trying to implement Live Update.
Even though I call LiveUpdate.ready() before setting the new version, the application constantly tries to rollback which fires a reload. And then after the reload the whole cycle happens again - setting next bundle, reloading ... and rollback.
I am unsure what I am doing wrong. The following code is what is being executed every time the app starts:
Also capacitor.config is:
LiveUpdate:{ readyTimeout:10000, resetOnUpdate:false }In LogCat I am getting "App is not ready. Rolling back to default bundle."
Unsure if I am doing something wrong because I am using v6 of the Plugin, and there's guide only for v7 afaik. Help would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions