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
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
I was calling fireBase.init() before the application.start() in app.js.
It worked in IOS, but on Android (real device and emulator) it didn't work. The log traced the error to firebase.android.js line 185 com.facebook.FacebookSdk.sdkInitialize(appModule.android.context);. appModule.android.context was undefined/null.
I changed the code to run fireBase.init() after application.start() and it worked.
Is this a Nativescript bug, nativescript-plugin-firebase bug or just expected behaviour?
The text was updated successfully, but these errors were encountered:
Can you test whether the current version on GitHub fixes the problem for you?
I'm not entirely comfortable with calling init before app start (you need to require the plugin before app start, not init), but I'd like to make it work also for your scenario nonetheless.
I was calling fireBase.init() before the application.start() in app.js.
It worked in IOS, but on Android (real device and emulator) it didn't work. The log traced the error to firebase.android.js line 185
com.facebook.FacebookSdk.sdkInitialize(appModule.android.context);
.appModule.android.context
was undefined/null.I changed the code to run fireBase.init() after application.start() and it worked.
Is this a Nativescript bug, nativescript-plugin-firebase bug or just expected behaviour?
The text was updated successfully, but these errors were encountered: