-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix unresponsive "Onboarding Questions" screen #19791
Fix unresponsive "Onboarding Questions" screen #19791
Conversation
You can test the changes in Jetpack from this Pull Request by:
|
You can test the changes in WordPress from this Pull Request by:
|
bfcced8
to
ac88772
Compare
ac88772
to
5eef2c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This worked great! I also approved wordpress-mobile/WordPressAuthenticator-iOS#719 (review). 🚀
For the pod to get pulled down I had to specify the commit hash rather than the branch. It looks like the branch name is out of sync and still pointing to 98dc0b8 instead of 03e2e89 that was force-pushed.
That should get ironed out once the merging / tagging takes place on the WordPressAuthenticator side.
I'd also consider a release note for this. 👍
690dc78
to
3a11a12
Compare
3a11a12
to
230140d
Compare
Generated by 🚫 dangerJS |
Since this PR was approved and the auto-merged enabled, the I resolved them (with GitHub's web editor, for a change) and am now waiting for the auto-merge to kick in before starting the 21.6 code freeze. |
Fixes #19774
Description
This PR resolves an issue that was causing the user to get stuck in the "Onboarding Questions" screen.
bug.mp4
CleanShot.2022-12-23.at.16.13.01.mp4
Related PR
Test Instructions
Prerequisites
Account Setup
Have an account with at least 2 sites and 2FA enabled.
Simulate Auth Token Issue
WPAuthTokenIssueSolver.m
file and changehasAuthTokenIssues
to returntrue
Regression Notes
Potential unintended areas of impact
None.
What I did to test those areas of impact (or what existing automated tests I relied on)
None.
What automated tests I added (or what prevented me from doing so)
None.
PR submission checklist:
RELEASE-NOTES.txt
if necessary.