Merged
Conversation
Contributor
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
tommasini
approved these changes
Mar 17, 2023
Contributor
tommasini
left a comment
There was a problem hiding this comment.
Thanks for pinging me to review this!
Just reinforced the need for testing on outside the navigation object screen
LGTM!!
f937a69 to
98e89c3
Compare
Contributor
Author
|
Just rebased |
Contributor
Author
|
@chrisleewilcox @cortisiko This issue might also be related to another one that Kat posted in Slack. If we have the bandwidth, could we quickly verify it as well? |
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes both the padding issue + interaction of the SRP reveal screen bug found in 6.2.0 regression
https://app.zenhub.com/workspaces/mobile-release-regression-6249e5242464b70013315a98/issues/gh/metamask/mobile-planning/720
Screenshots/Recordings
Reach out to @Cal-L for videos
Testing
There are three main scenarios that the reveal credentials screen affects (the first 3 scenarios. 3 and 4 are essentially the same scenario)
Scenario: Should be able to recover SRP when something errors out on the Root boundary
Scenario: Should be able to recover SRP when something errors out on the Activity boundary
Scenario: Should be able to reveal SRP from the settings flow
Scenario: Should be able to reveal private key from the settings flow
Checklist