feat: implement app version auto-update mechanism - #574
Merged
RUKAYAT-CODER merged 1 commit intoJun 25, 2026
Merged
Conversation
|
@collinsezedike Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Closes #356.
Adds an in-app update system that checks for new versions on startup and prompts users to install with one tap, satisfying all acceptance criteria:
AppUpdateService.checkForUpdate()runs on mount viaUpdateCheckerin the root layout. A 24-hour interval guard (shouldCheck()) prevents redundant calls on every launch.UpdateNotificationModalrenders an accessible modal with the update description and optional release notes. Mandatory updates block dismissal.fetchUpdateAsync()thenreloadAsync()viaexpo-updates(dynamically imported, so the app won't crash before the package is added to a native build). Native/binary changes fall back to a "Open App Store / Open Play Store" path using the store URLs already defined inapp.json.mobileAnalyticsService.trackEventfires on every stage: check started, update available/not available, download started/completed/failed, update applied, dismissed, and store redirect. Nine newUPDATE_*events added toAnalyticsEvent.appUpdateService.test.ts(10 cases) anduseAppUpdate.test.ts(9 cases) cover all state transitions, error paths, platform branching, and the mount-time auto-check.Key files
src/services/appUpdateService.tssrc/hooks/useAppUpdate.tssrc/components/common/UpdateNotificationModal.tsxsrc/__mocks__/expo-updates.tsapp/_layout.tsxUpdateCheckercomponent wired into the provider treeapp.jsonexpo-updatesplugin,updatesconfig,runtimeVersionpolicysrc/utils/trackingEvents.tsUPDATE_*analytics eventsNotes
expo-updatesis not yet inpackage.json(package installation was deferred). It needsnpx expo install expo-updatesbefore the next native build. The dynamic import means existing JS bundle runs are unaffected until then.src/services/index.tsfile had stale merge-conflict prose as its content; that was corrected as part of this PR.