You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected tapping "Log in" prompt in Stats to allow me to connect my site and load stats.
Actual behavior
When the Jetpack Plugin is in a site-only connection state, tapping "Log in" results in a login loop. I am able to complete the login flow, but the account is not connected and I cannot view stats.
Steps to reproduce the behavior
Create a new self-hosted site, and get it into site-only state by:
From wp-admin on the web, install the Jetpack Plugin, and activate it.
Still in wp-admin, tap "set up" for the Jetpack Plugin, but don't complete the process. When you see "Connecting as...", don't tap "Approve," instead press the back button.
You'll now see the following in wp-admin > Jetpack, towards the bottom:
In the app, add your self-hosted site. I did this while already logged into a WordPress.com account on the app.
Once added, tap "Stats" and note you see the "Log in" prompt.
Tap "Log in" and go through the login flow for your WordPress.com account.
Once the login flow is complete, note Stats still shows the "Log in" prompt.
loginloopios.mov
Tested on iPhone 12 mini, iOS 15.7, JPiOS 21.0
The text was updated successfully, but these errors were encountered:
staskus
changed the title
Stats: Log In fails when Jetpack Plugin is in site-only connection state
Jetpack Install: Log In fails when Jetpack Plugin is in site-only connection state
Jan 19, 2023
Expected behavior
Expected tapping "Log in" prompt in Stats to allow me to connect my site and load stats.
Actual behavior
When the Jetpack Plugin is in a site-only connection state, tapping "Log in" results in a login loop. I am able to complete the login flow, but the account is not connected and I cannot view stats.
Steps to reproduce the behavior
loginloopios.mov
Tested on iPhone 12 mini, iOS 15.7, JPiOS 21.0
The text was updated successfully, but these errors were encountered: