Thank you! I think it should support 64 bit but not sure about the OS version
Discussion
running
> adb install 8540bd492064c17d83bcdc6d2a463c2aea46f13c2b0d13b8a96023df95bd0c9d.apk
gave me this:
Performing Streamed Install
adb: failed to install 8540bd492064c17d83bcdc6d2a463c2aea46f13c2b0d13b8a96023df95bd0c9d.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
i am not an android dev, so don't really know what's going on here
I could run it on my phone in dev mode, so the issue is something to do with how the APK is packaged?
One question though, nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9, how does zap.store figure out which apps are installed? Based on the package name?
Correct, the app is released for arm64-v8a only and many of the indexed apps are only fetched for that arch, it was simpler for me to build it this way. But I want to improve.
Yes the installed apps are detected based on the package name, typically a reverse domain notation identifier
Hmm it looks like it's the architecture otherwise it would match the ABI. Unfortunately we only support arm64-v8a at the moment, as well as all the apps available there. I want to make it better and more accessible with time, do you have a github account? If so could you open an issue on https://github.com/zapstore/zapstore ?