No, it’s just assistant. You can do setup without it.
Just ignore it. It’s used for Simulator builds afaik.
Regarding build.gradle. You have to have the following lines:
classpath ‘com.google.gms:google-services:3.0.1’
in your top-level build.gradle file and
apply plugin: 'com.google.gms.google-services'
in the app build.gradle file
I attached zip with my gradle files from sample project with working notifications v2 plugin
Thank you! I did it and it started to work.
Actually, the same lines as in your examples work:
classpath ‘com.android.tools.build:gradle:3.0.1’
classpath ‘com.google.gms:google-services:3.1.2’
While classpath ‘com.google.gms:google-services:3.0.1’ generated “not found” errors when syncing the gradle.
So far so good. The app generates the FCM token and doesn’t crash. However when I use this token in the FB console, the push notification is not delivered. It fails.
So there is something else I am missing. The build with the simulator works fine. Something about google-services.json? It should be in the app directory now, right?
Yes, google-services.json should be in the app directory.
Android Native is tricky, you have to figure out all these dependencies… Perhaps you should follow Google tutorial and add something like
com.google.firebase:firebase-messaging:12.0.1
into your gradle dependencies.
Thank you!
To sum it up, In Native Android I implement FCM in Java and plugin.notifications.v2.jar helps just to call FCM from .lua files, right? build.settings is ignored in this case, I guess.
Yes, you got it right.
As said here https://coronalabs.com/blog/2017/10/19/using-plugins-with-native-android-builds/
it’s your responsibility to integrate them into your Android Studio project. Each Android plugin may have additional settings and configuration that you need to complete before you can use it.