Flutter Android/iOS wrapper for cipherwill.com/app. Email/password, Google and Apple sign-in stay native. After sign-in, a small bridge restores the same Firebase account in the web client. Onboarding, email verification, encryption factors and all application features run in the existing web client. Web logout also signs out the native account.
The native vault, storage, people, settings, billing, support, updates, crypto, generated GraphQL operations and related tests/tooling have been removed.
Use Flutter stable 3.41.4, Dart 3.11.1, Java 17 and an Android SDK.
Minimum targets remain Android 9/API 28 and iOS 16. iOS builds require macOS,
Xcode and CocoaPods. Flutter is installed at C:\flutter\bin on this workspace.
- Run
flutter pub get. - Firebase registrations for
project-cipherwillandcom.cipherwill.appare committed. To regenerate them, run./tool/configure_firebase.ps1, then the Firebase/Google synchronization scripts intool/. - Copy a
config/*.example.jsonto the matching ignored environment JSON. SetAPI_URLto the existing GraphQL endpoint for native password resets. Leave Firebase overrides empty to use the registered FlutterFire options. - Run
flutter run --dart-define-from-file=config/production.json.
The wrapper always loads the production web app. With no build overrides, password resets use its public production API endpoint. Google client IDs are synchronized from the committed native Firebase registration.
Deploy the backend token-exchange route and companion web authentication adapter before distributing this mobile build. The previous deployed web client cannot read the new bridge. See authentication bridge.
flutter analyzeflutter test lib testnode tool/check_source_rules.mjs --formatnode --test tool/release_*_test.mjs tool/android_signing_test.mjsflutter build apk --debug
GitHub Actions validates the wrapper and builds Android/iOS artifacts. Signed Android APK/AAB builds still use release commits; see release instructions. Physical-device Firebase providers, WebView uploads/downloads, web encryption factors, Android back navigation and iOS compilation require device acceptance.