Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android <7.0 support #163

Open
fr-an-k opened this issue Jan 20, 2024 · 1 comment
Open

Android <7.0 support #163

fr-an-k opened this issue Jan 20, 2024 · 1 comment

Comments

@fr-an-k
Copy link

fr-an-k commented Jan 20, 2024

After building an apk, adb install gives INSTALL_PARSE_FAILED_NO_CERTIFICATES.
Looking at the code it seems that V1 signing is not supported (Android <7.0).

In Cargo.toml (is this actually used?):

[package.metadata.android.sdk]
min_sdk_version = 21
target_sdk_version = 34
max_sdk_version = 34

Command:

x build -v --release --format apk --platform android --arch arm64

If I build directly for the device, it decides to make an aab instead of apk (format arg is not allowed).
That's undesirable; I don't use a store and adb doesn't work with this format.

x build -v --release --device 192.168.0.225:5555
adb -s 192.168.0.225:5555 install -r target/x/release/android/na-winit-wgpu.aab
Performing Push Install
adb: need APK file on command line

If I try to run it, it fails:

x run -v --release --device adb:192.168.0.225:5555
Error: adb getprop exited with code Some(1)

On Android 8.1 I can build and run just fine.

@fr-an-k
Copy link
Author

fr-an-k commented Jan 20, 2024

If I try to convert the aab to apk, bundletool says:

Error: The archive doesn't seem to be an App Bundle, it is missing required file 'BundleConfig.pb

cargo apk build creates an installable apk (it doesn't work but that's probably because of wgpu)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant