Back
Push Target Handling
TL;DR
Developers suggest assigning target_ids to UDIDs and allowing target overrides when users log in with new accounts to better handle push targets. Currently, the issue arises when users delete an app and reinstall it, leaving expired push targets in the database. One developer suggests using the session ID for push target IDs to delete them when users log out. However, this only works for user logouts, not app deletions. The desired solution involves finding a way to handle push targets effectively, possibly by implementing target_id to UDID mappings and allowing overrides for target accounts when users switch accounts.