Awesome! 

Can you try publishing with --overwrite-app next time? So that it points the images to the new domain 

 👀

nostr:nevent1qqswe6u0haxld20c0gw270wjn7l6atz7gl6vsvg92uzagylx4smr5qqprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qgsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqrqsqqqqqp4edm7h 

 Sorry about that! Yeah needed to update to zapstore-cli 0.1.2 , I see Pokey now 

 0.7.2-alpha is on the relay. Which version? 

 Yes! Only happens with Themed icons enabled 

 Thanks. As far as I can see, it is set.

There is no app.json in the project, that might be for Kotlin? 

 The foreground image is a white-ish bolt with transparent background, png 

 I drew random lines on background, foreground and monochrome logos. Themed icon remains the same (blank). More likely a configuration issue 

 Fixed. Shipping in next release 

 Not sure, but I removed the monochrome image and it worked 

 Android devs: anyone knows how to fix the themed icon?

I tried but didn't manage. 

Also, I'd like to know which bureaucrat came up with the whole mipmap xml thing and what kind of crack they were smoking.


nostr:nevent1qqs0fynf5m4yc7fw9v50j83cqaa3dyv2k7hvjnjse5rsa9vrhsue55qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyquzlxj3rnvx95a99gct3q8856crfp8z557u0t4d2t7rydd7u5zesqcyqqqqqqg9ahknh 

 Pelo Obtainium tambem e possivel 

 https://github.com/zapstore/zapstore ? Or just search for it 

 Hold on I have Tim Cook on the line, I'll ask for permission

😅 

 Just install via Obtainium. It should install a "Zapstore" app. Use that one. Remove the "zap.store" old one 

 nostr:nevent1qqs0xasxu0ga8dgak459yp6sh7fm9tellz6gfrupp26s06n7y3gkcrcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygrceeh65u3xgwrjsnny0wnf8zv4wd0v3374ckn9wdl92yc0qf3s05psgqqqqqqs6vamrn 

 Can you be more explicit? What does not download from where? 

 This comment was directed to someone who asked about Obtainium. Best way is to get Zapstore through zap.store 😉 

 So true, and exactly the challenge we seek to solve

nostr:nevent1qqs8zra3ch8wrsxjqytqk8dnyz83hfanzsw464vzxakdzsks8xuqt7qprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qgsq4gu7tthengqq577mpdyezkxf90z25g8mvkf355ks2k67km0lwwqrqsqqqqqpc5w9qn 

 Migration happening in the next few days😉 

 That's the plan! 

 It's a bug and already fixed, release in the next few days!

It says: To fix, remove the app (uninstall and reinstall) 

 System for now. To see the uninstall you have to go to Settings and Delete local cache

This is also fixed in the next release 

 Pushing an update to zap.store is super easy (command line tool, that signs events with your nsec). App is then discoverable and updatable -  and soon zappable. 

Happy to whitelist you in our relay if interested.  

 All good.

- Closed source apps totally allowed in zap.store
- Auto updates and other features are not there due to lack of time, not against it. All that's coming
- Would not recommend pasting nsec in CI, we'll get NIP-46 signing in the future

If I were you I'd try to put the app in as many places as possible. Make it easy to update, APK should be in Github releases. So then its updatable via Obtainium. If you don't wanna sign thats ok, I'll add your app to our indexer and it will still be available to users, without you doing any extra work 

 tldr: APK on Github

Also, I like what you're doing with your app. Liquid makes a lot of sense. There are so many bitcoiners that just don't get it 

 Grayjay is also on zap.store  

 Getting this when checking signatures:

❯ apksigner verify --print-certs Desktop/v1.4.0-release.apk
DOES NOT VERIFY
ERROR: Target SDK version 34 requires a minimum of signature scheme v2; the APK is not signed with this or a later signature scheme
WARNING: APK Signature Scheme v3 signer #1: Unknown additional attribute: ID 0x559f8b02
WARNING: SourceStamp: Unknown stamp attribute: ID 0xe43c5946 

 Using build-tools 35.0.0, apksigner 0.9, when verifying your APK:

INFO: SourceStamp: No digests available in the source stamp for signature scheme: 31

Are you getting a different result? Which build tools version? 

 Using --verbose is now showing the certificate information.

However, it gives false for Verified using v4 scheme (it's true for v3.1 scheme) 

 Don't worry, your signatures are in the event you published. Need to fix something in the app and it will be okay 

 It says To fix, remove the app. 

But there's another bug if you decide to uninstall, so in that case Delete local cache from Settings 

 I understand. You had the Play store version installed? 

 Got it! Yes, often times devs publish play and non-play APKs. Not a trivial problem to solve but considering it 

 Thanks, possibly. But every time you delete the local cache it will be gone. 

 Don't worry, it will be fixed 

 Thank you sir! 

 Not sure what we can do about it.

Have you found the APK? 

 Hmmm weird! Possibly two downloads in parallel. Will check! 

 I understand your point, but you labeled them infloooencers. I did not.

Gigi and Vitor are two friends, recognized in the community, who have been very supportive in my zap.store journey and that's why I chose them for this (very early) social feature. 

 Yep! Let me know 

 Would you like to self-publish on zap.store nostr:nprofile1qqswgvmv65ja7706f5a0xe8ajcqdfvgdeeppt2jvx0kh06sggg6ykyqppemhxue69uhkummn9ekx7mp0qys8wumn8ghj7mn0wd68ytn9d9h82mny0fmkzmn6d9njuumsv93k2tcpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0v9ru2a ? 

 Yes, this is the workaround for now! Bug is already fixed and coming out soon 

 Relay management coming soon 

 Yeah it means they do not have a public repository with the corresponding source code.

I will revisit the messaging around this. For many people it's important 

 A dev signed Robosats on zap.store would be 🔥 

 All ready! Your npub authorized to publish com.robosats . Let me know how it goes 

 Awesome! Yeah, the other one has been removed from the relay but still in local cache (which you can delete). Trying to think of a nicer UX for these cases. 

 Search should show just yours, though 

 zap.store has influencooors, blindly signs apps pulled from Github/Microsoft and has a hardcoded, closed relay.

Frens, I'm not Google Corp with unlimited resources 😂 I'm solo on this stuff (but building fully on nostr) and trying to introduce better UX and bootstrapping in a sustainable way in order not to burn out.

Patience please🙏 Relay management, better security features, and viewing apps through your web of trust lens are all coming.

nostr:nevent1qqsffqd60anw4wkjn002293q6cskc9wpxardj6rw6wkhyqcqvxh3a6gpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczypssvegyv9lw0yu8qg0p3jylk7w3mk7ru7llr88j9x85q3n0su27jqcyqqqqqqgdalgh2 

 Soon™️ 

 Yes, it's a bug (already fixed) that will be shipped in the next release.

As a temporary workaround, go to the Settings screen (gear icon) and Delete local cache.  

 https://github.com/zapstore/zapstore-cli

Hopefully that's clear enough!

For other stores, probably fastlane 

 I guess thats fine? Choose to update non beta versions? Several projects only do pre releases 

 👀 

 https://world.hey.com/dhh/living-with-linux-and-android-after-two-decades-of-apple-4f730084 

 It's a bit tricky to support some F-Droid packages, but we'll look into it 

 Thanks for reporting! Yes, aware of this and will be fixed, high priority 

 Beautiful! 

 On it 🫡 

 Dear devs, moving forward published apps should go to relay.zapstore.dev

For that to happen, please update to zapstore-cli 0.1.2

zapstore install zapstore 

Or from https://github.com/zapstore/zapstore-cli