Notification feed stream emits stale state for comment/reaction activity types

[andrewmikhniuk]

Bug Report: FeedState stream emits stale state for 'comment', 'reaction', and 'comment_reaction' activity types

Package version: stream_feeds: ^0.5.0

Description

When listening to Feed.stream for notification feeds, the stream does emit when new activities of type 'comment', 'reaction', or 'comment_reaction' are received, but it emits the old/stale state instead of the updated state containing the new activity.

Expected behavior

When a new comment, reaction, or comment_reaction activity is added to the feed, the FeedState stream should emit a new state that includes the newly added activity.

Actual behavior

The stream listener is triggered when activities of type 'comment', 'reaction', or 'comment_reaction' are added, but the emitted FeedState contains the previous state without the new activity. The new activity only appears after manually refreshing the feed.

Important: When re-initializing the feed (calling getOrCreate() again), the initial state is correct and includes the new notifications. This indicates the issue is specifically with the stream not emitting the updated state.

Code to reproduce

final query = FeedQuery(
  fid: FeedId.notification(client.user.id),
);
final feed = client.feedFromQuery(query);
await feed.getOrCreate();

notificationsStream = feed.stream.listen((streamState) {
  // When activity.type is 'comment', 'reaction', or 'comment_reaction':
  // - This callback IS called
  // - But streamState.activities contains the OLD state, not the new activity
  print('Activities: ${streamState.activities}');
});

Impact

Notification badges and real-time notification lists do not update when users receive comments or reactions on their posts, even though the stream event fires.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Bug: ownReactions field resets when adding multiple reactions #57

Related Issues

• Missing export: ActivityState class is not publicly accessible #61
• Missing export: ReactionGroupData class is not publicly accessible #63
• Error when trying to add an activity #76

🔗 Related PRs

#64 - refactor(llc)!: unify comment data model and add tests [merged]
#65 - feat(llc): add onNewActivity callback to Feed [merged]
#66 - feat(llc): add support for location based filtering for activities [merged]
#71 - feat(llc): handle missing events [merged]
#72 - refactor(llc): remove client side sorting from feeds [merged]

👤 Suggested Assignees

• xsahil03x
• andrewmikhniuk
• rlee1990

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[xsahil03x]

Hey @andrewmikhniuk , I am not really able to reproduce it locally. Can you test again with the latest version v0.5.1? and maybe also share a video showcasing the same? Thanks

[andrewmikhniuk]

Hi @xsahil03x,

Thanks for looking into this! I've tested with stream_feeds: ^0.5.1 and can still reproduce the issue.

I've attached a video demonstrating the bug:

What the video shows:

1. The debug page displays FeedState.activities from the Feed.stream subscription
2. When a new comment/reaction/comment_reaction notification arrives, the stream does emit (you can see the "Last stream event" timestamp updating)
3. However, the emitted FeedState.activities contains the stale/old state — the new activity is not included
4. When I manually call getOrCreate() again (reinitializing the feed), the fresh Feed.state.activities does contain the new notification

This confirms the stream listener is triggered, but it emits the previous state rather than the updated one.

Environment:

• stream_feeds: ^0.5.1
• Flutter 3.38.4
• iOS/Android

Let me know if you need any additional information or a minimal reproduction project!

Screen.Recording.2026-01-15.at.16.47.54.mov