-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically re-send event after NIP-42 authentication #509
Comments
As temporary workaround: subscribe with autoclosing option using a filter that get nothing, like The issue shouldn't be the authentication but the fact that AUTH message is sent after you send the first event (or REQ). So, after the authentication, the event should be re-sent (same issue of few days ago with REQ). I'll try to search a way to automatically re-send the event if the error is related to authentication. |
Yo thank you, your workaround help me resolve the weird bug in my chat app 😅 |
Fixes #509 Signed-off-by: Yuki Kishimoto <yukikishimoto@protonmail.com>
Fixes #509 Signed-off-by: Yuki Kishimoto <yukikishimoto@protonmail.com>
Fixes #509 Signed-off-by: Yuki Kishimoto <yukikishimoto@protonmail.com>
* Remove `Client::spawn_notification_handler` * Add `SharedState` * Auth relays (NIP42) directly in the `InnerRelay` Fixes #509 Signed-off-by: Yuki Kishimoto <yukikishimoto@protonmail.com>
* Remove `Client::spawn_notification_handler` * Add `SharedState` * Auth relays (NIP42) directly in the `InnerRelay` Fixes #509 Signed-off-by: Yuki Kishimoto <yukikishimoto@protonmail.com>
Fixed in #667 |
Describe the bug
Construct a client which also set
automatic_authentication
totrue
(default). It will not automatically auth.To Reproduce
Repo: https://github.com/reyamir/rust-nostr-debug.git
The result is
Err: event not published: auth-required: you must auth
Expected behavior
Automatically auth when add new relay.
Build environment
The text was updated successfully, but these errors were encountered: