-
Notifications
You must be signed in to change notification settings - Fork 6
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
MessageCenterNotification not responding immidiately after sending reply from Message Centre #16
Comments
The Apptentive SDK uses a message polling technique, which can result in a delay of up to 5 minutes between sending messages from the dashboard and receiving them in the app. This might explain why you're experiencing a delay before the MessageCenterNotification data class triggers. If you're not getting any callbacks on the unread messages but can see messages in Message Center, you can try the following code snippet (or something similar) to verify that the callback still gets invoked (be careful not to use your current callback when you check this, as it'll overwrite the first callback):
|
Hi Nick,
Thanks for the update, We tried to implement solution shared but unable to resolve Apptentive.addUnreadMessagesListener on successful registration. Can you help with that
Thanks
Kiran S N
|
Hey Kiran, Sorry about that. Try using onUnreadMessageCountChanged instead. Here's method summary as well: https://learn.apptentive.com/docs/android/api/index.html?index-all.html |
We migrated our apptentive-kit-android to sdk 6.0.5 version, We observed that when reply is sent from message centre it take 5-10 mins to get update from callback. MessageCenterNotification data class will not trigger immediately at the same time when we open message centre chat it updates all the message quickly.
Tested in Android 13 Samsung and Pixel devices
Please suggest changes as to get quick update from message centre data
Reference: https://learn.apptentive.com/knowledge-base/android-integration-guide/#message-center-data-monitoring
The text was updated successfully, but these errors were encountered: