Skip to content
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

Notification Feed Subscription not being triggered by ActivityMarker().allSeen().allRead() #193

Open
ObserverMoment opened this issue Jan 28, 2022 · 0 comments · May be fixed by #198
Open
Labels
bug Something isn't working enhancement New feature or request

Comments

@ObserverMoment
Copy link

Hi,

Is there a way to be able to be able to receive real-time updates when a user marks all their notifications as seen / read?

I am getting unseen counts to display an indicator via

final counts = await _notificationFeed.getUnreadUnseenCounts()

Then subscribing to the notification feed via

 _feedSubscription =
          await _notificationFeed.subscribe(_handleSubscriptionMessage);

When the user opens their notifications list I run this

final feedActivities = await _notificationFeed
          .getEnrichedActivities<User, dynamic, String, String>(
              limit: _postsPerPage,
              offset: offset,
              marker: ActivityMarker().allSeen().allRead());

However, the subscription is not triggered and so the indicator does not update correctly.

Can you advise how this should be achieved please?

Thanks,

Rich

@ObserverMoment ObserverMoment added the bug Something isn't working label Jan 28, 2022
@sachaarbonel sachaarbonel added enhancement New feature or request backend bug Something isn't working and removed bug Something isn't working backend labels Feb 1, 2022
@sachaarbonel sachaarbonel linked a pull request Feb 1, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants