According to the article What Are “Binary Compatible Changes”?, the Live Update feature only works on binary compatible changes which makes sense. If we, for example, install and implement a new plugin we want the native changes + web changes to be deployed/available at the same time.
Now how does Live Update works in consecutive deployments of binary compatible changes and not binary compatible changes?
For example, If I deploy a not binary compatible change and then deploy a binary compatible change (web-only change), will the second deployment be blocked from using Live Update since a native app takes time to be approved in app stores?
Thanks in advance!
1 post - 1 participant