search

coleblvck / Shelf

Android Desktop re-imagined.
GNU General Public License v3.0
32 stars 0 forks source link

App crashes with Android 14 #1

Open mondlicht-und-sterne opened 3 months ago

mondlicht-und-sterne commented 3 months ago

When I start this app, I briefly see the picture and then the app crashes

Samsung S21 5G Android 14 IMG_20240626_081804_494

coleblvck commented 3 months ago

I made a build earlier today with some minor changes for Android 13 and 14. I just tested it with Android 14 and it works fine.

I intend on pushing the changes today, hopefully that should work for you. Just a few things I need to wrap up.

mondlicht-und-sterne commented 3 months ago

I downloaded the update, but it didn't work either. Then I uninstalled it and installed the latest version. Doesn't work either. The app remains visible for 1 second longer and then crashes.

coleblvck commented 3 months ago

I have not been able to reproduce this issue. Maybe an architectural issue?

I have updated the current release with three files, two with the other architectures and a debug one. You might want to try the debug, though it is relatively large. Let me know what the deal is.

mondlicht-und-sterne commented 3 months ago

This apk app-armeabi-v7a-release.apk displays the following message:

This app is not compatible with the latest Android version photo1719489300

sanctimoniousape commented 3 months ago

This apk app-armeabi-v7a-release.apk displays the following message:

This app is not compatible with the latest Android version photo1719489300

Out of curiosity, is there a reason you're using the 32bit version (7a) instead of the 64bit (8a) one? Your phone definitely has a 64 bit processor - even though it can run 32 bit apps, you're adding an extra layer of complexity needlessly. I honestly doubt it matters, but if I was tracking down compatibility issues then that's one potential source of contention that's easy to eliminate.

coleblvck commented 3 months ago

Your phone definitely has a 64 bit processor

This was my understanding also and I initially only uploaded the v8a on the releases, but then I tried not ruling anything out as there was no error to work with on this issue. So I uploaded everything else (v7a, x86 and debug) with the hopes of getting something to work with.

Unfortunately, the error/response reported with the v7a is quite generic and still not verbose, so the occurrence of this issue still seems random. My guess is that the debug could possibly do a better job at describing what is happening.

coleblvck commented 3 months ago

@mondlicht-und-sterne I guess until this issue can be reproduced, it'll remain open.

Side note: I have this same app, but written in Kotlin and Jetpack Compose on a private repo here but I only prototype android platform features with it, so it's quite rough and needs some clean up. Perhaps I'll clean it up soon, if you'd like to try that.