nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 the nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvuasnac app cannot be verified on the zapstore when installing...
Discussion
Can you try again? If it still fails and the file fully downloaded, it's likely nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvuasnac modified the github release. Otherwise there is a man in the middle attack - be careful this is a wallet
I tried multiple times. Every time the file downloads and it fails during verification. Every other app downloads and verifies successfully. I think they might have changed their signature? When I look their sha256 I get this key:
e0735a70d3439f6e5739a2b9e2ddd2d4bec18b679ac1a614a05ecacc8e1d2820 1.9.57.apk
If i am not mistaken in your app it shows another key...
Yes, then they changed the APK after it was indexed. Zapstore working as expected!