Issue with GetUnreadMessageCountAsync method in Messaging SDK Unity
投稿日時：2025年4月16日
Hello!
We are currently integrating your messaging SDK into our Unity application and have encountered a technical issue with the GetUnreadMessageCountAsync method
Here are the details of the issue:
In our usage GetUnreadMessageCountAsync(Action onUnreadCountChanged, bool shouldSubscribe) returns 0 until the user opens the support conversation.
We attempted subscribing to the WebSocket event outside of the conversation, but this did not resolve the issue.
The method only starts returning valid information after the user has opened the support conversation.
Our goal is to notify users of new responses from support agents by displaying a notification dot above the support button. However, the current behaviour of the SDK prevents us from achieving this functionality.
Expected Behaviour:
We expect that the GetUnreadMessageCountAsync method should return the actual unread message count as soon as the SDK is initialised, regardless of whether the user has opened the support conversation.
Could you please provide guidance on how to resolve this issue or let us know if there is an alternative approach to achieve the desired functionality?
We are using Zendesk Unity UPM package version 3.2.0
Thank you for your assistance. We look forward to your response
0
4件のコメント
Nikita Kostuk
Hi Greg!
Thanks for answers!
1
Greg Katechis
I don't have a great way to ensure that you're notified when this specific feature rolls out, mostly because it won't be a "big" announcement like some other features might be. That being said, the announcements section is a good place to follow in general. A less efficient, but definitely more accurate method would be to check the changelog every week or two, because this will definitely show up as a release note!
0
Nikita Kostuk
Hi Greg!
Yes, indeed, all our users are anonymous. It’s great to hear that your dev team is working on a solution for this case. I’m looking forward to seeing this resolved in the coming months.
By the way, is there any way to track the progress of this task or be notified once the fix is implemented?
Thank you for the update!
0
Greg Katechis
Hi Nikita,
Could you let me know if this issue is occuring for users who are authenticated via JWT or if this is only happening for anonymous users? I ask because currently this would be expected behavior for anonymous users, although the dev team is looking to get around this in the coming months. If this is occurring with authenticated users, then we would definitely want to take a further look at this.
0
サインインしてコメントを残してください。