After registering a push device in the All Contact List, a random GUID is assigned to the contact created for the device. And when a
ContactKey is assigned to that
Device ID, it gets assigned to a new contact with a different
Contact ID in the contact model.
What happens next is that the
Device ID is erased from the first Contact (with the random GUID) and given to the new contact. So if you're already using the GUID contact in a journey to send Push messages, if a
ContactKey registration is forced on his device, the user stops recieving push notifications from that said journey.
Is there any workarround to that issue by forcing push notification sends in journey builder to a specific device or a procedure to allow users to continue recieving the notifications ?