Google Play 64-bit requirement

Solar2D Android
#161

Hi all.

I can’t to build my app.

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ‘:App:processReleaseResources’.

> com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence.

* Try:

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.

* Get more help at https://help.gradle.org

BUILD FAILED in 3m 43s

Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

Android build failed (1) after 229 seconds

What i can do to resolve it?

#162

@paisaev are you using 3495 or 3496?

Can you post your build.settings file?

#163

i use 3496. 

https://drive.google.com/file/d/1EE4KqG98sFmqHRmLMLWxs01RDKHToAXl/view?usp=sharing

#164

Hello, @paisaev. Does your app contains non-latin (outside of a-z) letters in app name?

What about Windows user name, or are you on macOS?

#165

i try to build android by corona v.2019-3496 
 

Build Error

Failed toBuild
More information may be available in the Simulator Console

WARNING: An illegal reflective access operation has occurred

09:49:08.743  WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/C:/Users/fairy/.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)

09:49:08.743  WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1

09:49:08.743  WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations

09:49:08.743  WARNING: All illegal access operations will be denied in a future release

09:49:08.743  warning: [options] source value 7 is obsolete and will be removed in a future release

09:49:08.743  warning: [options] target value 7 is obsolete and will be removed in a future release

09:49:08.743  warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.

in  building.settings file
 

android =

{

versionCode = “3”,

        usesPermissions =

{

            “android.permission.INTERNET”,

            “android.permission.ACCESS_NETWORK_STATE”,

            “android.permission.CALL_PHONE”,

},

usesFeatures =

        {

            { name = “android.hardware.location”, required = false },

            { name = “android.hardware.location.gps”, required = false },

            { name = “android.hardware.location.network”, required = false },

        },

supportsScreens =

        {

            smallScreens  = true,

            normalScreens = true,

            largeScreens  = true,

            xlargeScreens = true,

        },

},

and don’t have plugin 

#166

Yes it is contains a lot of russian texts.

#167

One plugin is native java but there are no .so files, and Qiso is pure Lua. I guess they’re both ok to just leave alone then?

Sorry, I don’t currently have, or really know anything about, Slack.

#168

@fairy.sa if you’re on a mac, run this from the terminal:

defaults write com.coronalabs.Corona_Simulator debugBuildProcess  -int 5

Then quit and build again, and your console log should have a lot more information about what’s going on. If you’re on Windows, you can run this from the cmd.exe:

 reg ADD “HKEY_CURRENT_USER\Software\Ansca Corona\Corona Simulator\Preferences” /f /v debugBuildProcess /d 5

Also if you’re on Windows, do you have any UTF8 special characters anywhere in the path of your project?

Rob

#169

New builds out:

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

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

These should contain Android SDK 28 (Android 9/Pie) support.

Support plugins are updated to the ones before June 17, so they are not the latest, but newer.

#170

In this build i have no problems. Thank you.

#171

Will we be able to use the AdMob and SplashScreen plugins with this build?

#172

@Falcon777 Yes, we can use them and they will work as they do now. Only issue is these plugins have reported some issues which Corona team will fix very soon once Android 64 is complete.

#173

After builf app not launch. =(  But in version 3490 i have no problem.

#174

@Rob,

I’ve completed my first Android build with the new version 3498 and my app will not run.

I uploaded into Google Play Beta without any difficulty. I downloaded the app from Google Play, but it failed to work properly.

So, I think thought to use adb install and see how that would work.

MacBook-Pro:projects troylyndon$ adb install -r “playtrivia.apk”
* daemon not running. starting it now at tcp:5037 *
adb E 06-29 08:52:44 90651 25115266 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)
* daemon started successfully *
Success
MacBook-Pro:projects troylyndon$

So, the issues isn’t installing the app. It will always install. It’s getting it to run without an immediate message invited me to Close App.

#175

@Rob, the exact message my Android brings up is “myGame keeps stopping” with the options App info, Close app, Send feedback. App info doesn’t provide any additional info - it just brings up the same screen as Settings>Apps>myGame

#176

Does ‘adb logcat’ has crash log? If it says that app keeps crashing, it must.

#177

@vlads,

MacBook-Pro:projects troylyndon$ adb logcat Corona:v *:s
--------- beginning of crash
--------- beginning of main
--------- beginning of system

nothing else shows up when I go to open the app

#178

@vlads, what is myGame.aab ? It is generated at the same time as myGame.apk

ANSWERED: From what I can tell, the myGame.aab is the new Android App Bundle format (hense the acronym extension of “aab”).

#179

@vlads and @Rob, I had just removed my 5 plugins, and the app will start-up. So, now I’m going to work one-by-one to figure out which one causes the app not to load and start.

Can you tell me which one you already know will not work yet?

     --[“plugin.facebook.v4a”] = { publisherId = “com.coronalabs”, },
     --[“plugin.notifications.v2”] = { publisherId = “com.coronalabs” },
     --[“plugin.gamecenter”] = { publisherId = “tech.scotth” },  --for iOS
     --[“plugin.google.iap.v3”] = { publisherId = “com.coronalabs”, supportedplatforms = { android=true } },
     --[“plugin.kochava”] = { publisherId = “com.coronalabs”, },

#180

@vlads and @Rob, apparently, the Kochava plugin is the culprit. I see that it is a CoronaLabs plugin, but I’m still going to reach out to my contact there and let them know of the problem and to make sure to be available should you need their help.

After you get the Kochava plugin working for 64-bit, I can then do some comprehensive testing of the 64-bit version for 2 of our 3 apps - I mean hours and hours and hours. Our 3rd app requires numerous other plugins, which will be a lower priority to fix. Thanks to everyone who is working on this, both within CoronaLabs and the community here, to get us all up and running again in 64-bit for Android before the deadline.