feat: Ability to retrieve your previous tickets#3121
Merged
veryayskiy merged 2 commits intomainfrom Feb 20, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Contributor
|
Size Change: +13.5 kB (+0.22%) Total Size: 6.16 MB
ℹ️ View Unchanged
|
marandaneto
reviewed
Feb 20, 2026
| loadUserTraits(): UserProvidedTraits | null { | ||
| if (!this._isPersistenceAvailable()) { | ||
| return null | ||
| private _migrateFromLegacyPersistence(): void { |
Member
There was a problem hiding this comment.
do we actually need to do this since its still not a public beta or anything? so its ok to break in order to have a cleaner code?
Contributor
Author
There was a problem hiding this comment.
Yes, but the moment we deploy on posthog i'll follow up with the cleaning.
marandaneto
approved these changes
Feb 20, 2026
Member
marandaneto
left a comment
marandaneto
left a comment
There was a problem hiding this comment.
left a comment/suggestion otherwise LGTM
veryayskiy
temporarily deployed
to
NPM Release
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR allows users to recover their previous tickets when switching devices or browsers.
Problem
Right now, if you open a product in another browser or computer, you won't see your previous tickets.
Also, the
widget_session_idwas being regenerated on every page refresh despite being stored in localStorage. Root cause: PostHog's core persistence layer silently drops data when the cookie+localStorage merge fails on large entries, so persistence.props came back empty while the raw localStorage still had the value.Solution
Users can retrieve previous conversations via email by:
Moved all conversation data out of PostHog's core persistence blob into its own dedicated ph_conv_ localStorage key (same pattern as toolbar/surveys extensions). Includes a one-time migration from the legacy persistence keys. This eliminates the silent data loss entirely.
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file