-
-
Notifications
You must be signed in to change notification settings - Fork 45
Cancelling config workflow when device isn't compatible #3197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
📝 WalkthroughWalkthroughThe change updates the Sequence Diagram(s)sequenceDiagram
participant User
participant PersonalIdMessageFragment
participant Activity
User->>PersonalIdMessageFragment: Triggers finish() with PERSONALID_DEVICE_CONFIGURATION_FAILED
PersonalIdMessageFragment->>Activity: finish()
Activity-->>User: Activity closes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (1)
✨ Finishing Touches
🧪 Generate Unit Tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
https://dimagi.atlassian.net/browse/QA-7849
Product Description
After showing the user an error message indicating that their device doesn't meet the security requirements for biometric, the configuration workflow will close.
Technical Summary
Finishing the activity instead of navigating to phone fragment.
Note: Popping back to phone would have also fixed the error, instead of navigating forward to phone fragment.
But once we know they can't enroll, might as well drop them back at home
Feature Flag
PersonalID
Safety Assurance
Safety story
Tested by forcing the error in code.
I was able to reproduce the bad behavior before the fix.
Automated test coverage
None
QA Plan
Reported by QA already.