NotRegistered with no reason

[IRIS Technologies]

Hi

we have a problem for our app using gcm

for no reason (no app update/remove nor android update), we get suddenly NotRegistered error for devices with  previously successfull response

i have no idea why this happens

we find around 20 devices on 170 registered at the end of august in this case.

i try to activate GCM stats on developer console but i did not find any explanation

the only way to fix this is to restart registration from app on device to check if registrationid changed.


last case reported yesterday for registration id
APA91bEq7YgqkkkEHjXdNCIQzDdQT155He0dnJ-k89SL3TxLixdZRvSljiAvsqCPPdgoa7Q5tDmx0y55EP8I91_ZbGuArGYt-TuMLyTTTiWSvGpLoZflPlkTptTeHjeStT25tU-1SaHqhziGxSuBuAAFAlok2RWc0g

[Thu Nov 27 14:29:50 2014] [info] PushRequest : Success
[Thu Nov 27 14:29:51 2014] [info] PushRequest : Success

[Thu Nov 27 14:29:53 2014] [info] PushRequest : Fail (NotRegistered)
[Thu Nov 27 14:30:09 2014] [info] PushRequest : Fail (NotRegistered)

time are  (UTC+0100)

is it possible to have a closer look for this please?

Thank you

[Tingmui Li]

There was unregister requests coming in around the time that you saw NotRegistered error code. 

Typically that is due to app update/uninstall or unregister() being called explicitly. Hope this helps.

[IRIS Technologies]

thank you for the reply

unfortunately, there is no call to unregister in my code...

as far as i know, the app was not updated nor uninstalled
the app was still running and is configured (en user does not know password for registration)

other cases

"APA91bFeAIbQI6xCAM8lLZ3EikrKM2T7bi9Oo8wMw-yraGyu0LGd7V9Nyl7hQfUqS8MAqWSL29a2CcvQeBv-iUHbyZDTUdMeRoAdUCVIxYvsgWBUOX7dyhQrAbyfvLACV18fAQv3DJnadmlzKGXibnWuQSqI0bBDig"
[Fri Nov 21 14:30:12 2014] [info] PushRequest Success
[Fri Nov 21 14:35:11 2014] [info] PushRequest Fail (NotRegistered)

"APA91bH5bC-XvXg1zRe078lJiDowHxPG-RIj3WTeyagVdh2AhNQ6Vn9LK4Zxni4iL5VIop2SXNG5jEJUgPf-hCdKpIjO12C1605Y_b7E3UB5-JVqwWIhAtQDUPr3YLbWob2FmpaF7Zy-Hmb_UrQa0yOq_v32m36wiQ"
[Fri Nov 21 14:35:12 2014] [info] PushRequest : Success
[Fri Nov 21 14:40:12 2014] [info] PushRequest : Fail (NotRegistered)

is there a way to know why registration state changed?

[IRIS Technologies]

new case detected this morning

""APA91bEo-fyLfBwW9_2yZB4niuVMPbbMJWCGjC_HvW0bK443l4qOnKhZVjrUN5gAHNbBbZAZ_ameXVKUd1Z2a70JOrU3jmlv_RG8MOzRi-7yOiiwGIOiYQeI7VDm_JRWA8nNTAWGcUw99nCz7suvgP2dsPvfu1Cazg"

send success until 09:25:15 CET
NotRegistered at 09:30:15 CET

[IRIS Technologies]

another one yesterday for regid

"APA91bGg-MVH0_pwGxcWLayGyoP1jNW5AvnxB1rSGVMxaya8epJqTi8A0uaOUqxtg9Wi_gUtl8OxChYwivQaIQb_KOyVSd1aSc3lq_SwIn8W4V4NLu2q1FR2sp3FdSJcjfxj6lxi2DgsrXFc3pVaWNfecVih7zcmtg"

