Recent searches
No recent searches

Giulio
Joined Nov 28, 2023
·
Last activity Jan 14, 2025
Following
0
Followers
0
Total activity
31
Votes
17
Subscriptions
10
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Giulio
Giulio commented,
CommentPerforming calculations
is it possible to use the IF formula in result metric calculations ?
View comment · Posted Aug 20, 2024 · Giulio
0
Followers
0
Votes
0
Comments
Giulio commented,
Community comment Feedback - Chat and Messaging (Chat)
Marius proposal is perfect! Is there any news about this release?
View comment · Posted Aug 20, 2024 · Giulio
0
Followers
1
Vote
0
Comments
Giulio commented,
Community comment Developer - Zendesk SDKs
Hello, is there any update on this matter?
View comment · Posted Mar 19, 2024 · Giulio
0
Followers
0
Votes
0
Comments
Giulio created a post,
Post Developer - Zendesk SDKs
Hi,
I am writing because we are finding some issues integrating the Android push notifications in the Zendesk messages. After following the instructions in https://developer.zendesk.com/documentation/zendesk-web-widget-sdks/sdks/android/push_notifications/ (we made the custom implementation of
I am writing because we are finding some issues integrating the Android push notifications in the Zendesk messages. After following the instructions in https://developer.zendesk.com/documentation/zendesk-web-widget-sdks/sdks/android/push_notifications/ (we made the custom implementation of
FirebaseMessagingService
since we have other handlers in the app), we found out that notifications were not received. After some digging, it seems that the root cause is the fact that onNewToken
is only invoked when the device token is invalid (normally because a new app install), but it is not invoked for existing users. So, in practice, for apps with pre-existing notifications, I believe it’s needed to add an extra step on the documentation, with something like:FirebaseMessaging.getInstance().token.addOnSuccessListener(activity) { result -> PushNotifications.updatePushNotificationToken(token) }
On top of that, now with that part of the code fixed, we are finding a second problem that we do not know how to resolve, and might require any assistance. When the app receives a push with a message, it can be in 3 states: foreground, background or killed. The first 2 states are handled properly, the use of
PushNotifications.displayNotification(context = this, messageData = remoteMessage.data)
handles a local notification that when clicked it redirects the user to the specific conversation in Zendesk by using a custom pending intent. However, when the app is in killed state, the notification management is different (the OS is the one showing the notification), and when user clicks the invoked method is a
onNewIntent
or onStart
in the launch activity of the app, which is not handling the zendesk data and therefore does not open the conversation screen. How can we fix this? can we invoke any method in ZendeskSdk when we get the new intent so zendesk can inspect it and open the conversation accordingly?Thanks for the helpPosted Feb 01, 2024 · Giulio
0
Followers
2
Votes
2
Comments