The app source is in expo/. iOS release: 3.0.0 (5).
Double-click Open TapMiles in Xcode.command in this folder. It opens the CocoaPods workspace, including both the app and Pods projects.
Do not archive TapMilesMileageTracker.xcodeproj on its own. It omits dependencies and can produce hundreds of cascading Clang errors, including a missing EXConstants.modulemap.
The native build also removes FinderInfo/resource-fork metadata from the generated app before signing, preventing the resource fork, Finder information, or similar detritus not allowed CodeSign failure (Apple QA1940). The cleanup runs after CocoaPods copies resources, including after a fresh prebuild.
In the workspace, select TapMilesMileageTracker → Any iOS Device (arm64), keep your existing signing team, then Product → Archive. Archive uses Release and embeds JavaScript; Metro is only needed for Debug development.
From the repository root:
node scripts/archive-ios.cjs
python3 scripts/verify-ios-archive.py /path/to/your.xcarchive
The archive helper always selects the workspace and synchronizes Xcode version/build settings with expo/app.json. --unsigned is only a compiler check, not an uploadable archive. Signed archives go to the standard ~/Library/Developer/Xcode/Archives folder; DerivedData also stays under Library, outside iCloud-synced Documents. TAPMILES_ARCHIVE_DIR and TAPMILES_DERIVED_DATA_DIR override those paths for CI. Unsigned checks go to work/. Generated native projects and archives stay out of Git.
When starting from a fresh clone, install Node.js and dependencies, then generate native iOS first:
cd expo
pnpm install --frozen-lockfile
pnpm exec expo prebuild --platform ios
The signed archive must still be distributed through Xcode Organizer and reviewed by Apple. Hermes is compiled from the RN-pinned source tag so its matching dSYM contains real DWARF symbols. Archive validation rejects missing or mismatched framework symbols.
Run npm run typecheck, npm run lint, and npm test inside expo/. The tests cover tracking, persistence, export escaping, archive workspace selection, signing mode, and prebuild version settings.
See store-assets/app-store/v3.0/UPLOAD-GUIDE-PL.md for screenshot, iPhone Duo, Header and Search Results upload instructions.
Build 5 enables RCT_BUILD_HERMES_FROM_SOURCE=true in the generated Podfile. CMake must be available when installing Pods, and the matching source-built Hermes compiler is used for the JS bytecode. To install the tested CMake version without changing system packages, run from this repository root:
python3 -m pip install --target work/ios-build-tools -r tools/ios-build-requirements.txt
export PATH="$PWD/work/ios-build-tools/cmake/data/bin:$PATH"
cd expo
pnpm exec expo prebuild --platform ios --no-install
cd ios
pod update hermes-engine --no-repo-update
For a fresh installation, pod install also works. When changing an existing binary-based installation, update the Hermes pod to invalidate CocoaPods’ cached specification. The dSYM build phase uses the unstripped source-built framework and puts the symbols in the archive; it fails if its input is missing. verify-ios-archive.py checks UUID equality and actual DWARF compilation units. Never rename a dSYM or modify a UUID to match another binary.
The first source build takes longer. Keep each archive’s original symbols with it; build 5 symbols cannot repair build 4 because the binary UUID changes. Source-building the engine follows React Native’s Bundled Hermes documentation.
The host Hermes compiler is configured as Release during CocoaPods integration, matching the production compiler configuration. Generated native dependencies are excluded from application TypeScript and ESLint scans.
Android uses versionName 2.5, versionCode 5; iOS remains 3.0.0 (5). The Android config plugin preserves the separate version through prebuild. The location disclosure appears before recording or permission requests, including for users upgrading with existing permissions; background access has its own explanation directly before its system request. Declining background access keeps foreground recording available.
On this Mac, quit Android Studio and use Open TapMiles in Android Studio.command to include Node.js and JDK 21/17 in its environment. The launcher supplies a project-local 4 GB Studio heap to prevent indexing the native dependencies from exhausting the default 2 GB heap. After expo prebuild --platform android --no-install, open expo/android.
Release signing reads a private Java properties file via TAPMILES_SIGNING_PROPERTIES. It must contain storeFile (absolute keystore path), storePassword, keyAlias, and keyPassword. Keep that file and the keystore outside version control. Release never falls back to the debug key.
cd expo/android
NODE_ENV=production ./gradlew :app:bundleRelease --max-workers=4
The AAB is app/build/outputs/bundle/release/app-release.aab. For an existing Play App Signing app whose upload key is lost, register the new public PEM certificate through the Play Console upload-key reset process before uploading a bundle signed by the replacement key. See Google’s signing guidance.
GPS recording does not require enabling Google’s optional network Location Accuracy service. Native watches disable that optional settings dialog after checking that device location services are available.