GCM messages die from a silent Accepted death.

A conceptual question if you don't mind.

We have a problem with receiving GCM notifications that are sequentially delivered to our Android application, and they knocked out buses from almost all sides of the code to find nothing wrong. However, many messages simply end their lives with status = Accepted.

I can confirm that the correct gcm_tokens are packaged and sent via POST at https://gcm-http.googleapis.com/gcm/send and that most, but not all, of them are received. I can confirm that all gcm_tokens for these messages are accepted by GCM mail when we register received message_ids. But message_id is not always translated into the submitted notification. FWIW: we do not override the default setting for the delay_while_idle parameter, and the time_to_live parameter is set to 1 day.

I am really at a loss. My remaining two hypotheses are: either GCM is materially smaller, 100% reliability, or we are faced with some kind of boundary case when the client is disconnected from the network and does not receive the message again active. Given this context, is there anything else we should check? Sorry for the vague question ... we don’t know what we don’t know.

+4
source share
1 answer

We faced the same problem.

, , . , - , . , . , GCM - , , .

, ( ). , , , . GCM Google Play - .

, . , GCM 4 ( time_to_live) , .

, https://developers.google.com/cloud-messaging/concept-options#lifetime.

+3
source

Source: https://habr.com/ru/post/1618985/


All Articles