Bug: Notifications shows wrong data

[Jaydbrown]

Component: Notifications
Issue: The data displayed is stale and does not reflect the latest on-chain state because the Apollo cache is not invalidated.

Steps to reproduce:

1. Navigate to Notifications
2. Trigger the action
3. Observe the bug.

Expected behavior: The application should handle this gracefully without breaking the user experience.

[mekeke111]

Hi maintainer I am a full stack developer I can handle this

[ekwe7]

I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

[Kenisank]

Hi maintainer, I would like to solve this issue

[Leyrioh7]

Hello Maintainer,
I'd love to assist on this

[grantfox-oss]

🦊 GrantFox — @Leyrioh7 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #163)
2. Your PR will be reviewed by the conduit-protocol maintainers

Good luck! Track your progress on GrantFox.

[Leyrioh7]

Hello Maintainer @Jaydbrown,

I searched the repository and Git history but couldn't find any Notifications component or notification-specific Apollo query. I did find TransactionHistory.tsx, which was implemented for issue #140 and already uses refetchQueries to refresh Apollo data after the action.

I also noticed similar issues for Token Selector, Wallet Connection, and Mobile View that mention incorrect/stale data.

Could you clarify whether the Notifications implementation is expected to be recreated, or if there's another component/data source I should modify?