HWID changes on every app update

Answered

Comments

3 comments

  • Avatar
    Ivan Skoritzky

    Hello,

    Please note that XXXXXXXXXXX:APA91bF6d2gLUM8FpxhnttpEA5XcMGQWFhScVe2zcVLWBjT7gkLAZzMQEHGdcLs788B2qWw8zY8jQPKI1YeXXX-UjUMGzYpK1gPfVbvp8xwmwYXwQwu95NzdXhSP9KmUeCR9OlgvMXXX is a device token, not a HWID.

    Could you please check it on your side?

    However, you can use our Push by User ID feature in order to set a unique value to each user.

    Regards, Ivan

  • Avatar
    eusonlito

    You are right. It's a device token, sorry. What's difference between device token and HWID? Device token is updated on every app update and HWID remains same?

    User ID is not valid for me because user can logged in my app in some devices and other not, I need to notify only to logged devices.

    Thanks!

  • Avatar
    Ivan Skoritzky

    Hello,

    Both HWIDs and push tokens are used for storing the information about a particular device in our system. HWIDs (hardware ID) are the unique device identifiers that are used for storing devices in user base; they are usually generated by Pushwoosh SDK according to IDFV/IDFA, or Android ID. While push tokens are provided by gateways (GCM, APNs, WNS, etc.) directly and used for sending pushes to devices.

    Push Token could be changed in some cases such as reinstallation and app update. Moreover, it should be emphasized that Google tends to change tokens from time to time and it's hard to tell how often such events occur. Please note that Google does not provide any clear information regarding the token expiry process and it is unpredictable to some extent.

    Meanwhile, only device reset (factory reset) and some very specific cases could cause HWID changing.

    Also, you can use the custom tag "logged in/logged out" and send a message only to those who have logged in.

    Regards, Ivan

Please sign in to leave a comment.