-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing message error #10
Comments
There is a known-bug with Dev Console where you will receive multiple On Tue, Aug 27, 2013 at 6:54 AM, Nitin Kappor [email protected]:
Cheers! |
Hi Stephen, While there may be a problem in the console program, our concern is that we are receiving it multiple times on the device. In fact that was the reason why we started investigating this. |
Yes thank you for the feedback, and I see why you have initially started the investigation. This may be a specific issue with an older Android SDK, we have recently posted a new one! Did you have a chance to review the upgrade to Android? |
Hi Stephen, We have on Android SDK 3.5.4. |
Okay thank you for details. Can you send us your setup details to [email protected] regarding the Android SDK, version number, Android OS version and any other relevant details? To confirm, this is a topic on Duplicate Messages on Android SDK, correct? Make sure to note that in the email to support email. |
Hi Stephen I have mailed details to [email protected] |
Excellent thank you greatly and we will be in touch. On Aug 28, 2013, at 10:34 PM, Nitin Kappor [email protected] wrote:
|
Hi,
I have found following errors while publishing to a channel to a ruby client . The channel is being subscribed by iOS as well as Android client. We faced an issue where android client was receiving duplicate messages where as iOS client received only a single message .
We ran test where we subscribed on the channel through Android , iOS as well as console. We noticed that sometimes console received a single message twice or thrice but there was only one message in history . Any idea why this is happening ????
The text was updated successfully, but these errors were encountered: