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.

Sign up for GitHub

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

Jump to bottom

Incompatibility due to targeting Android 13 "Tiramisu" as the target #1

Closed
Titokhan opened this issue May 18, 2022 · 2 comments · Fixed by #2
Closed

Incompatibility due to targeting Android 13 "Tiramisu" as the target #1

Titokhan opened this issue May 18, 2022 · 2 comments · Fixed by #2
Assignees
@chenxiaolong
Labels
bug Bug in BCR itself

Comments

@Titokhan
Copy link

Device: Redmi 5, Redmi Note 4
Android: 11, 12 (unofficial LineageOS builds)

After flashing the Magisk module, the application can't be found inside the app drawer. You can locate the APK under system/priv-app, but it's not functioning.

Curiously, if you manually try to sideload the APK using ADB, you'll get the following error:

adb: failed to install app-release.apk: Failure [INSTALL_FAILED_OLDER_SDK: Failed parse during installPackageLI: /data/app/vmdl822031778.tmp/base.apk (at Binary XML file line #7): Requires development platform Tiramisu but this is a release platform.]

I can see that android:compileSdkVersion is "32" and android:compileSdkVersionCodename is "Tiramisu" after decompiling the APK.

===

Device: Google Pixel 4a
Android: 13 Beta 2

If you manually try to sideload the APK using ADB, you'll get the following error:

adb: failed to install app-release.apk: Failure [INSTALL_FAILED_TEST_ONLY: installPackageLI]

I can only sideload it under Android 13 using the -t parameter (allow test packages).

The Pixel 4a's bootloader is locked, so I can't test the Magisk module yet. Will do so after backing up data from the device.

===

Android app development isn't my forte, but I think targeting Tiramisu is the primary issue here.
@chenxiaolong
Copy link
Owner

Interesting, I didn't know targeting Tiramisu would break installation on older Android versions. I should have tested that in an emulator. I'll change it to target and compile with SDK 32.

chenxiaolong added a commit that referenced this issue May 19, 2022
@chenxiaolong
Target SDK 32 instead of the Tiramisu preview
e76035c 
It turns out apps built with the preview SDK cannot be installed on
older stable versions of Android.

With BCR now targeting SDK 32, the creation of the notification channel
has been moved from RecorderInCallService to RecorderApplication to
ensure that Android 13 Beta devices automatically prompt for
notification permissions on the first app launch.

Once the stable SDK 33 is released, we can re-add the runtime
permissions request for POST_NOTIFICATIONS.

Fixes: #1
Signed-off-by: Andrew Gunnerson <[email protected]>
@chenxiaolong chenxiaolong mentioned this issue May 19, 2022
Merged
@chenxiaolong
Copy link
Owner

This should be resolved in version 1.1: https://github.com/chenxiaolong/BCR/releases/tag/v1.1

@chenxiaolong chenxiaolong self-assigned this May 22, 2022
@chenxiaolong chenxiaolong added the bug Bug in BCR itself label May 23, 2022
chenxiaolong pushed a commit that referenced this issue Jun 8, 2023
@symbuzzer
Merge pull request #1 from symbuzzer/symbuzzer-patch-1
f469dca 
Update strings.xml
@R44D44 R44D44 mentioned this issue Feb 24, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chenxiaolong chenxiaolong

Labels
bug Bug in BCR itself
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Target SDK 32 instead of the Tiramisu preview chenxiaolong/BCR
2 participants
@chenxiaolong @Titokhan