Repository navigation
Bug: Notifications shows wrong data #163
Description
Activity
mekeke111 commented
on Jul 25, 2026 ContributorMore actionsHi maintainer I am a full stack developer I can handle this
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
Hi maintainer, I would like to solve this issue
- addedGrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26Campaign: Official Campaign | FWC26
on Jul 25, 2026 Hello Maintainer,
I'd love to assist on thisgrantfox-oss commented
on Jul 25, 2026 grantfox-ossboton Jul 25, 2026 – with GrantFox OSSMore actionsHello 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?
- added a commit that references this issue
on Jul 26, 2026
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:
Expected behavior: The application should handle this gracefully without breaking the user experience.