[firebase/auth]: ISPs blocking connection with gRPC on Windows #17087
Labels
Needs Attention
This issue needs maintainer attention.
platform: windows
Issues / PRs which are specifically for Windows.
plugin: auth
type: enhancement
New feature or request
Is there an existing issue for this?
Which plugins are affected?
Auth
Which platforms are affected?
Windows
Description
I discovered that the Windows version uses the Firebase C++ SDK for authentication, and this SDK communicates via gRPC.
The problem is that the network is blocking this communication. Initially, this only happened on corporate networks, but now it is also occurring with some ISPs in my region.
All other libraries work fine.
I saw that the web was also having issues with this, and a change was made to support REST instead of gRPC.
Wouldn't it be possible to configure it in some way to prefer this method in the Firebase initialization settings?
It would be very interesting if, just like the Web platform support, the Windows version allowed authentication via REST, using the RestTransport instead of GRPCTransport (I saw this on FirebaseDataConnect class), which works correctly on any network.
I created a brand new project to test only the auth lib and it happened as well.
Reproducing the issue
Unfortunately, the only way to reproduce this is in an environment where this network blocking issue occurs.
The only message we get when trying to use it is:
[firebase_auth/unknown-error] An internal error has occurred.
This happens when attempting to use any function from the authentication library.
I could arrange remote access if necessary to perform these checks.
Everything was working perfectly. I also use the cloud_store and storage libraries. The issues I found, I reported, and they were promptly fixed. Since then, I hadn't encountered any other problems. However, this one is really serious because it completely blocks the use of the framework on this platform.
One observation is that after successfully connecting using a VPN, for example, and then disconnecting, it continues to work. It seems like a token or something is stored and maintained after this successful connection.
Firebase Core version
3.11.0
Flutter Version
3.27.4
Relevant Log Output
Flutter dependencies
Expand
Flutter dependencies
snippetAdditional context and comments
No response
The text was updated successfully, but these errors were encountered: