Closed khlling closed 3 months ago
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!
Hi, thanks for bringing this to our attention. Regarding how you are deleting the attribute and it isn't appearing, this might be related to our customer dashboard caching as when you go to set the attribute in the app it might not be cleared yet. Let me check this with the team and I will let you know.
Hi @khlling, Sorry for the late response. Is this happening when setting the subscriber attribute to be the exact same thing it was before you deleted it? What if you set Purchases.setAttributes({ age: 24 }); , delete via dashboard, and then set Purchases.setAttributes({ age: 100 });, do you still experience the same issue?
Hi @khlling, Since this issue hasn't been updated for some time, I closed it. But if you're still having this issue, please feel free to reopen it.
Describe the bug I found this issue while testing custom attribute targeting.
Purchases.setAttributes({ age: 24 }); syncAttributesAndOfferingsIfNeeded();
Through investigation, I have found a workaround:
Set the custom attribute to "" before setting it to the value you want:
I would expect that deleting the custom attribute from the backend means I can recreate from the frontend without issue. I am being careful to call syncAttributesAndOfferingsIfNeeded(); below the limit of 5 per minute whilst testing.
Additional context Add any other context about the problem here.