🚀 zapstore CLI 0.2.3 released

Various fixes, including one related to updating date on release.

Developers: I recommend updating: `zapstore update zapstore`

Or get from https://zapstore.dev/download if using standalone (no need to install it if just using `zapstore publish`)

Reply to this note

Please Login to reply.

Discussion

my current phone isn't compatible with zapstore 😢 is there a minimum ram requirement? I only have 2GB with android 14 go

Sorry about that. I don't think I can do anything about it, not anytime soon. I'm a one man show

I found an issue trying to link to Zapstore apps.

The Fossify Messages app ID has an extra space at the end, which makes it not open up properly within a link. Add the extra space and it works.

Still not sure what the issue is with the QR Scanner link not working.

Misty Breez has an extra space at the end of the app ID as well

Phoenix wallet has 2 extra spaces at the end of it app ID

IronFox has an extra space.

These link used to work. Maybe the last updates are adding extra spaces to the end of app IDs.

Thank you! Need to research that

Which link are you talking about?

The link to the zapstore app ID, such as

zapstore://fr.acing.phoenix.mainnet

If I want the markdown link to work right now I have to put a space after the app ID like so.

(zapstore://fr.acing.phoenix.mainnet )

Thank you!

Can you whitelist me on cdn.zapstore.dev?

zapstore publish tries to upload there and fails despite my zapstore.yaml:

blossom_servers:

# - https://cdn.zapstore.dev

# - https://blossom.band

- https://blossom.iris.to

nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9

Absolutely. Done!

Sorry just checked here

This is a great (z)app store. Thank you for building this. You're profile says 0.2.6 is the latest release, but zapstore within zapstore is showing 0.2.7

To clarify, for the android app.