When I view a post in a webview from the Reader while logged in to a WordPress.com account, I expect to be authenticated in the webview.
When I view a post in a webview from the Reader, if the post is on a site with a *.wordpress.com address I'm authenticated. But if the site has a custom domain, even if it's hosted on WordPress.com I'm not authenticated in the webview. I see it as it I'm logged out of my WordPress.com account.
@rachelmcr I'm getting a related issue. It seems to have gotten worse. 馃槵 Now, I'm getting a _"The password field is empty"_ error when I view a *.wordpress.com site.

I tested this on production (12.1.2), develop (2d20deb27d527da685a7578baf2fadae224f0ae7), and 12.0. I deleted the app from the device (Pixel 3, Android 9) before testing. It happens on all versions.
Does this look familiar?
As for the first issue you mentioned, it looks like we tried to fix this in #5742. @oguzkocer, can you please confirm if the issue is the same as #5742? If they are the same, would you mind sharing some background or some advice on how to solve this?
Now, I'm getting a "The password field is empty" error when I view a *.wordpress.com site.
Whoa, that's very weird. I haven't seen that before that I can recall, and I can't reproduce it now on alpha-164 (fresh install on device - moto e5 play, Android 8.1) or develop (2d20deb) on a simulator (Pixel 2, Android 9). I'm not sure what's going on there for you.
Tested and confirmed that the comment form does not recognize me as a logged-in user when I go to Reader and tap "Visit" for posts on sites with custom domains (including free .blog domains) even though I am logged in to WordPress.com in the app.
Note: it works as expected in Reader for .wordpress.com domains or if you browse to a webview via Site > Blog Posts > View.

Tested with WPAndroid alpha-173 (12.6 alpha) on Pixel 3 Android 9 for https://wibblywobblytimeywimey.travel.blog/2019/06/14/dorayaki/
Note: The solution applied here - allowing cookies for 3rd party sites, might fix the issue.
This should be fixed by #10588 which sends now authentication details when opening a site with custom domain that has isWP == true
Most helpful comment
This should be fixed by #10588 which sends now authentication details when opening a site with custom domain that has
isWP == true