Expected behavior

When logging in with a site address for an Atomic or Jetpack site, I'd expect to be logged into their associated WP.com account at the end of the flow.

Actual behavior

Instead, I'm either unable to login or they behave just like self-hosted sites, not allowing me, for example, to access Stats and Notifications or to see other sites associated with the same WP.com account.

Steps to reproduce the behavior

0. Clear app data.
1. On the Prologue screen, if the Smart Lock dialog appears, dismiss it.
2. Tap Enter your site address.
3. On the Site Address screen, enter either a Jetpack or an Atomic site address*.
4. Tap Continue.
5. Notice the Username/Password screen.
6. Enter the username and password associated with the site**.
7. Tap Continue.
8. Complete the login flow normally.
9. On the Epilogue screen, notice how it doesn't display any other site associated with the same WordPress.com account.
10. Tap Done.
11. On the Main screen, tap Notifications.
12. Notice how it shows the "Install Jetpack" button.

* Private Atomic sites will fail with an error here, which is also not expected.

** Using WP.com credentials here won't work, which is another problem related to this. For a Jetpack site, it's possible to use site credentials (the same used to login to wp-admin), but 2FA won't be supported then (just like with self-hosted sites). As for Atomic sites, site credentials need to be generated via wp-admin > Users > All Users > Select User > Generate Password.