Skip to content

Conversation

@ahmed-tarek-salem
Copy link
Contributor

No description provided.

@sallymoc
Copy link
Contributor

@ahmed-tarek-salem can you please add in the readme the information how this works

@ahmed-tarek-salem
Copy link
Contributor Author

@sallymoc

Done, and I will update that again after moving the endpoint to static qubic

@sallymoc
Copy link
Contributor

@ahmed-tarek-salem
The popup approach might not work for force updates with breaking changes - old code could crash before the popup is shown. For example: backend endpoints removed or changed, API responses in a new format the old code can't parse, or library incompatibilities with newer OS versions. Most apps use a full-screen blocker that runs at app launch, before loading any screens, to ensure the update prompt shows before any potentially broken code executes. If the app crashes when returning from background, that's unavoidable since old code is already in memory - but the next launch will show the update screen.

@sallymoc
Copy link
Contributor

@ahmed-tarek-salem should we close this PR and only work on the #586 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

To define a strategy and to implement flexible and forcing upgrade app functionality

2 participants