NativeScript / NativeScript/firebase
@nativescript/firebase-admob crashed without any error message. Application just disappear.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 62
- Forks
- 53
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 2
Description
Application compiling successfully, but disappear without any error message after I have add @nativescript/firebase-admob. Application disappear during initialization, there are no any forms of application showed.
What I done before application going to unworkable state:
- Change Zone.js from V13 to V14 (with V13 application working perfectly), than install @nativescript/firebase-core and @nativescript/firebase-admob - application still working.
- Add google-services.json from new Firebase project I created specially to this project.
- Follow documentation https://www.npmjs.com/package/@nativescript/firebase-admob#1-initialize-the-mobile-ads-sdk I have add line
to my platforms\android\app\src\main\AndroidManifest.xml (this is test value from https://developers.google.com/admob/android/test-ads#demo_ad_units )
Gradle process modified my AndroidManifest.xml description and deleted this line during command 'ns debug android --debug-brk ' - Add Admob.init() to main.ts file (this is Android project)
- Add AdmobModule to app.module.ts
- Add frame with Banner to one of the form<BannerAd height="100%" width="100%" [unitId]='bannerAdUnit' (layoutChanged)="bannerLoaded($event)" row="1" >
- And define variable with the same demo id "ca-app-pub-3940256099942544/9214589741" and event bannerLoaded(event){console.log(Banner: ${event})}
That's it. Now application became not workable. Now Even first form not showed in run-time. No any warning in compilation. No any error message in runtime. All done follow the package description https://www.npmjs.com/package/@nativescript/firebase-admob
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the initialization failure with the steps in the issue, then inspect main.ts, app.module.ts, and platforms/android/app/src/main/AndroidManifest.xml, including the Gradle-generated manifest. Check the debug Android output for the first failure. Done means the app starts and shows its first form with the AdMob banner configuration enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100