-
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
upgrade to angularFire 7.0.3 and 4 new error #2929
Comments
This issue does not seem to follow the issue template. Make sure you provide all the required information. |
The format has changed. |
@tja4472 is correct. In 7.0 we broke the This seems trivial and annoying but means we no longer have to take feature requests and cut minor releases when the auth SDK adds new options to the useEmulator function. |
just for reference, changing as suggested solved the issue |
Second, confirm. Docs should be updated. I can make a PR if you'll like. https://github.com/angular/angularfire/blob/master/docs/emulators/emulators.md |
According to the issue the format of USE_EMULATOR have changed. angular/angularfire#2929 (comment) This seems to have broken FirebaseUI-Angular in that it can no longer connect to the emulator. This change fixes the issue. However it is not backwards compatible which I don't know if it is a requirement.
According to the issue the format of USE_EMULATOR have changed. angular/angularfire#2929 (comment) This seems to have broken FirebaseUI-Angular in that it can no longer connect to the emulator. This change fixes the issue. However it is not backwards compatible which I don't know if it is a requirement.
I had to use the following in my
|
An error after upgrading firebase & angularFire (still using the compat library :)):
Any idea?
**Angular: 12.2.0
**Firebase: 9.0.1
**AngularFire: 7.0.3 and 7.0.4
Other (e.g. Ionic/Cordova, Node, browser, operating system):
node 14
windows 10
chrome
How to reproduce these conditions
Failing test unit, Stackblitz demonstrating the problem
error when looking in chrome devtools:
Emulator URL must start with a valid scheme (http:// or https://). (auth/invalid-emulator-scheme).
code in app module:
The text was updated successfully, but these errors were encountered: