Closed joshmossas closed 3 years ago
I'm getting a similar behaviour on Angular but using NS7
{
"using_ios": true,
"using_android": true,
"analytics": true,
"firestore": true,
"realtimedb": true,
"authentication": true,
"remote_config": false,
"performance_monitoring": false,
"external_push_client_only": false,
"messaging": false,
"in_app_messaging": false,
"crashlytics": false,
"storage": false,
"functions": false,
"facebook_auth": true,
"google_auth": true,
"admob": false,
"dynamic_links": false,
"ml_kit": false
}
I turned off some of the features and did ns plugin remove @nativescript/firebase
and then ns plugin add @nativescript/firebase
and now it's working. I haven't determined which Firebase feature is causing the crash though.
I've identified that admob
is the one that's causing the problem. For anyone seeing this set admob to false
in your firebase.nativescript.json
and then run ns plugin remove @nativescript/firebase
followed by ns plugin add @nativescript/firebase
and the crash should no longer happen.
Closing this as crash is a result of an incomplete Admob setup as outlined in the instructions here. https://github.com/EddyVerbruggen/nativescript-plugin-firebase/blob/master/docs/ADMOB.md#android
My Environment:
OS: Windows 10 CLI: Nativescript v8.0.1 Android Runtime: @nativescript/android 8.0.0 IOS Runtime: @nativescript/ios 8.0.0 Webpack: @nativescript/webpack 5.0.0-beta.3 Test Device: Android Emulator (API v29) Flavor: Nativescript-Vue
Details
Basically after installing this plugin and running
ns run android
. Webpack will compile successfully and I get the messageSuccessfully installed on device with identifier 'emulator-5554'
. However on the device itself the app will open then immediately crash and no error is given in the console. When I try to reopen the app in the emulator I get the following message:My package.json
My App Resources
My
App_Resources/Android/app.gradle
My
nativescript.config.ts
My
firebase.nativescript.json
Things I've Tried
When I uninstalling @nativescript/firebase the app builds fine but as soon as I install this plugin I get this problem again.