I get the same thing right after uploading a new release; hopefully nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 can give a pointer of what’s going on here
Discussion
Definitely unusual, I'll have a look in a bit
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esdp32r9 the file got corrupted when uploading to zapstore file server, I need to add checks for that.
Two options:
- try again
- create a github release and use that mode
(use --overwrite-release flag in either case)
Now it worked for me.
Thank you so much