search

ursuscamp / nostore

A nostr signing extension for Safari.
MIT License
56 stars 13 forks source link

Issues with profile selection and saving #2

Closed blakejakopovic closed 1 year ago

blakejakopovic commented 1 year ago

I'm unsure the cause, but the first time I added an account it worked well, then after that it kept losing new profiles, didn't want to save, and kept returning undefined as the pubkey for websites on sign in, even with the private key set.

This is using a MacBook with latest Safari and latest TestFlight version of the extension.

ursuscamp commented 1 year ago

Does it resolve on its own and then reoccur? Or is this a permanent issue?

blakejakopovic commented 1 year ago

It seems permanently broken, after that initial period it worked when I first added a profile. A weird issue where the profile name populated after a delay as I was typing a new name happened too. I uninstalled the extension, reinstalled and disabled in Safari for now.

On 27 January 2023 at 2:34:19 pm, Ryan Breen @.***) wrote:

Does it resolve on its own and then reoccur? Or is this a permanent issue?

— Reply to this email directly, view it on GitHub https://github.com/ursuscamp/nostore/issues/2#issuecomment-1406517643, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADILOQLGYBZV7DD7GW6IODWUPFFXANCNFSM6AAAAAAUIVB6VE . You are receiving this because you authored the thread.Message ID: @.***>

ursuscamp commented 1 year ago

Pretty strange!

If you have the Develop menu active in Safari, you could right click somewhere on the Nostore popup (not a webpage, the popup) and select "Inspect element". Then goto the Javascript console and use the command: await browser.storage.local.get(); and then provide that information which is returned. That should give me a view of the extension's state and might provide some insight as to how it got so borked.

If you do choose to do that, please note that data will include your keys, so make sure to replace your keys with random garbage or something.

blakejakopovic commented 1 year ago

I've been playing around with it a bit more and haven't trigged the same issues - however I remember that I used bech32/nsec keys originally, and so far I have only been testing using hex keys.

I'll continue to play with it and see If I can trigger the same issues, and I can then share await browser.storage.local.get();.

Thanks, Blake

On 27 January 2023 at 6:55:09 pm, Ryan Breen @.***) wrote:

Pretty strange!

If you have the Develop menu active in Safari, you could right click somewhere on the Nostore popup (not a webpage, the popup) and select "Inspect element". Then goto the Javascript console and use the command: await browser.storage.local.get(); and then provide that information which is returned. That should give me a view of the extension's state and might provide some insight as to how it got so borked.

If you do choose to do that, please note that data will include your keys, so make sure to replace your keys with random garbage or something.

— Reply to this email directly, view it on GitHub https://github.com/ursuscamp/nostore/issues/2#issuecomment-1406878617, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADILOQMFUMCNKQ7E2DCYKLWUQDXZANCNFSM6AAAAAAUIVB6VE . You are receiving this because you authored the thread.Message ID: @.***>

blakejakopovic commented 1 year ago

I wasn't able to cause the same issue on that version with minimal testing, and since now there are major updates, I'll close this as resolved. Thanks for your time anyway.