- Ya
- 25 Aprili 2026, 22:04 UTC
- Mwandishi
- kamo
- Ahadi ya
- 95700c5
TicketChat and ChatNotificationListener imported the context via the '@/app/contexts/...' alias while PresenceWrapper (the provider) imports it via the relative '../contexts/...' path. Next.js bundler treats these as two distinct module instances, so the consumers were reading the DEFAULT context (with no-op subscribe/unsubscribe) instead of the provider's value. Result: TicketChat's STOMP subscription was a silent no-op, the agent never sent SUBSCRIBE for /topic/chat/session/{guid}, and only messages loaded via REST initial-fetch appeared. Subsequent visitor messages had no real-time delivery path. Also adds a console.warn to the default context value so any future "wrong import path" issue is loud instead of silent.