You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IOS seems to proxy traffic for "tracking domains" to get around IP tracking, I believe apis.google.com is on their list. This causes the network request to be routed through their internal VPN service which potentially doesn't work well with IPV6.
*Apple potentially uses a second (more aggressive) VPN service for their customers subscribed to iCloud+, we believe this to be pertinent to the issue but aren't sure.
This network request is only made either during proactive initialisation or logging in with a popup, such as OAuth through google or Facebook, and it causes our project to hang or fail because we're forced to wait for the network request to complete.
Disabling proactive initialising solves this issue, and we have a workaround, but would prefer a more official way to accomplish this.
Steps to reproduce:
Enable "limit IP address tracking" on an iPhone (possibly enabled by default)
We're seeing the script load fail, it times out after some time but only under the conditions in the issue. Our project depends on auth being init'ed so the whole thing fails to load when this request is made.
We've already worked around it by disabling proactive init, which prevents the request from being made until a user tries to sign in with a popup, but we're forced to do this by modifying the auth package which isn't ideal.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Possibly related to #7012
IOS seems to proxy traffic for "tracking domains" to get around IP tracking, I believe apis.google.com is on their list. This causes the network request to be routed through their internal VPN service which potentially doesn't work well with IPV6.
*Apple potentially uses a second (more aggressive) VPN service for their customers subscribed to iCloud+, we believe this to be pertinent to the issue but aren't sure.
This network request is only made either during proactive initialisation or logging in with a popup, such as OAuth through google or Facebook, and it causes our project to hang or fail because we're forced to wait for the network request to complete.
Disabling proactive initialising solves this issue, and we have a workaround, but would prefer a more official way to accomplish this.
Steps to reproduce:
Workaround
Disable
BrowserPopupRedirectResolver:_shouldInitProactively
sed -i.bak 's/return _isMobileBrowser() || _isSafari() || _isIOS();/return false\/*Force disabling due to ios tracking bug*\/;/g' node_modules/@firebase/auth/dist/esm2017/index-*.js
Preferably, there should be a call to disable proactively initialising, such as
The text was updated successfully, but these errors were encountered: