Build failed for android using the latest corona build 2019.3495

Solar2D Android
#1

Hey,

Glad that corona finally has a version that supports 64-bit builds. I installed the latest version i.e. 2019.3495 and created a new project from the simulator with only an empty main file. I then tried building that project for android but got an error message saying the build failed. The following text was being printed on the simulator’s console.

19:16:54.041  WARNING: An illegal reflective access operation has occurred

19:16:54.041  WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/C:/Users/famousdoggHP/.gradle/wrapper/dists/gradle-5.1.1-all/97z1ksx6lirer3kbvdnh7jtjg/gradle-5.1.1/lib/groovy-all-1.0-2.5.4.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)

19:16:54.041  WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1

19:16:54.041  WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations

19:16:54.041  WARNING: All illegal access operations will be denied in a future release

19:16:54.041  

19:16:54.041  FAILURE: Build failed with an exception.

19:16:54.041  

19:16:54.041  * Where:

19:16:54.041  Build file ‘C:\Users\famousdoggHP\AppData\Local\Temp\Corona Labs\CLtmpa04544\template\app\build.gradle.kts’ line: 715

19:16:54.041  

19:16:54.041  * What went wrong:

19:16:54.041  C:\Users\famousdoggHP\AppData\Local\Temp\Corona Labs\CLtmpa04544\template\app\build\intermediates\corona-mega-jar does not exist.

19:16:54.041  

19:16:54.041  * Try:

19:16:54.041  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

19:16:54.041  

19:16:54.041  * Get more help at https://help.gradle.org

19:16:54.041  

19:16:54.041  BUILD FAILED in 11s

19:16:54.228  Android build failed (1) after 13 seconds

  

#2

Let me run this by engineering

Rob

#3

Thanks, @leokarun, this will be fixed in next daily build, bug which wasn’t in previous. If you build app with some plugins, it will go away. Or wait till next build is up.

#4

Okay, I tried to build an app after including some plugins and still got the exact same error. Guess I’ll have to wait for the next build and hopefully this problem would be resolved by then. Cheers.

#5

Sorry about that. Single line of code to fix rare error broke a build :frowning: New build is up. Only change is fix to that fix. Just replace numbers in URL to 2019.3496 (note, it’s in two places)

#6

Here are the new URLs:

http://developer.coronalabs.com/sites/default/files/corona/2019.3496/Corona-2019.3496.msi

http://developer.coronalabs.com/sites/default/files/corona/2019.3496/Corona-2019.3496.dmg

Rob

#7

Thanks Rob and vlads- we’re still experiencing some issues but we’re trying out the latest builds on multiple systems now to try and figure out exactly where the problem is because the latest logs are not very clear on why it’s failing. 

We’ll post again as soon once we have some more details. We’ll also test plugins extensively and report any issues that we find. Thanks :slight_smile:

#8

Hey again @Rob & @vlads. After trying out the latest build( i.e. 2019.3496) the following were my observations -

  • I was finally able to create a 64-bit build of a blank app created using corona simulator. I even tested the app on a device and it worked as expected which is great :slight_smile:

  • But when I tried building one of our working projects, I was getting some dependency related error on multiple systems. I have included a text file that contains the logs pertaining to the error. I suspect it could be due to one of the plugins. I’ll anyway be looking to spend more time testing this, like try after removing some 3rd party plugins etc.

Please let me know if you could make out what the issue might be. Thanks for your support. 

#9

Keep in mind that this is basically closed alpha we are showing to pinpoint issues like that. Currently know issues in Corona itself are about Windows and non-ascii paths or names.
Also, as you seen for yourself, some plugins are still not working. If plugins don’t work for you, please, post which are broken

#10

Hey all. This thread is becoming unmanagable. We’ve created a new forum just for Android 64 bit:

 

https://forums.coronalabs.com/forum/664-android-64-bit-testing/

 

Please read the pinned post at the top:

 

https://forums.coronalabs.com/topic/75790-handling-bugs-with-android-x64-and-target-sdk-28/

 

Please direct any testing related issues there.

 

Thanks

Rob

#11

Let me run this by engineering

Rob

#12

Thanks, @leokarun, this will be fixed in next daily build, bug which wasn’t in previous. If you build app with some plugins, it will go away. Or wait till next build is up.

#13

Okay, I tried to build an app after including some plugins and still got the exact same error. Guess I’ll have to wait for the next build and hopefully this problem would be resolved by then. Cheers.

#14

Sorry about that. Single line of code to fix rare error broke a build :frowning: New build is up. Only change is fix to that fix. Just replace numbers in URL to 2019.3496 (note, it’s in two places)

#15

Here are the new URLs:

http://developer.coronalabs.com/sites/default/files/corona/2019.3496/Corona-2019.3496.msi

http://developer.coronalabs.com/sites/default/files/corona/2019.3496/Corona-2019.3496.dmg

Rob

#16

Thanks Rob and vlads- we’re still experiencing some issues but we’re trying out the latest builds on multiple systems now to try and figure out exactly where the problem is because the latest logs are not very clear on why it’s failing. 

We’ll post again as soon once we have some more details. We’ll also test plugins extensively and report any issues that we find. Thanks :slight_smile:

#17

Hey again @Rob & @vlads. After trying out the latest build( i.e. 2019.3496) the following were my observations -

  • I was finally able to create a 64-bit build of a blank app created using corona simulator. I even tested the app on a device and it worked as expected which is great :slight_smile:

  • But when I tried building one of our working projects, I was getting some dependency related error on multiple systems. I have included a text file that contains the logs pertaining to the error. I suspect it could be due to one of the plugins. I’ll anyway be looking to spend more time testing this, like try after removing some 3rd party plugins etc.

Please let me know if you could make out what the issue might be. Thanks for your support. 

#18

Keep in mind that this is basically closed alpha we are showing to pinpoint issues like that. Currently know issues in Corona itself are about Windows and non-ascii paths or names.
Also, as you seen for yourself, some plugins are still not working. If plugins don’t work for you, please, post which are broken

#19

Hey all. This thread is becoming unmanagable. We’ve created a new forum just for Android 64 bit:

 

https://forums.coronalabs.com/forum/664-android-64-bit-testing/

 

Please read the pinned post at the top:

 

https://forums.coronalabs.com/topic/75790-handling-bugs-with-android-x64-and-target-sdk-28/

 

Please direct any testing related issues there.

 

Thanks

Rob