last success
[Mon Jan  5 10:40:05 2015 CET

fist fail
Mon Jan  5 10:45:05 2015 CET

app installed 28 Aug 2014
not updated nor uninstalled

still no idea why i get this NotRegistered error

please help...

[Tingmui Li]

We looked at the issue from the server side and would need log/bug report from the device when this happens.

Or if you have another instance of when this happens recently, please provide the regID with the device bug report?

[IRIS Technologies]

OK i will report next case

for the log it may be hard to provide you more infos as i have no access to the device...
what kind of log/info do you need?

[IRIS Technologies]

new case this moring

push ok until 08:05 (UTC+0100)

got NotRegistered at 08:10

regid
"APA91bEPv8wJZuS7QP3OlsSUt5rta-zbWGnAhsRcJQhcPFm6yHo593O01mqn4JyX3oHeL8auRlAgASXH59EYWJEoaDASyNEEEEbNv3l7LoqENhipO8WDHgmSsVx6Q0rh5hYokxd1fFY1k0dU-Rv0Z4cDoGxHiGKR9w"

app installed 26 Aug 2014

Le mercredi 14 janvier 2015 21:56:43 UTC+1, Tingmui Li a écrit :

[Olexandr Tereshchuk]

I have similar issue - at some point, registration id stop working and server responds NotRegistered. It happens on relatively small number of devices.

понеділок, 16 березня 2015 р. 10:41:07 UTC+2 користувач IRIS Technologies написав:

[Diego Giorgini]

Hi Olexandr,

if you want us to debug the issue we need some reference such as registration-id or message-id.

The server returns NotRegistered when the application is not registered with GCM anymore.
This can happen if your application called unregister() or if the user uninstalled your application.

Also, it is a good practice to obtain a new registration-id after each application update.

This because the registration-id might get invalidated during the update under some particular scenarios.
(see: https://developer.android.com/google/gcm/client.html)

If you are sure that the error you are seeing is not due to what I wrote above, then you can send us the registration-id and we can check the data on our end.

Thanks

--
You received this message because you are subscribed to the Google Groups "android-gcm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-gcm...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/b1f72150-386b-4927-bbd2-ad509399e1cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Olexandr Tereshchuk]

Hi Diego,

here is an example (5 minutes old)

token:

APA91bF0WuoVRUm5_HmyeDVuTNevysq16VuIH_7xRK-ndtNVPkF_f7K0erTmwma5ozWXTFHBf_BJDMQ_sHpeg2pSCFOzHMxkt5hnZl8RyehpI2g3FgYgstoMu_RNRVQ9amN3kh0R5cSv

server response:

{"multicast_id":8610165014240580995,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"NotRegistered"}]}

--
You received this message because you are subscribed to a topic in the Google Groups "android-gcm" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-gcm/LbBzSZG76z8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-gcm...@googlegroups.com.

To post to this group, send email to andro...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/CAK3gzh8GXr%2BByJOdzqiibLNFcOYqVpc-sp7sF5D%3DFTmA_HLhiQ%40mail.gmail.com.

[IRIS Technologies]

Last case for me

"APA91bFLAL8TQMmKH8nDFeoXqz2R2corrRsC3u7NUGjzJoU4sqvLqjTtQ-IM991eCOeluLzl6pDNw8eu0ZkHUWchQY4HfIsWBS-vYKkbM8IAgTawLfoQG8keXLhOgRc18DsLmJGLJGMqOEd8nCUqoyAza8a_ikv79w"


Success [Mon Apr 20 08:05:12 2015]
NotRegistered [Mon Apr 20 08:10:13 2015]

app installed 26 aoû 2014

[Olexandr Tereshchuk]

I've just updated app and GCM client gave me the same token: APA91bF0WuoVRUm5_HmyeDVuTNevysq16VuIH_7xRK-ndtNVPkF_f7K0erTmwma5ozWXTFHBf_BJDMQ_sHpeg2pSCFOzHMxkt5hnZl8RyehpI2g3FgYgstoMu_RNRVQ9amN3kh0R5cSv

Here is the log (I've tried to enable all log-tags that I've found):

