[floooat]

Symptom

A site calls Gleap.clearIdentity() inline on its login page, so the call is queued in window.GleapActions. After logout, the previous identified contact's message preview bubble is shown to the now-anonymous visitor on that browser. This is a privacy issue: messages addressed to a named contact are shown to whoever opens the page next.

Root cause

• clearSession() → GleapNotificationManager.clearAllNotifications(false), whose whole body, including saveToGleapCache('unread-notifications', []), sat behind if (!this.notificationContainer) return;.
• Queued snippet actions run synchronously when the module evaluates (Gleap.js, "Check for unperformed Gleap actions"). injectNotificationUI() only runs after session ready → config → DOM ready. A queued clearIdentity() therefore always found no container, and the gleap-widget-unread-notifications cache survived.
• injectNotificationUI() → reloadNotificationsFromCache() then replayed every cached notification younger than 1 h. That cache key is shared by every contact on the browser.

Fix

1. clearAllNotifications() now always resets the in-memory list and the persisted cache. Only the DOM teardown and the cross-tab broadcast still need the container. The tab channel only starts in injectNotificationUI(), so the broadcast was a no-op before mount anyway.
2. Defence in depth: showNotification() stamps cachedForGleapId on each notification, and reloadNotificationsFromCache() keeps only entries stamped with the current session's gleapId. A reload can no longer show one contact another contact's notifications, even when the identity changes without clearIdentity().

Rollout side effect: bubbles cached by older builds are unstamped. They are at most 1 h old and are dropped once on the first page load after the update. Unread state in the messenger is unaffected.

Verification

Unit tests (src/GleapNotificationManager.test.js, new block "notification cache vs identity (#225880)"):

• Red before the fix: clearAllNotifications(false) clears the persisted cache before the UI is mounted, showNotification stamps the receiving gleapId…, reloadNotificationsFromCache drops notifications cached for another (or no) gleapId (3 failed / 24 passed).
• Green after: the file passes 27/27, and the full npx jest passes 33 suites / 581 tests. Two existing reload fixtures were updated to carry the stamp.

Browser reproduction. A local page seeds the unread cache with a previous contact's notification (written unstamped, as a pre-fix build writes it), then loads the standard async snippet with Gleap.initialize(<test project>) and a queued Gleap.clearIdentity():

Build	Bubbles rendered	gleap-widget-unread-notifications after load
sdk.gleap.io/latest (19.3.5, before)	PREVIOUS USER: Hi Jane, … shown to the new anonymous session	unchanged (1 entry)
this branch (after)	none (container mounted)	[]

Regression check (this branch): the same contact gets a notification via Gleap.showNotification, which caches it stamped with its gleapId. After a reload the bubble is shown again.

Gleap ticket #225880.

🤖 Generated with Claude Code