clragon / e1547

A sophisticated e621 browser
https://e1547.clynamic.net/
GNU General Public License v3.0
209 stars 16 forks source link

Solving the problem of broken apk with 31 SDK #44

Closed Drawmahs closed 2 years ago

Drawmahs commented 2 years ago

Hi, slragon!

I think I found the reason why the apk releases are broken. the problem seems to be present on Android 11 and above. The android website states that starting from API Level 30, not only the APK v1 Signature Scheme is required, but it should be also signed using the APK v2 signature scheme or higher. I believe you're more experienced with these requirements. I'm sending a link and a screenshot. Hope this'll help you in the development, can't wait for a store release version!

https://developer.android.com/about/versions/11/behavior-changes-11#minimum-signature-scheme

Screenshot_1

clragon commented 2 years ago

Hi,

Thanks for telling me. I am unsure if this is the problem, because certain users have reported being unable to install the app even from the playstore.

Since the playstore signs the app bundles themselves instead of me compiling the APK and since the playstore is basically google, I would assume they would be signing the resulting APK with both the old and new signature scheme.

But we cant be too sure, so I will go check. If i find something, I will let you know. thanks again.