04-22 08:11:43.444  16838-16838/com.google.process.gapps D/GCM﹕ GcmService start Intent { act=com.google.android.gms.gcm.PACKAGE_REPLACED cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.gms.gcm.PACKAGE_REPLACED

04-22 08:11:43.444  16838-16838/com.google.process.gapps D/GCM﹕ A CONNECTED 1  ReconnectManager: skip retry, isActive()

04-22 08:11:46.987  16838-16838/com.google.process.gapps D/GCM﹕ GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE

04-22 08:11:46.987  16838-16838/com.google.process.gapps D/GCM﹕ A CONNECTED 1  ReconnectManager: skip retry, isActive()

04-22 08:11:47.048  16838-16838/com.google.process.gapps D/GCM﹕ GcmService start Intent { act=com.google.android.gms.gcm.PACKAGE_REPLACED cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.gms.gcm.PACKAGE_REPLACED

04-22 08:11:47.048  16838-16838/com.google.process.gapps D/GCM﹕ A CONNECTED 1  ReconnectManager: skip retry, isActive()

04-22 08:11:48.069  30687-30711/com.keypr.czar I/LogProvider﹕ Invalidating GCM token

04-22 08:11:48.169  18261-30887/com.google.android.gms D/GCM﹕ Registration proxy: serial=12

04-22 08:11:48.189  18261-30887/com.google.android.gms I/GCM﹕ GCM config loaded

04-22 08:11:48.199  17195-17195/com.google.android.gms D/GCM﹕ Dispatch to user 0 service com.google.android.c2dm.intent.REGISTER

04-22 08:11:48.209  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89] Register binder info: calling uid=10021 pid=16838 4060165623643519497

04-22 08:11:48.219  16838-30892/com.google.process.gapps I/GCM﹕ GCM config loaded

04-22 08:11:48.229  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89] register: url=https://android.clients.google.com/c2dm/register3

04-22 08:11:48.229  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89]   device=3837588424505886095

04-22 08:11:48.229  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89]   app=com.keypr.czar  cert=ec2ffe02c60ffa601ce285f625e1c9e5faf1b4c0

04-22 08:11:48.229  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89]   sender=<secure>

04-22 08:11:48.229  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89]   device_user_id=12

04-22 08:11:48.229  16838-30892/com.google.process.gapps V/GCM﹕ echo 'WC1HT09HLlVTRVJfQUlEPTQwNjAxNjU2MjM2NDM1MTk0OTcmWC1HT09HLlVTRVJfVE9LRU49Nzc2OTY0ODUxMzE3ODUzNjA1JmRldmljZT0zODM3NTg4NDI0NTA1ODg2MDk1JnNlbmRlcj0zOTYzMzg0NzI1MTUmYXBwX3Zlcj0yNjAwMDImZ2NtX3Zlcj03MDk5MDM2JmFwcD1jb20ua2V5cHIuY3phciZpYXQ9MTQyOTcxNTUwOCZjZXJ0PWVjMmZmZTAyYzYwZmZhNjAxY2UyODVmNjI1ZTFjOWU1ZmFmMWI0YzAmaW5mbz1ZcTR3aGZyS3Q0Y1VGdTR4SW1STW9Xb2RBeXl2bVFJJmRldmljZV91c2VyX2lkPTEy' | base64 -d > /tmp/$$.bin; curl -X POST --header "app: com.keypr.czar" --header "content-length: 285" "https://android.clients.google.com/c2dm/register3" --data-binary @/tmp/$$.bin

04-22 08:11:48.549  16838-30892/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.89] Send registration intent for app= com.keypr.czar registration_id uid=12

04-22 08:11:48.569  18261-18261/com.google.android.gms D/GCM﹕ Dispatch to user 12 Intent { act=com.google.android.c2dm.intent.REGISTRATION flg=0x10 cmp=com.google.android.gms/.gcm.GcmProxyReceiver (has extras) } com.keypr.czar

04-22 08:11:48.569  18261-18261/com.google.android.gms E/GCM﹕ No receivers found com.keypr.czar

04-22 08:11:51.452  30687-30712/com.keypr.czar I/LogProvider﹕ Invalidating GCM token

04-22 08:11:51.472  18261-30970/com.google.android.gms D/GCM﹕ Registration proxy: serial=12

04-22 08:11:51.472  18261-30970/com.google.android.gms I/GCM﹕ GCM config loaded

04-22 08:11:51.482  17195-17195/com.google.android.gms D/GCM﹕ Dispatch to user 0 service com.google.android.c2dm.intent.REGISTER

04-22 08:11:51.482  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92] Register binder info: calling uid=10021 pid=16838 4060165623643519497

04-22 08:11:51.492  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92] register: url=https://android.clients.google.com/c2dm/register3

04-22 08:11:51.492  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92]   device=3837588424505886095

04-22 08:11:51.492  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92]   app=com.keypr.czar  cert=ec2ffe02c60ffa601ce285f625e1c9e5faf1b4c0

04-22 08:11:51.492  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92]   sender=<secure>

04-22 08:11:51.492  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92]   device_user_id=12

04-22 08:11:51.492  16838-30971/com.google.process.gapps V/GCM﹕ echo 'WC1HT09HLlVTRVJfQUlEPTQwNjAxNjU2MjM2NDM1MTk0OTcmWC1HT09HLlVTRVJfVE9LRU49Nzc2OTY0ODUxMzE3ODUzNjA1JmRldmljZT0zODM3NTg4NDI0NTA1ODg2MDk1JnNlbmRlcj0zOTYzMzg0NzI1MTUmYXBwX3Zlcj0yNjAwMDImZ2NtX3Zlcj03MDk5MDM2JmFwcD1jb20ua2V5cHIuY3phciZpYXQ9MTQyOTcxNTUxMSZjZXJ0PWVjMmZmZTAyYzYwZmZhNjAxY2UyODVmNjI1ZTFjOWU1ZmFmMWI0YzAmaW5mbz1ZcTR3aGZyS3Q0Y1VGdTR4SW1STW9Xb2RBeXl2bVFJJmRldmljZV91c2VyX2lkPTEy' | base64 -d > /tmp/$$.bin; curl -X POST --header "app: com.keypr.czar" --header "content-length: 285" "https://android.clients.google.com/c2dm/register3" --data-binary @/tmp/$$.bin

04-22 08:11:51.592  16838-30971/com.google.process.gapps D/GCM﹕ [C2DMRegistrar.92] Send registration intent for app= com.keypr.czar registration_id uid=12

04-22 08:11:51.592  30283-30886/com.keypr.czar I/KeyprRegistration﹕ KeyprRegistration: Store GCM registration ID {...R5cSv} for app version 260002

04-22 08:11:51.602  18261-18261/com.google.android.gms D/GCM﹕ Dispatch to user 12 Intent { act=com.google.android.c2dm.intent.REGISTRATION flg=0x10 cmp=com.google.android.gms/.gcm.GcmProxyReceiver (has extras) } com.keypr.czar

04-22 08:11:51.602  18261-18261/com.google.android.gms E/GCM﹕ No receivers found com.keypr.czar

--
You received this message because you are subscribed to a topic in the Google Groups "android-gcm" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-gcm/LbBzSZG76z8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-gcm...@googlegroups.com.

To post to this group, send email to andro...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/fc18f67c-dc48-483c-9eca-6067a975cd64%40googlegroups.com.

[IRIS Technologies]

sorry

this device was reset for maintenance, so this is a good NotRegistered response...

[Olexandr Tereshchuk]

I see a really strange behavior.

Having token APA91bF9wToiitLZbC7qjny54XHPubWpno0SF-RCqLa_JaaJyDe9YWa5-lOIaYzVHHi71MfsMMrnGDsxf_hlaYxiK2IVAXdst_fkZ44tvcHaroGvREY5nFKhbiOfOgz4J0bIeEyT-03V

I increment version code to force re-registration. But always get same token (at least until device reboots or user got deleted).

What strange is that sending messages to that token results in {"multicast_id":7943618671817827970,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"NotRegistered"}]} but right after the re-registration device receives push notification which I've send earlier

четвер, 23 квітня 2015 р. 15:33:13 UTC+3 користувач IRIS Technologies написав: