Skip to content

hotfix/cp-12815-preserve-attributes-tags-and-subscription-history-when-user-re-enables-notifications - #389

Open
unnaticleverpush wants to merge 2 commits into
masterfrom
hotfix/cp-12815-preserve-attributes-tags-and-subscription-history-when-user-re-enables-notifications
Open

unnaticleverpush wants to merge 2 commits into
masterfrom
hotfix/cp-12815-preserve-attributes-tags-and-subscription-history-when-user-re-enables-notifications

Conversation

@unnaticleverpush

@unnaticleverpush unnaticleverpush commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Preserve subscription data when notifications are disabled and re-enabled


Note

Medium Risk
Changes unsubscribe cleanup and subscription sync payload affect targeting and server-side subscription state when notifications are toggled.

Overview
When users unsubscribe with keepTargetingDataOnUnsubscribe enabled, Piano segments are now kept in local prefs alongside topics, tags, and attributes—they are only cleared when that flag is off.

Subscription sync (/subscription/sync/) now reads stored tags and custom attributes from SharedPreferences and includes them in the sync payload (tags, customAttributes), so re-enabling notifications can restore targeting data on the server without losing local history.

Reviewed by Cursor Bugbot for commit dbbf36f. Bugbot is set up for automated code reviews on this repo. Configure here.


Summary by cubic

Preserves subscription data when users disable and re-enable notifications.

  • Piano segments are no longer cleared when keepTargetingDataOnUnsubscribe is enabled.
  • Restores saved tags and custom attributes during subscription sync after re-enabling notifications.

Written for commit dbbf36f. Summary will update on new commits.

View guided diff Turn on auto-fix

…n-user-re-enables-notifications

Preserve subscription data when notifications are disabled and re-enabled
@unnaticleverpush unnaticleverpush self-assigned this Oct 23, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 2 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants