Skip to content
This repository was archived by the owner on Apr 4, 2023. It is now read-only.

Firebase Analytics is listed as missing dependency #1416

Closed
Lehren opened this issue Sep 26, 2019 · 5 comments
Closed

Firebase Analytics is listed as missing dependency #1416

Lehren opened this issue Sep 26, 2019 · 5 comments

Comments

@Lehren
Copy link

Lehren commented Sep 26, 2019

I have only installed Firebase In App messaging and Firebase Cloud Messaging and upon running the app, I get the following error

java.lang.RuntimeException: Unable to get provider com.google.firebase.provider.FirebaseInitProvider: com.google.firebase.components.MissingDependencyException: Unsatisfied dependency for component Component<[class com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay]>{2, type=0, deps=[Dependency{anInterface=class com.google.firebase.FirebaseApp, type=required, direct=true}, Dependency{anInterface=interface com.google.firebase.analytics.connector.AnalyticsConnector, type=required, direct=true}, Dependency{anInterface=class com.google.firebase.inappmessaging.FirebaseInAppMessaging, type=required, direct=true}]}: interface com.google.firebase.analytics.connector.AnalyticsConnector

I am running version 10.0.0 and you have stated Analytics can be an optional dependency. Doesn't seem to quite work yet.

@EddyVerbruggen
Copy link
Owner

Interesting, so I guess FirebaseInAppMessagingDisplay still internally depends on Analytics in the Firebase Android SDK.

I guess for the time being adding this (but true) and running rm -rf platforms node_modules should get you going again.

@n0mer
Copy link

n0mer commented Sep 26, 2019

@EddyVerbruggen , does this plugin support yarn? I've got package-lock.json file created after running rm -rf platforms node_modules and then tns run android

@EddyVerbruggen
Copy link
Owner

@n0mer I'm not sure what that has to do with this issue, but AFAIK no.

@kdiehl
Copy link

kdiehl commented Sep 26, 2019

I solved a lot of problems by running npm install and then deleting package.lock etc.
and running yarn again. (Does not feel very good but seems to work somehow)

@n0mer
Copy link

n0mer commented Sep 26, 2019

@EddyVerbruggen you are right, this is sort of side-effect to this issue. Discovered it after applying fix with "analytics: true" in config file, removing node_modules & platforms. Though you might find this information helpful in case some other yarn user would try this fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants