Personal Community Mobile Application Upgrade Guide 1. Overview For sites deploying Personal Community as a mobile application, the mobile app must be upgraded alongside the corresponding Personal Community web version. As part of every Personal Community upgrade, sites must: Upgrade the Personal Community web application. Rebuild the iOS and Android mobile applications using the upgraded Personal Community version. Test the updated mobile applications. Republish the updated applications to the Apple App Store and Google Play Store. The updated mobile application should be made available as part of the same upgrade process. If the Personal Community web application is upgraded without rebuilding and republishing the corresponding mobile application, the existing mobile application will no longer function. Organizations should account for mobile application build, testing, app store review, and publishing timelines when planning a Personal Community upgrade. 2. Upgrade Prerequisites Before upgrading the mobile application, ensure that you have: The existing Base-Capacitor-Env build file version used to build the currently published application. This will be used to compare against the target Personal Community version. The mobile app .tgz file corresponding to the target Personal Community version. This file is available from the WRC Software Distribution . Access to the customer-specific Apple and Google developer accounts used to publish the existing application. Access to the existing iOS and Android signing configuration and credentials. If push notifications are enabled, access to the existing customer-specific Firebase and APNs configuration. 3. Review Base-Capacitor-Env Changes Before updating the application, the following version matrix to determine whether the target release requires an updated Base-Capacitor-Env build file. These files are available from the WRC Software Distribution . Personal Community version Base-Capacitor-Env build file version 2025.3 2025.3 2025.4 2025.4 2025.5 No updates - use version 2025.4 2025.6 2025.6 2026.1, 2026.2, 2026.3 No updates - use version 2025.6 2026.4 2026.4 2026.5 No updates - use version 2026.4 If there are no required Base-Capacitor-Env changes, retain the existing customer-specific project used and update the Personal Community mobile application dist only. If Base-Capacitor-Env has changed, incorporate the documented changes into the existing customer-specific project while retaining the site's configuration, including: Bundle identifier/package name Application name and branding iOS and Android application configuration Signing configuration Firebase configuration, if push notifications are enabled APNs configuration, if push notifications are enabled 4. Review Version-Specific Upgrade Considerations Before updating the mobile application, verify that the build environment meets the requirements for the target Personal Community version . Dependency requirements may change between Personal Community releases. When upgrading across a version boundary shown below, update the applicable build tools before rebuilding the application. For complete installation instructions for these dependencies, see Building the Personal Community Mobile Application with Capacitor in the Personal Community Mobile Application Guide. 4.1. Node.js and npm Personal Community Version Node.js npm 2025.5 and earlier 16.19.0 8.19.3 2025.6–2026.3 20.14.0 10.7.0 2026.4 and later 22+ 10.9.8 4.2. iOS Build Requirements Building the iOS application requires macOS. 4.2.1. Xcode and Minimum iOS Version Personal Community Version Xcode Minimum iOS Version 2025.6–2026.2 16.0+ 2026.3 and later 26.0+* 16.0 * The Xcode 26 requirement is based on Apple's App Store submission requirements rather than a Personal Community product dependency. Beginning in April 2026, Apple requires Xcode 26 for App Store submissions. Do not modify the minimum iOS version specified for the target Personal Community release. 4.2.2. CocoaPods Personal Community Version CocoaPods 2025.6 and later 1.16.2 4.3. Android Build Requirements Personal Community Version Android Studio Minimum Android SDK 2025.6–2026.3 Ladybug (2024.2.1) or later 21 2026.4 and later Otter (2025.2.1) or later 21 5. Update the Personal Community Mobile Application Download the Personal Community Mobile .tgz file that corresponds to the target Personal Community version from the WRC Software Distribution, if not yet downloaded. The mobile application version must match the Personal Community web version being installed. Follow the Base-Capacitor-Env ReadMe instructions to replace the existing Personal Community mobile application dist with the files from the new version. 6. Synchronize the Application After updating the Personal Community mobile application files and applying any required Base-Capacitor-Env changes, synchronize the Capacitor project: npx cap sync 7. Building the Upgrade App Distribution The new builds must use the same application identifier as the currently published applications but must have an updated version/build number. 7.1. Apple 7.1.1. Setting the Application Name and Version in Xcode In Xcode, verify the following under the application target's General > Identity settings: Display Name – Retain the existing application name. Bundle Identifier – Retain the existing bundle identifier. Do not create a new identifier for the upgrade. Version – The major version of the published app. Update as appropriate for the new application release. Build – T he minor version of the published app. Increment for the new App Store build. Verify that the existing signing, capabilities, and push notification configuration remain associated with the application. 7.1.2. Confirm App Icons Verify that the existing assets catalog for your app icon remains. 7.1.3. Publishing the App to App Connect In XCode, run the following to publish the app to App Connect Select Project → Archive When this completes, you have the option to Validate App or Distribute App Select Distribute App and choose a distribution model. From App Connect, you can now see this build of the application and can initiate testing, the review process, or publishing. 7.2. Android 7.2.1. Setting the Application Name and Version In android/app/build.gradle , update: versionCode – Increment this value for each release published to Google Play. versionName – Update as appropriate for the new application release. Retain the existing application/package identifier. Do not create a new package name for the upgrade. Verify that the existing signing and Firebase configuration remain associated with the application. 7.2.2. Confirm App Icons Verify that the existing image assets for your app icon remains. 7.2.3. Building and Signing the App In Android Studio: Sync gradle files (File → Sync Project with Gradle Files) Open the Build Variants tool bar View → Tool Windows → Build variants Set Active Build Variant to Release Build the app bundle Build → Generate Signed App Bundle / APK Follow the prompts to sign the application 8. Post-Upgrade Validation Because the upgraded application retains the same bundle identifier/package name, the operating system should recognize it as a new version of the existing application rather than installing a separate application. Validate the following as applicable: The existing application upgrades successfully. The application launches after the upgrade. The patient can sign in. Existing customer branding and configuration are retained. Core Personal Community workflows function as expected. Existing device permissions continue to behave as expected. Push notification configuration continues to function, if enabled.