Skip to content

Conversation

@ice-cerberus
Copy link
Contributor

@ice-cerberus ice-cerberus commented Jan 14, 2026

Description

  • fixed an issue that happened when user logs out, and then logs in again without restarting the app
  • closes relay connection (and unsubscribes from it) in the "already authenticated" case
  • catch error on followers count provider level

Additional info

This is the uncaught exception happened before the fix:

- [exception] | 14:01:43 580ms | [SESSION-ERROR] Session 019bbc61-d58b-77d4-a7b5-1dd172d29356 failed: 
- SendEventException: received unexpected auth message: already authenticated with a different public key

Task ID

ION-5055

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Refactoring
  • Documentation
  • Chore

).future,
) as FutureOr<int?>;
} catch (error) {
return null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will show incorrect data (0) instead of infinity loading, in case of exception, is it better / do we need to do that?

cache: false,
);
} catch (sendError) {
relay.keys.first.unsubscribe(subscription.id);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we unsubscribe in the finally block already, why do we need it here?

@ice-morpheus ice-morpheus force-pushed the fix-followers-profile-loading branch 17 times, most recently from 8ac6247 to 80a4c2f Compare January 16, 2026 13:34
@ice-morpheus ice-morpheus force-pushed the fix-followers-profile-loading branch from 80a4c2f to a747545 Compare January 16, 2026 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants