-
Notifications
You must be signed in to change notification settings - Fork 350
64 bit #250
Comments
|
@oarsheo How to do it in Android Studio? |
I did this and now I have 5 apks: arm64, armeabi, armv7, x86, x86_64. All of them have crosswalk integrated (the file size confirms it) but when I try to upload them to Play Store I got errors: if I upload only x86 and armv7 (like before) it says they are not 64bit and from 1, August I wont be able to release updates anymore; if I upload arm64 and x86_64 I get an error which says the users will not be able to update to this release; if I upload arm64, x86_64, armv7 and x86 the Play Store says me that they are the same and it removes two of them. Do you have any idea? Thanks! ps: until yesterday I had cordova-ios 6.3 so I only had two apk, x86 and armv7 |
hey @eeschiavo did you get any update on the matter above? Thanks |
I use this way:
it works for me |
@voltor thanks for the response, my worked when I changed the command to
|
Does anyone know how to build 1 apk with arm64, armv7, x86, x86_64? Or 2 apk for armv7+arm64 and x86+x86_64? Because google play will not accept separately armv7.apk and x86.apk. |
I just build with arm64, arm7, x86_64 in 1 apk |
@CCHuang0731 So you used this below? Do you have enabled lite mode of crosswalk? cordova plugin add cordova-plugin-crosswalk-webview --variable XWALK_MODE="lite" |
Thank for your reply. |
It has backward compatibility inside. Now you need only this one package. |
@lumitor2 which one should we use? |
Previously we have got two apk (32 and 64bit version). Now after build there is only one 64bit version, which is backward compatible to 32bit devices. |
I used the build command for the 64bit (--release --xwalk64bit) and have the two APKS (x86 and ARM). I installed the ARM (android-arm64-debug.apk) on a Samsung S7 without issue. When testing on a 32 bit device (Samsung S5) I get Failure [INSTALL_FAILED_NO_MATCHING_ABIS] As I understand this is when there are no matching CPU/CPU-type. |
Update: When looking inside the APK I see that in the lib folder there is only one subfolder with the crosswalk library "arm64-v8a" so no 32 bit included. APK size is also the same as before when we only had the 32 bit version. |
I'm struggling with the same issue, I used:
With the following in config.xml <preference name="xwalk64bit" value="xwalk64bit" />
<preference name="buildArchitecture" value="x86_64" />
<preference name="xwalkMultipleApk" value="false" />
<preference name="xwalkVersion" value="xwalk_core_library:23.53.589.4" /> But when I build, it throws the following errors: FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':app:arm64DebugCompileClasspath'.
> Could not find xwalk_core_library_canary-64bit.aar (org.xwalk:xwalk_core_library_canary:17.46.460.1).
Searched in the following locations:
https://download.01.org/crosswalk/releases/crosswalk-lite/android/maven2/org/xwalk/xwalk_core_library_canary/17.46.460.1/xwalk_core_library_canary-17.46.460.1-64bit.aar and BUILD FAILED in 1s
14 actionable tasks: 1 executed, 13 up-to-date
/Users/JD/Projects/orca-scan/orca-scan-mobile/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':app:arm64DebugCompileClasspath'.
> Could not find xwalk_core_library_canary-64bit.aar (org.xwalk:xwalk_core_library_canary:17.46.460.1).
Searched in the following locations:
https://download.01.org/crosswalk/releases/crosswalk-lite/android/maven2/org/xwalk/xwalk_core_library_canary/17.46.460.1/xwalk_core_library_canary-17.46.460.1-64bit.aar Looking at the
Any idea what I should do next? |
The 'lite' mode doesn't have the 64 bit libraries. If you look at the 'embedded' version the 64 bit files exists. |
This comment has been minimized.
This comment has been minimized.
I got the same problem too. Any help please. I want to know if it's possible to have both lib/arm64-v8a and lib/amrv7 inside, like this I will try to publish an Android App Bundle instead an apk. |
My bad. Everything is ok now. |
@Jilouwikyky How did you create an apk for each architecture (32bit and 64bit)? |
@deviconceptowl Everything is ok for arm7 and x86, if you analyze them you will see they contain the lib folder. So you can use them on Google Play Store after jarsigning and zipaligning operations. But arm64 and x86_64 do not contain the lib folder. You can pass this command Upload all the apks in the same release on Google Play Store like that you care about 32bits and 64bits devices |
@Jilouwikyky Thank you so much. |
I try to do this, and I got three apk, with x86(with 5 library, x64 libs without xwalk library), arm and intel apks. |
@vinceharmon But my app size doubles when I use embedded instead of lite? What should I do? |
Thanks for pointing me in the right direction @Jilouwikyky. I've got a fork repo that has a commit that makes that work a bit easier by automatically using libxwalkcore.so of the appropriate cpu architecture (32 vs 64) by using the flavors that Cordova 9 automatically sets if the xWalk64Bit / buildMultipleApks configurations is set. Defaulting to Cordova's way of versionCode adjustment because that seems to happen anyways. Hope this helps someone on their journey with this dead product 😒 |
this is why I lost many time by eliminating crosswalk from my enterprise project... :-( |
I'm using cordova 9 with this configuration
in the xwalk gradle file
The build generate two files
when i upload it to the PlayStore i have the following error:
the error message refers to the arm64-v8a apk... |
Please upgrade to the 64 bit version.
The text was updated successfully, but these errors were encountered: