google cloud messaging - Why my Android device is registered at UrbanAirship without GCM Registration ID -
I've integrated the Airship SDK in an Android app. Since app startup and airship, I am receiving the following debug information in my log:
07-27 12: 46: 31.916 XXX - UIILB (1545): push start 07-27 12: 46: 31.937 XXX- Ulyab (1545): Push enabled: True 07-27 12: 46: 31.941 XXX- Ulyab (1545): Starting GCM 07-27 12: 46: 31.941 XXX APID (1545): F28dc1b8-76a7-4c2f-9135-66e968ca8922 07-27 12: 46: 31.941 XXX - Ulyab (1545): Getting Rich Push Getting Started 07-27 12: 46: 31.952 XXX - UALib (1545): Register Default Actions. 07-27 12: 46: 31.953 XXX - UALib (1545): Getting Started with Analytics 07-27 Disambr: 46: 32.025 XXX - UALib (1545): Using GCM registration id: APA91bG3ae7LxgdhRBhpFOS7_QlA0OuYtg5CIoycO6v0moSziWBjycSSs-WMJJ8t6x9liRWi7jaWnaqnKuYU3ORA5S4hsn_vMkEz_7I1YWe76l7kdSiGwkPfc70q4oJCaSp-TaxX1WaHu0SWpX6XHbgwT4vsTABAI187A8xHTy4kGTUg0J6ywMo
But when I go to the airship portal and review token - a device without the registration ID:
apied f28dc1b8-76a7-4c2f-9135-66e968ca8922 No status activated GCM registration ID
And as a result I'm not getting a push for that device.
Any suggestions?
I have already implemented the urban API API, at that time I was also searching for GCM registration ID But nowadays urbanization has changed that thing so problems for you are two problems.
- You can send push messages using APID.
- You can set your unique device ID in the Alive, then you can send push messages to that area using the API.
Hope this helps. Please comment for further explanation
Comments
Post a Comment