-
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
Site Creation > New Site Doesn't Open after Creation #17928
Comments
I tested the appstore version newsite.mov |
I was unable to reproduce this as well, but did see what may be a clue:
@startuptester selected mynewsite.business.blog, but the preview shows mynewsitebusiness.wordpress.com (which redirects to mynewsite.business.blog). 🤔 |
Wow, good find @twstokes! |
That's an interesting find indeed @twstokes! I wonder if we check the site name to see if a new site was created and that leads to the issue in corner cases like this 🤔 |
That sounds quite plausible @antonis! I'll dig and see what I can find. |
@startuptester and @antonis I dug into this issue fairly deeply but was never able to reproduce it. My conclusion was that at the end of the new site creation (which appeared to be successful), the site picker view was never dismissed. Since there has been recent work and refactoring related to this flow, I wonder if we should pause this deep dive until it can be reproduced. If this can be reproduced, please reassign me and I'll be happy to continue troubleshooting. 🙇 |
Thank you for investigating this @twstokes 🙇
I agree to put this issue a side till we have a way to reproduce 👍 |
The ad-hoc site picker after login is no longer in the picture. I think it's safe to assume this is no longer an issue, closing. |
Expected behavior
I expect a newly created site to open after I dismiss Quick Start and I'll see the My Site screen
Actual behavior
It goes back to the site "Choose a site to open." screen
Steps to reproduce the behavior
RPReplay_Final1644464092.MP4
Tested
on iPhone 13 Pro, iOS 15.3, WPiOS 19.1
The text was updated successfully, but these errors were encountered: