Hi Rob;
I read the recent posts over the weekend and I was SO EXCITED today to try making an Amazon build of one of our word games to see how and whether Chartboost would display ads properly now.
But I ran into a very fundamental problem with the Corona Builds (I tried builds 3528, 3549, 3551) that make the 64 bit APKs for Google. The problem with the APKs built by these versions is this:
– If I add any SINGLE one of several advertising plugins in build.settings . . . and then I make a build and install it on my Amazon device . . . the app, upon launch, immediately displays a developer message from Corona that “Jumble Crossword does not target the Google Play Store, but includes Google Play Services.”
– If I then remove that one advertising plugin (i.e. Chartboost) and build it again, the app opens fine.
This is the difference in the initial logged messages from my Kindle Fire device as the app opens:
NO PROBLEM WITH JUST AMAZON STORE AND NOTIFICATIONS PLUGINS: =================================
11-18 15:18:20.302 25884 25902 V Corona : > Class.forName: network.LuaLoader
11-18 15:18:20.302 25884 25902 V Corona : < Class.forName: network.LuaLoader
11-18 15:18:20.303 25884 25902 V Corona : Loading via reflection: network.LuaLoader
11-18 15:18:20.311 25884 25902 I Corona : Platform: KFKAWI / ARM Neon / 7.1.2 / Mali-T720 / OpenGL ES 3.1 v1.r12p1-01alp0.62f282720426ab7712f1c6b996a6dc82 / 2019.3551 / English | US | en_US | en
11-18 15:18:20.373 25884 25902 V Corona : > Class.forName: shared.google.play.services.base.LuaLoader
11-18 15:18:20.380 25884 25902 V Corona : > Class.forName: _CoronaSetup.LuaLoader
PROBLEM - IF I ADD AN ADVERTISING PLUGIN TO THE OTHER TWO: =====================================
11-18 15:09:33.435 25304 25388 V Corona : > Class.forName: network.LuaLoader
11-18 15:09:33.435 25304 25388 V Corona : < Class.forName: network.LuaLoader
11-18 15:09:33.435 25304 25388 V Corona : Loading via reflection: network.LuaLoader
11-18 15:09:33.438 25304 25388 I Corona : Platform: KFKAWI / ARM Neon / 7.1.2 / Mali-T720 / OpenGL ES 3.1 v1.r12p1-01alp0.62f282720426ab7712f1c6b996a6dc82 / 2019.3551 / English | US | en_US | en
11-18 15:09:33.475 25304 25388 V Corona : > Class.forName: shared.google.play.services.base.LuaLoader
11-18 15:09:33.475 25304 25388 V Corona : < Class.forName: shared.google.play.services.base.LuaLoader
11-18 15:09:33.475 25304 25388 V Corona : Loading via reflection: shared.google.play.services.base.LuaLoader
11-18 15:09:33.480 25304 25388 V Corona : > Class.forName: _CoronaSetup.LuaLoader
You can see that there are a couple of extra lines in the PROBLEM log. I’m guessing the problem grows out of the “Loading via reflection: shared.google.play.services.base.LuaLoader” line.
I cannot add Chartboost, adColony, AppLovin without triggering this. And there might be a couple of others that trigger this too. I got tired of building test versions to narrow down this problem after a couple of hours.
If you want a test case to duplicate the problem . . . simply swap in and out these plugin sections:
APP RUNS FINE WITH THESE TWO PLUGINS
================================
APP RUNS FINE WITH THESE TWO PLUGINS ================================ plugins = { ["plugin.notifications"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"] = true } }, ["plugin.amazon.iap"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"] = true } }, },
ON APP LAUNCH, GIVES ME THE GOOGLE PLAY ALERT WITH THESE THREE ============================================================== plugins = { ["plugin.chartboost"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"] = true } }, ["plugin.notifications"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"] = true } }, ["plugin.amazon.iap"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"] = true } }, },
As an aside, this app builds just fine and makes an APK without any problems with last April’s Corona 3476. But building with that version just won’t help me test and confirm that Chartboost is fixed.
Thanks for early attention to this.
Steve