getAlby / getAlby/lightning-browser-extension
[BUG] If browser is closed with for ex hamstr.to client opened and then pages restored, Alby do not sign nostr events.
- Dominant language
- TypeScript
- Stars
- 585
- Forks
- 228
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 16
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
Hi,
If browser is closed with for ex hamstr.to nostr client opened and then pages restored, Alby do not sign events.
### Screenshots [optional]
https://user-images.githubusercontent.com/1178856/214727901-719de2f0-4cc0-4dcd-a352-8430dc8a7455.mp4
### Steps To Reproduce
1- Open https://hamstr.to/
2- Login on Hamstr using Alby
3- Close browser and then reopen and restore hamstr.to
4- Unlock Alby
5- Try to post something on Hamstr
### Expected behavior
Be able to sign events, but what happens is that is only possible to sign events again, if I logout from Hamstr and login again with Alby. Refresh page do not help.
### Alby information
Alby version: 1.24
### Device information
_No response_
### Additional context
_No response_
### Are you working on this?
No
Contributor guide
Research direction
No source file or test is named. Start by reproducing the flow on hamstr.to with Alby 1.24: restore the browser session, unlock Alby, and try to post a Nostr event. Trace the signing request after restoration; done means events can be signed without logging out and logging in again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100