1Password 8.10.34 loads slowly in the network environment in mainland China.

Hello @TanMusong! 👋

I'm sorry that there's a delay when opening items in 1Password on your Android device. The team has been investigating an issue with 1Password loading items slowly in certain geographic areas and I'd like to ask a few questions to better understand that issue you're running into:

1. Did you notice the slowness before updating to version 8.10.34? Or is it new to this version on your device?
2. If you have access to a VPN/proxy, does the slowness still occur when connecting through that VPN/proxy?
3. How did you determine that "play-fe.googleapis.com:443" is timing out? Are you using a specific network appliance to confirm this? Can you post a screenshot showing this data from that network appliance?

-Dave

ref: dev/core/core#23888

Same here in China too...It worked fine in EU, in China it doesn't work... See my other post a few mins ago....

I'm sorry to hear about the issue, @StJust. I've replied to you in the other forum post here: https://1password.community/discussion/comment/713699/#Comment_713699.

I look forward to hearing from you.

-Evon

@1P_Dave
Are you from 1password's customer service team or development team?
This problem has been around for almost a year.
I've seen this being told to be a known issue, why hasn't it been fixed for so long? I have also reported it and sent a report, but it has not been resolved.
Googleapis.com, which is similar to Google's API address, cannot be directly accessed in China. I think we should communicate with the development team. If googleapis.com cannot be connected properly on Android phones, will it directly destroy the user experience? Since there is an offline mode, why is it not available? Or is it all fake on Android phones and must be online?
But I think this should at least be based on the availability of 1password API access rather than the availability of Google API access.

@mikuo

If you've previously sent a report my recommendation would be to continue the conversation with the email team. That way they can always look at past conversations. We do not have any direct knowledge of conversation you've had with the team unless you share those detail with us.

As Dave mentioned this issue is on the teams radar. I'm sorry it has not materialized just yet.

@1P_Tommy
The response I got was:
They have added this ticket reference to the open issue.But They don't have an exact timeframe for when this issue will be resolved.

Judging from the timeline of another post, this problem has existed for almost a year.

I hope it can be fixed as soon as possible, because this problem has existed for a long time, and affected users including me have provided some relevant logs.This problem has a great impact on the user experience.

Correct, we generally do not give time frames or estimates on a resolution. It's always been that way, as long as I have been a user which is ~16 years now. That's due in part to a proposed resolution may not work and we'll have to go back to the drawing board. Things like that.