Anyone else having a failure on upgrade?
Obtanium reports a "conflict" while nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpstc2n just exits the update.
Same here! I'll look into this today
nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 I ran into a few issues with zapstore-cli.
Thanks for reporting! I ll take a look
Next week I'll be working mostly on the Android app...
Do you mean when tapping on Update on the Android prompt/dialog?
When did this strange behavior start happening?
Can you record a screencap and/or share device info (in the ⚙️ screen) via DM?
Zap.store CLI 0.0.5 released✨ Improvements around publishing, so that even more developers can self-sign.
Download from https://zap.store or https://github.com/zapstore/zapstore-cli (docs are in the readme)
To update: zapstore install zapstore 🐶
🔑 Also: We JUST had a very well known Android app signed by its dev! Guess which
You're absolutely right. Java can and should be used that way. Culturally though, the average Java programmer will tend to bloat things, at least that is my experience over the years.
My Flutter-generated APKs are very small (8-10MB) and most of what I see written in JS is way bigger. So I actually think the opposite!
Super interesting, thanks! I wonder if we have other ways of compiling to Dalvik than through JVM bytecode
I did not mention Java and XML on purpose because who would torture himself that way
Android developers... what language/platform do you use to build your apps?
Kotlin, React Native, Capacitor, Flutter, any others?
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsfd4wdf nostr:nprofile1qqsyq6npqal7vlcwmf97jv2h93fzlyme2twmqfxgwee78hntxl56nrcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgdwaehxw309ahx7uewd3hkcr6e5r3 the app doesn't let me install on a pixel 8 pro 
Sorry bug, we're fixing it
When zap.store is ready i'll change the keys and start publishing the hashes
For now you can check if Amber is signed with the key 56dc631996a55c2284790448c7dc9f1dd05df596b2ce4882313633f5602e5fe4 and try to check if the apk is reproducible by building it and see if it matches the content inside the apk
The best way of doing this i found was adapting the signal docker file
https://github.com/signalapp/Signal-Android/tree/main/reproducible-builds
If you dont want to do this its better to wait for when i start signing with my new keys in zap.store
Would you like to try it now? Hopefully it works.
see https://github.com/zapstore/zapstore-cli
I already whitelisted your npub in the relay
The other option is going the AltStore or sideloadly route, but I'm not sure about UX
It would not, PWAs are web applications
This would be awesome. But I found a bug in the publisher when trying to upload the APK. Once I fix this, I will let you guys know.
https://github.com/zapstore/zapstore-cli has a readme with documentation.
In addition, the Android client needs an update to clearly show this software is closed source.
We'll be in touch!
🙃
