reboot needed to send queued upstreams (jb & ics)

[Flash Bump]

Hi,

When network is down or if the connection between the device and GCM server is down, upstreams are locally queued.

Once this queue exceeds 20 messages, subsequent messages are discarded and a local intent is broadcasted (MESSAGE_TYPE_SEND_ERROR and error=TooManyMessages).

When connection is up again, remaining messages in the queue are correctly sent on kk.

On jb and ics (4.1.2, 4.2.2, 4.0.4) they are not, and sending messages triggers the local intent.

Only a reboot forces the messages to be eventually sent.

All devices have the same, up to date, Google services.

As anyone observed this?

[Francesco]

Hi there,

do you have gTalk or Hangouts installed on those jb and ics devices?

--
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/7356f08c-782a-45ca-9c6b-d5ff286a4b9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Flash Bump]

Hangouts is installed on the 4.2.2 device (S4). Can't check other devices right now, but they are in their initial setup, so either one of gtalk or hangouts should be installed.
Thanks in advance.

[Francesco]

yeah I am interested in knowing whether the affected devices have gTalk or they upgraded to Hangouts. Anyways we are investigating.

On Fri, Mar 21, 2014 at 4:55 AM, Flash Bump <com.fl...@gmail.com> wrote:

Hangouts is installed on the 4.2.2 device (S4). Can't check other devices right now, but they are in their initial setup, so either one of gtalk or hangouts should be installed.
Thanks in advance.

--
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/be754ccf-52b9-4378-98a5-f7dc70572d0a%40googlegroups.com.

[Flash Bump]

I'll give you detailed gtalk/hangouts installation reporting quickly (next week).
Feel free to ask use cases to run.

[Flash Bump]

I checked the 3 devices. They all upgraded from gTalk to Hangouts, and share the same version (2.0.303 - 1004807-30) of it, same configuration as on the kk device.

[Flash Bump]

Hi, any insight on this one ?

[Flash Bump]

As an information, today's new hangout upgrade does not appear to solve the above problem.

[Vadim Osovskiy]

I have observed same issues, except I had no idea that reboot would push messages from queue.

When data connection is restored, messages in queue are not pushed until reboot, but newly sent messages are sent just fine.

Tested on 4.2.2 with latest Hangouts.

[Sam Kelleher]

Hello,

Also experiencing a 20 message limit on locally queued messages from device to server when offline. This limit isn't documented anywhere. It seems to me to be a rather daft limit. Surely this is some sort of bug or configuration issue rather than by design?

Running:

Hangouts v 2.1.100 (1151589-30)

Google Play Services v 4.3.25 (1117461-032)

Android: 4.1.2

[Flash Bump]

You are right, this limit doesn't seem to be documented, Francesco mentions it in Google IO, though.

[Flash Bump]

I can't observe the issue anymore.

I don't know which component upgrade is to be thanked, but it is issue has completely gone.

Thanks.