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
Analytics: Firebase Analytics is not supported in this environment. Wrap initialization of analytics in analytics.isSupported() to prevent initialization in unsupported environments. Details: (1) Cookies are not available. (analytics/invalid-analytics-context).
From what I have read, safari blocks third party cookies in iframes.
We will not be able to do anything about this.
my question is, what is the correct way to initialize firebase so this error goes away.
how can I call isSupported in the provide, since it's async?
One strange thing I also found is that if I inject the Analytics service when the initialization fails, it's not undefined but instead an empty object / class.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Error:
From what I have read, safari blocks third party cookies in iframes.
We will not be able to do anything about this.
my question is, what is the correct way to initialize firebase so this error goes away.
how can I call isSupported in the provide, since it's async?
I'm using firebase 9 and the new modular way.
my current config looks like this.
Analytics is an object
One strange thing I also found is that if I inject the
Analytics
service when the initialization fails, it's not undefined but instead an empty object / class.I would think that if the initialization fails because of isSupported = false that the injected service would be undefined or null.
Maybe it has to do with how angular fire wraps the firebase Analytics in a class?
https://github.com/angular/angularfire/blob/master/src/analytics/analytics.ts#L10-L14
Beta Was this translation helpful? Give feedback.
All reactions