After adding the appodeal plugin, live builds don’t work for me anymore after changing the app package name to be the same as the one on the appodeal app configuration. I’ve connected my phone and noticed this on the logs:
3-20 17:20:20.008 18129 18230 V Corona : \> Class.forName: network.LuaLoader 03-20 17:20:20.008 18129 18230 V Corona : \< Class.forName: network.LuaLoader 03-20 17:20:20.008 18129 18230 V Corona : Loading via reflection: network.LuaLoader 03-20 17:20:20.010 18129 18230 I Corona : Platform: Nexus 5X / ARM Neon / 8.1.0 / Adreno (TM) 418 / OpenGL ES 3.2 V@258.0 (GIT@8e59954, I0be83d0d26) (Date:09/22/17) / 2018.3326 / English | GB | en\_GB | en 03-20 17:20:20.015 18129 18230 V Corona : \> Class.forName: \_Corona\_Build\_Number.LuaLoader 03-20 17:20:20.021 18129 18230 V Corona : \> Class.forName: shared.google.play.services.base.LuaLoader 03-20 17:20:20.029 18129 18230 V Corona : \> Class.forName: CoronaProvider.licensing.google.LuaLoader 03-20 17:20:20.029 18129 18230 V Corona : \< Class.forName: CoronaProvider.licensing.google.LuaLoader 03-20 17:20:20.029 18129 18230 V Corona : Loading via reflection: CoronaProvider.licensing.google.LuaLoader 03-20 17:20:20.030 18129 18230 V Corona : \> Class.forName: \_CoronaSetup.LuaLoader 03-20 17:20:20.032 18129 18230 V Corona : \> Class.forName: plugin.liveBuild.LuaLoader 03-20 17:20:20.032 18129 18230 V Corona : \< Class.forName: plugin.liveBuild.LuaLoader 03-20 17:20:20.032 18129 18230 V Corona : Loading via reflection: plugin.liveBuild.LuaLoader 03-20 17:20:20.053 18129 18230 V Corona : \> Class.forName: plugin.appodeal.LuaLoader
The app doesn’t even load, it stops there. It loads ok if I change the app package name to something else, but then ads won’t show, obviously.
The non-live builds works correctly on the device. This is pretty annoying because I can’t use live builds and it takes a while to create a normal build, install it and test.
There is a live builds hidden file in the same folder with main.lua. I’m not at a point I can look it’s name up, but you can try removing it. You can also close and reopen your live build server.
Check to make sure your your device and your computer are on the same wifi network.
Do you mean .CoronaLiveBuild? I’ve tried to remove it multiple times. I’ve also followed all the steps described on the troubleshooting section here https://docs.coronalabs.com/guide/distribution/liveBuild/index.html and still same problem as long as the package name (bundle id) is the same as the one used by the app settings on Appodeal.
Are you using the Appodeal plugin? I’ve tried with other apps that are not using the plugin and they work. I suspect it’s a problem with Appodeal + package name; other combinations seem to work for me.
For the sake of double checking, I’ve done the following:
Install 2019.3470 build
Build the Android live build with a different package name than the one configured on Appodeal for the app. I added an extra letter. The app loads (of course, ads don’t as the package name is not the correct one)
Remove .CoronaLiveBuild file
Uninstall the app from the device
Build the Android live build with the correct package name. The app doesn’t load anymore.
Checkout one of the initial commits, which doesn’t have the Appodeal plugin
Remove .CoronaLiveBuild file
Uninstall the app from the device
Build the Android live build with the package name used by Appodeal app. The app doesn’t load, even if it’s not using the plugin. The adb log gets stuck at “Loading via reflection: plugin.liveBuild.LuaLoader”
Uninstall the app from the device
Build the Android live build with a different package name. The app loads correctly.
So it looks to me like a problem with the package name. No idea why… It doesn’t contain any weird characters or anything like that.
Thanks @agramonte. I’ve got quite a few more Appodeal plugins (basically all of them), but I don’t see why that would be a problem, as even reverting back to a version without ads suffers from the same problem.
Hey! Thanks for trying things out, but using some Plugins with Live Builds can be tricky - far from all ad networks allow to re-initialize their runtimes without consequences. I feel like you may hit one of those cases. Sorry about that.
There is a live builds hidden file in the same folder with main.lua. I’m not at a point I can look it’s name up, but you can try removing it. You can also close and reopen your live build server.
Check to make sure your your device and your computer are on the same wifi network.
Do you mean .CoronaLiveBuild? I’ve tried to remove it multiple times. I’ve also followed all the steps described on the troubleshooting section here https://docs.coronalabs.com/guide/distribution/liveBuild/index.html and still same problem as long as the package name (bundle id) is the same as the one used by the app settings on Appodeal.
Are you using the Appodeal plugin? I’ve tried with other apps that are not using the plugin and they work. I suspect it’s a problem with Appodeal + package name; other combinations seem to work for me.
For the sake of double checking, I’ve done the following:
Install 2019.3470 build
Build the Android live build with a different package name than the one configured on Appodeal for the app. I added an extra letter. The app loads (of course, ads don’t as the package name is not the correct one)
Remove .CoronaLiveBuild file
Uninstall the app from the device
Build the Android live build with the correct package name. The app doesn’t load anymore.
Checkout one of the initial commits, which doesn’t have the Appodeal plugin
Remove .CoronaLiveBuild file
Uninstall the app from the device
Build the Android live build with the package name used by Appodeal app. The app doesn’t load, even if it’s not using the plugin. The adb log gets stuck at “Loading via reflection: plugin.liveBuild.LuaLoader”
Uninstall the app from the device
Build the Android live build with a different package name. The app loads correctly.
So it looks to me like a problem with the package name. No idea why… It doesn’t contain any weird characters or anything like that.
Thanks @agramonte. I’ve got quite a few more Appodeal plugins (basically all of them), but I don’t see why that would be a problem, as even reverting back to a version without ads suffers from the same problem.
Hey! Thanks for trying things out, but using some Plugins with Live Builds can be tricky - far from all ad networks allow to re-initialize their runtimes without consequences. I feel like you may hit one of those cases. Sorry about that.