-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebase Analytics issue on angular 11 #2672
Comments
Same here but for me it was not AG 11 but angular fire > 6.0 |
6.1.0-rc.4 and above causes this |
What do you DI tokens look like? If rc.4 introduced this it sounds like it's the object comparison on the instance settings (I just did |
Getting the same error also. |
@jamesdaniels nothing was changed so far on the consumer side. DI tokens are imported as they used to. |
Understood, but are any of the DI tokens your providing to AngularFire objects that aren't serializable with |
I'm having the same issue. Nothing changed on my side. I'm using a configuration as provided by Firebase. Not using any DI.
|
I have this same issue in the latest angularfire and none of my analytics events are being logged anymore. I am not using any custom DI for analytics |
I have the same issue on Angular 10 and "@angular/fire@6.1.0, during lazy loading of my module.
Does anyone a have workaround? |
Cutting |
Version info
Angular:
Angular 11.0.1
Firebase:
8.0.2
AngularFire:
6.1.1
Other (e.g. Ionic/Cordova, Node, browser, operating system):
Ionic/Cordova, Mac os
How to reproduce these conditions
Try calling below code in one of the pages
const userInfo = { email: 'myemail@google.com'}
await this.angularFireAnalytics.setUserProperties(userInfo);
Failing test unit, Stackblitz demonstrating the problem
Steps to set up and reproduce
Sample data and security rules
Debug output
** Screenshots **
![image](https://user-images.githubusercontent.com/5780117/99662496-57652800-2a8b-11eb-860f-05aca282ee6f.png)
Expected behavior
Actual behavior
It was working earlier on 10.2.x, after upgrading to Angular 11 it is not working.
The text was updated successfully, but these errors were encountered: