CleaverTap Id is not reachable


#1

We implemented Push notification in our android application. After login application registered with clevertap and getting CleverTap objectId.
Now we are cleared the app data, then logged in into application, now new clevertap id generated.
Here is the actual problem, this new clevertap object id is not working. Clevertap says Clevertap object id “Not Reachable”.


#2

Hey Naveen,

To send out a push notification to any user, there needs to be a mobile token present for your device. Once it is passed, there will be a green bell icon present using which you can send out a test push notification to a particular device.

Can you please check if the device token is being passed to CleverTap everytime the user launches the application.


#3

Hey Saby,

Upon clearing the app data (Android), once i login to my app, Clevertap is generating a new token id.

But the old token id is not cleared in clevertap side.

Can you please check if the device token is being passed to CleverTap everytime the user launches the application.
Yes, New token id which has been generated is sent. But clevertap DB is having the old token id.

For example

During first login, clevertap token is _jkhjkshfjkdhasjkhdjk7878
Upon clearing the data and logging in once again, clevertap token is _89dhakhdkhakjhajksdh

While trying to send a push notification using “_89dhakhdkhakjhajksdh” (newly generated token), we are shown with a message that ‘Not Reachable’

Could you please assist us with this!


#4

Hey Naveen,

This looks like an integration issue. Request you to write to support@clevertap.com so that we can further deep dive into this issue and assist you.