You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
AGP updated the default ABI filters to include riscv64, which causes apps using barcode-scanning without setting ABI filters to fail when uploading to the Play Store. This is because libbarhopper_v3.so is not available for the riscv64 ABI within the AAR.
> 403 Forbidden
PUT https://androidpublisher.googleapis.com/upload/androidpublisher/v3/applications/{appId}/edits/{editId}/bundles?uploadType=resumable&upload_id={uploadId}
***
"code": 403,
"errors": [
***
"domain": "global",
"message": "Your app declares support for 'riscv64' architecture, but the following libraries are missing: [libandroidx.graphics.path.so, libbarhopper_v3.so, libbugsnag-plugin-android-anr.so, libbugsnag-root-detection.so, libdatastore_shared_counter.so]. Update your app to rely on libraries that support 'riscv64' architecture.",
"reason": "forbidden"
***
],
"message": "Your app declares support for 'riscv64' architecture, but the following libraries are missing: [libandroidx.graphics.path.so, libbarhopper_v3.so, libbugsnag-plugin-android-anr.so, libbugsnag-root-detection.so, libdatastore_shared_counter.so]. Update your app to rely on libraries that support 'riscv64' architecture.",
"status": "PERMISSION_DENIED"
***
Expected behavior barcode-scanning should probably build libbarhopper_v3.so for riscv64, or the ABI restriction should be documented.
Describe the bug
AGP updated the default ABI filters to include
riscv64
, which causes apps usingbarcode-scanning
without setting ABI filters to fail when uploading to the Play Store. This is becauselibbarhopper_v3.so
is not available for theriscv64
ABI within the AAR.Expected behavior
barcode-scanning
should probably buildlibbarhopper_v3.so
forriscv64
, or the ABI restriction should be documented.SDK Info:
com.google.mlkit:barcode-scanning:17.3.0
The text was updated successfully, but these errors were encountered: