-
Notifications
You must be signed in to change notification settings - Fork 932
Runtime Error: instance.INTERNAL.registerService is not a function #2420
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
Comments
I found a few problems with this issue:
|
Same error message here also since 7.5.1 on Ubuntu 19.10, Node v12.13.1, TypeScript 3.7.3. |
How did you upgrade firebase? It seems that you upgraded |
@Feiyang1 same as always - npm i firebase. |
Ah I see. I think |
Thanks for the tip @Feiyang1, uninstalling and installing both resolved the issue. I supposed NPM had messed up something in the lock file. I'm closing this now. |
Unlinke @zarko-tg I have a firestore error: function configureForFirebase(firebase) {
firebase.INTERNAL.registerService('firestore', function (app) { return new Firestore(app); }, shallowCopy(firestoreNamespace));
} …but I'm using an experimental build of firestore to get offline persistence in web workers. It may be incompatible with the new firebase versions, I'm going to ask @thebrianchen if he can update the build. |
@laurentpayot Yep. That should solve your problem. |
Yep. Problem solved. Thanks! |
Getting the same error as well:
Uninstalling and installing doesn't solve the issue for me. I've tried importing the storage both from the main firebase package ("firebase": "^5.8.0",) and from the stand alone packages ("@firebase/app", "@firebase/auth", "@firebase/firestore", "@firebase/storage"). As soon as I import the storage package I get that error. I'm on Ubuntu 18.04.3 LTS using firebase for a Vue 2.6.10 project built with vue-cli 4. Stack Trace:
|
@ioanmeri did you try a full |
Thank you @laurentpayot |
The library became unusable since 7.5.1 on an existing Ionic 3 project. Typescript is at 2.8.4.
The text was updated successfully, but these errors were encountered: