This is driving me crazy because there is a corrupted user in my sandbox environment and I can’t continue working without deleting it. But deleting it doesn’t work because it’s cached for a few hours.
We REALLY need a way to be able to completely delete a user in sandbox environment along with clearing the cache.
+6There shouldn't be a cache on the user itself, but there may be some data in the dashboard (e.g. Customer Lists and Charts) which continues to persist for a few hours until those data sources are periodically updated.
Could you please share some details on your workflow? Specifically - what data is being cached and how is it impacting your testing workflow?
I’ve been running into this same pain when testing out the webhook setup and verifying the paywall and checkout flow works e2e (giving entitlement access to specific features for the user etc). Like im testing it out on my physical iPhone and ill run into errors along the way. The sandbox subscription goes through but my backend webhook setup is not correct. Then if you try to test this out again you run into the issue where “The user is already subscribed” or something like that and you have to delete that customer and try again. But even after you delete the customer you still run into the caching issue where it still thinks your subscribed already. It seems to work fine a few minutes after deleting the customer but it is kinda annoying to deal with.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
