* feat: update particular circuit type
* feat: script to build single circuit
* feat: update single circuit build artifact
* feat: support for multiple circuit name build
* wip
* move colors
* sort the dev screen menu alphabetically. for sanity
* lint
* move country hooks to sdk
* added peer dep
* add as dev dep
* remove SelfMobileSdk component before someone thinks that it should be used
* mock it like before
* chore: bump iOS build number to 179
* fix: use PR source commit for deployment to get correct version.json
When deploying from a PR merge (e.g., dev → staging), now uses the source
branch's commit instead of always checking out staging. This ensures
version.json has the correct bumped build number from the previous
deployment's PR back to dev, preventing 'build number already exists' errors.
* downgrade to match store
* fix: use merge_commit_sha instead of head.sha for deployments
Use github.event.pull_request.merge_commit_sha instead of head.sha to ensure
we deploy exactly what landed on staging after the merge, not just the source
branch state. This correctly handles:
- Conflict resolutions made during merge
- Any staging-only changes
- The actual state of staging post-merge
The merge commit still includes the updated version.json from the source
branch (e.g., dev), so build numbers remain correct while ensuring we deploy
and tag the true staging state.
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
---------
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
* chore: bump iOS build number to 179
* fix: use PR source commit for deployment to get correct version.json
When deploying from a PR merge (e.g., dev → staging), now uses the source
branch's commit instead of always checking out staging. This ensures
version.json has the correct bumped build number from the previous
deployment's PR back to dev, preventing 'build number already exists' errors.
* downgrade to match store
* fix: use merge_commit_sha instead of head.sha for deployments
Use github.event.pull_request.merge_commit_sha instead of head.sha to ensure
we deploy exactly what landed on staging after the merge, not just the source
branch state. This correctly handles:
- Conflict resolutions made during merge
- Any staging-only changes
- The actual state of staging post-merge
The merge commit still includes the updated version.json from the source
branch (e.g., dev), so build numbers remain correct while ensuring we deploy
and tag the true staging state.
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
---------
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
* Enable WebSocket connections in demo client
* save working keychain
* save wip
* save polish tweaks
* downgrade react-native-svg
* abstract components
* onSuccess alert displays only once
* sort by registered first
* add clear all documents button
* formatting and typing
* refresh register document screen after successful registration
* fix double tap on register
* coderabbit feedback
* lock NFCPassportReader to commit
* remove react native picker
* remove lock
* minor fixes
* Add LoadingUI and DevLoadingScreen components for enhanced loading experience
- Introduced LoadingUI component with customizable animation, action text, and progress indicators.
- Created DevLoadingScreen to facilitate development testing with state selection and loading feedback.
- Updated navigation to include DevLoadingScreen in the dev tools.
- Adjusted loading screen logic to improve user experience during document processing.
- Enhanced loading text management to provide clearer feedback based on current state.
- Added new SVG icon for the loading UI.
This commit improves the overall loading experience in the app, making it more user-friendly and visually appealing.
* Update navigation tests to include DevLoadingScreen for improved development experience
* create nice structure for the mobile sdk
* spv
* actually dont touch what we dont understand
* fix metro
* fix pretty
* fix types on app and imrpove names
* sneek in actually checking the types in the mobile app.
* not yet
* fix jest imports and name test better
