MacOS Proxy Issue

BTW I believe the user feedback related to networking issues is REALLY BAD.
There 2 manifestations: at login time, at startup/sync time.
1/ Login
There is a catch all error handler for any failure to login that displays an error message that may push users to believe they have entered the wrong login info even though it is an network related issue.

My suggestion is to have an error handling that differentiates environmental issues vs user errors and provides different error message very clear on what the user can do to remediate/troubleshoot.
5-6months ago, I just abandonned upgrading to 8beta because I did not have the time to troubleshoot this. Had I known it was not an account version compatibility issues (I had other v7 clients), I would have done the troubleshooting I did this time (my previous messages).

2/ Startup/Sync time
I find very surprising that any network issues encountered during synchronization is not reported by the client app (at least I have not found one on firefox/chrome/macos/ios). I believe hidden failures like that leads the users to start doubting the product. Plus it sometimes leads to more serious issues: I locked myself out of my bank because I tried too many times to log in with out-of-date creds after a password reset on another device.
So we need visible error status and ways to recover it:
a. Clear but non intrusive error message when the sync is not successful (maybe a badge somewhere that indicates it is failing).
b. A way to force sync that will display an explicit error message to help troubleshoot (click on the badge? ).

In addition it would be great to have a way to see the synchronization state of all account/personal devices. You can track what data revisions each client have last pulled, show if the current device/app has unsynched modifications and show the ones that are out-of-date. This would make troubleshooting where the sync failure occurs much easier: i.e. answering which device/app is not synching:
* is it the one I made an update on?
* is it the other one I am trying to use the update on?

Jacques

Duh I am on macos 11.6.7 1password 8.8.0 (80800176)

Same issue here.
If I am not logged in to my work VPN, I can log in and synch works.
As soon as I am connected to my VPN it stops synching and if I force a logout/login, I can't log back in anymore.

In the log I find these errors entries (just starting 1password already logged in):
ERROR 2022-07-05T13:28:16.460 tokio-runtime-worker(ThreadId(7)) [1P:foundation/op-proxy/src/lib.rs:245] proxy test network connection failed: error sending request for url (): error trying to connect: tls handshake eof
INFO 2022-07-05T13:28:16.460 tokio-runtime-worker(ThreadId(7)) [1P:foundation/op-proxy/src/apple.rs:329] skipping proxy returned by PAC since we couldn't connect to it: Network(Network(error sending request for url (): error trying to connect: tls handshake eof))

Interestingly launching from the terminal with no proxy variables has the same outcome.
However if I set manually https_proxy to what my work PAC would return, it works.