Kommunicate.io Android Chat SDK for Customer Support

I get following error while launching conversation : Registration response is: {"message":"PASSWORD_INVALID","currentTimeStamp":1618334956706,"deactivate":false,"totalUnreadCount":0,"metadata":{},"newUser":false}

My code :

 fun openConversation(context: Activity, onLoading: ((isLoading:Boolean) -> Unit)?=null, onError:((error:Throwable?, showError:Boolean)->Unit)?=null) {
        var messageMetaData=  mutableMapOf<String, String>()
        var sessionId= MyApplication.instance?.preferencesManager?.getSessionId()
        var userId=MyApplication.instance?.preferencesManager?.getCachedUser()?.customer_id
        var emailId=MyApplication.instance?.preferencesManager?.getCurrentUserEmail()
        var suite=MyApplication.instance?.preferencesManager?.getCachedUser()?.suite
        if(!(validateCredentials(userId,emailId,suite))){
            onError?.invoke(null, true)
            return
        }
        onLoading?.invoke(true)
        var user = KMUser()
        user.userId= userId
      //  user.userName=suite
        user.email = emailId
        user.password=APPConstants.KOMMUNICATE_PASSWORD
        messageMetaData.put("defaultMessageMetaData","{\"userId\":\""+sessionId+"\"}")
        var kmConversationBuilder :KmConversationBuilder
        if(Kommunicate.isLoggedIn(context))
            kmConversationBuilder= KmConversationBuilder(context)
        else
            kmConversationBuilder=KmConversationBuilder(context).setAppId(APPConstants.KOMMUNICATE_APP_ID)
                    .setKmUser(user)
        kmConversationBuilder
                .launchConversation(object : KmCallback {
                    override fun onSuccess(message: Any) {
                        onLoading?.invoke(false)
                    }

                    override fun onFailure(error: Any) {
                        onLoading?.invoke(false)
                        onError?.invoke(null, true)
                    }
                })
    }

Permission WRITE_EXTERNAL_STORAGE will no longer provide write access when targeting Android 10 and above. Details: https://developer.android.com/training/data-storage/shared/media#request-permissions

But in your SDK, WRITE_EXTERNAL_STORAGE is requested regardless of the API version.

Client can set attribute android:maxSdkVersion on that permission in manifest, it has the effect of removing element on higher Android SDK versions, at least in terms of how runtime permissions work.

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
                 android:maxSdkVersion="28" />

There is a lint warning in AS with regards to WRITE_EXTERNAL_STORAGE, it suggest set atrribute android:maxSdkVersion="28". But in that case verification that both WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE permissions granted will always not pass (ConversationActivity.java:700). The files selection screen will not open and will show up snackbar "Storage permission is required...".

Hi, I did a chatbot integration with dialogflow. My dialogflow bot also has webhook integration. When I use the following code; I don't see the metadata and the user information passed to payload from kommunicate to dialogflow webhook.

Is the following code wrong or is there a configuration that I did not do or is there an isse on kommunicate server-side?

        new KmConversationBuilder(this.activityContext)
                .setSkipConversationList(true)
                .setSingleConversation(true)
                .setBotIds(botIds)
                .setMessageMetadata(this.chatContext)
                .setKmUser(user)
                .launchConversation(new KmCallback() {
            @Override
            public void onSuccess(Object message) {
                System.out.println("onSuccess");
                System.out.println(message);
            }

            @Override
            public void onFailure(Object error) {
                System.out.println("onFailure");
                System.out.println(error);
            }
        });

When i send a message i send a parameter in metadata. Here is log which get printed when i send a message :

Sending message to server: { "applicationId": "174afd6c613bbb5be0bbd725cafbe88", "attDownloadInProgress": false, "canceled": false, "clientGroupId": "[email protected]_523659", "connected": false, "contactIds": "", "contentType": 0, "createdAtTime": 1618817104202, "delivered": false, "deviceKey": "235cc17d-d712-4ad2-97d5-d4bc29753274", "groupId": 57925473, "hidden": false, "key": "212a5201-f473-4f05-9322-925342e92380", "message": "hello. testing again", "metadata": { "userId": "66b3d32cd58a51a54d35a3547cc7e5e0" }, "read": true, "replyMessage": 0, "sendToDevice": false, "sent": true, "sentMessageTimeAtServer": 0, "sentToServer": true, "shared": false, "source": 2, "status": 1, "storeOnDevice": true, "type": 5, "userKey": "974bb53b-3768-43f0-9cc0-24f5e9a6fc9e" }

But our web guy is unable to get "userId" under metadata on his side. Here is the request he is getting using "dialogflow". Can you help us with this?

{"responseId":"55eb9d3d-1311-4c7d-8c65-e9271be3a59c-d74139ee","queryResult":{"queryText":"u10d2u10d0u10dbu10d0u10e0u10efu10ddu10d1u10d0","parameters":[],"allRequiredParamsPresent":true,"fulfillmentMessages":[{"payload":{"metadata":{"payload":[{"message":"u10d8u10dcu10e4u10ddu10e0u10dbu10d0u10eau10d8u10d0 u10d0u10dbu10d0u10dcu10d0u10d7u10d8u10e1 u10e8u10d4u10e1u10d0u10eeu10d4u10d1","title":"u10d8u10dcu10e4u10ddu10e0u10dbu10d0u10eau10d8u10d0 u10d0u10dbu10d0u10dcu10d0u10d7u10d8u10e1 u10e8u10d4u10e1u10d0u10eeu10d4u10d1"},{"message":"u10d6u10ddu10d2u10d0u10d3u10d8 u10d8u10dcu10e4u10ddu10e0u10dbu10d0u10eau10d8u10d0","title":"u10d6u10ddu10d2u10d0u10d3u10d8 u10d8u10dcu10e4u10ddu10e0u10dbu10d0u10eau10d8u10d0"}],"contentType":"300","templateId":"6"},"message":"u10dbu10ddu10d2u10d4u10e1u10d0u10dau10dbu10d4u10d1u10d8 $firstname, u10dbu10d4 USA2GEORGIA-u10e1 u10d1u10ddu10e2u10d8 u10d5u10d0u10e0. u10d8u10dcu10e4u10ddu10e0u10dbu10d0u10eau10d8u10d8u10e1 u10dbu10d8u10e1u10d0u10e6u10d4u10d1u10d0u10d3, u10d2u10d7u10eeu10ddu10d5u10d7, u10d0u10d8u10e0u10e9u10d8u10ddu10d7:","platform":"kommunicate"}}],"outputContexts":[{"name":"projects/usa2bot-emqd/agent/sessions/57925473/contexts/actions-followup","lifespanCount":2},{"name":"projects/usa2bot-emqd/agent/sessions/57925473/contexts/system_counters","lifespanCount":1,"parameters":{"no-input":0,"no-match":0}}],"intent":{"name":"projects/usa2bot-emqd/agent/intents/3bf1bb94-7000-4122-a3fc-78efcee19f63","displayName":"actions"},"intentDetectionConfidence":1,"languageCode":"en"},"originalDetectIntentRequest":{"payload":{"messageSource":"2","botId":"usa2georgia-bot-ahpos","attachments":[],"groupId":"57925473","applicationId":"174afd6c613bbb5be0bbd725cafbe88"}},"session":"projects/usa2bot-emqd/agent/sessions/57925473"} white_check_mark eyes raised_hands

1. Added the Rich Messages Video Template Feature.

We have two types of payloads to play videos in our sdk.

1. Payload for web hosted videos
2. Payload for Youtube videos

Below is the sample custom payload in our documentation. Doucmentation link for Rich Video Template

{
  "platform": "kommunicate",
  "message": "Hello this is example videos",
  "metadata": {
    "contentType": "300",
    "templateId": "14",
    "payload": [
      {
        "url": "https://s3-migration-dot-applozic.appspot.com/rest/ws/aws/file/AM
Ifv95BPKLnhNtiYz0SNJYXTDhUkvhPYQikSjFaoL1hbg1zCcK8n6KZZfZC5Z42bfxOLaNeKSbKrt4o9pI0_ICb1fKKY8HqtcCeEuUZU8b18u8sr-4U5d4rFtmC79cn_0xaiV0MQfF01T0hAea8sQANoaYuvR5hQJHiFSB047yp1mkfqcwNb_ExaX1xutdJ8Qamkjp8xTKjlPiG0920T7qqLFIBxl1eGL7ikvTCtXG_f8Me8OKsEOhUXOP7LLuJLcOG_p8cijsp",
        "caption": "Video & Youtube Examples"
      },
      {
        "source": "youtube",
        "url": "https://www.youtube.com/embed/3-ijFzzF934"
      }
    ]
  }
}

Sample Images:

Sample Video:

https://user-images.githubusercontent.com/61688116/144352056-418bd8a1-7ad5-41d7-b971-610af4685d39.mp4

Hello,

I am integrating the Kommunicate Flutter SDK and I'm currently having a problem with the localization on the Android side. I'm successfully translating most of the resources to French and it seems to me that we are not able to use a customized string for the hint "Write a Message.." used at the bottom of this screen.

The string resource that seems to mean to be edited is enter_message_hint in mobicom_strings.xml but it is never used.

I think that this part of the code is the problem :

messageEditText.setHint(!TextUtils.isEmpty(alCustomizationSettings.getEditTextHintText()) ? alCustomizationSettings.getEditTextHintText() : getString(R.string.enter_message_hint));

as alCustomizationSettings.getEditTextHintText() is never Empty and contains "Write a Message.."

• Added functionality to update conversation metadata via conversation builder
• Added functionality to update conversationAssignee if a different assignee is passed in the conversation builder
• Moved the updates into parallel tasks so it doesn't affect the response time of conversation builder
• Use the below method to update conversation metadata:

  Map<String, String> map = new HashMap<>();
            map.put("TicketId", "123456");
            map.put("Status", "ActiveNo");

            new KmConversationBuilder(context)
                    //other properties might go here
                    .setConversationAssignee(newAssignee)
                    .setConversationMetadata(map)
                    .launchConversation(new KmCallback() {
                        @Override
                        public void onSuccess(Object message) {
            
                        }

                        @Override
                        public void onFailure(Object error) {
                            
                        }
                    });

Below test cases are satisfied:

1. If this is a new conversation, the conversation will be created and the above metadata will be set.
2. If this is an existing conversation, this metadata will be set, if conversation does not have metadata this metadata
3. If the values change or new metadata is passed, the metadata will be updated accordingly.
4. If same metadata is passed, no update occurs.

We have been a long time with an old version of your library. Now, we have upgraded to the latest version and the library crashes on all the devices we have with API 16, 17 and 18. We have also tested your test app and it crashes as well.

The problem is in the org.eclipse.paho.client.mqttv3 library version. Version 1.2.1 and higher do not seem to support API < 19, because they use StandarCharsets and StandarCharsets was added in API 19.

For now we have fixed it by forcing the library version in our build.gradle, while we hope you can release a new version with the problem fixed.

implementation('org.eclipse.paho:org.eclipse.paho.client.mqttv3') { version { strictly '1.2.0' } }

Stacktrace

2022-09-01 13:44:41.062 1993-2336/xxx.xxxxx.xxxxxx E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #4
    java.lang.RuntimeException: An error occured while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:299)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:352)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:219)
        at java.util.concurrent.FutureTask.run(FutureTask.java:239)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
        at java.lang.Thread.run(Thread.java:856)
     Caused by: java.lang.ExceptionInInitializerError
        at org.eclipse.paho.client.mqttv3.internal.ClientState.<init>(ClientState.java:162)
        at org.eclipse.paho.client.mqttv3.internal.ClientComms.<init>(ClientComms.java:108)
        at org.eclipse.paho.client.mqttv3.MqttAsyncClient.<init>(MqttAsyncClient.java:470)
        at org.eclipse.paho.client.mqttv3.MqttAsyncClient.<init>(MqttAsyncClient.java:320)
        at org.eclipse.paho.client.mqttv3.MqttAsyncClient.<init>(MqttAsyncClient.java:315)
        at org.eclipse.paho.client.mqttv3.MqttClient.<init>(MqttClient.java:227)
        at com.applozic.mobicomkit.api.AlMqttClient.<init>(AlMqttClient.java:21)
        at com.applozic.mobicomkit.api.ApplozicMqttService.connect(ApplozicMqttService.java:94)
        at com.applozic.mobicomkit.api.ApplozicMqttService.connectPublish(ApplozicMqttService.java:126)
        at com.applozic.mobicomkit.api.conversation.ApplozicMqttIntentService.onHandleWork(ApplozicMqttIntentService.java:104)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:396)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:387)
        at android.os.AsyncTask$2.call(AsyncTask.java:287)
        at java.util.concurrent.FutureTask.run(FutureTask.java:234)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573) 
        at java.lang.Thread.run(Thread.java:856) 
     Caused by: java.lang.NoClassDefFoundError: java.nio.charset.StandardCharsets

Hi, My app targets android 12 and I use the latest version of sdk 2.3.0. Users ran into an issue when push notification comes:

Caused by java.lang.IllegalArgumentException <my.app.package>: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent. Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.

android.app.PendingIntent.checkFlags (PendingIntent.java:382)
android.app.PendingIntent.getActivityAsUser (PendingIntent.java:465)
android.app.PendingIntent.getActivity (PendingIntent.java:451)
android.app.PendingIntent.getActivity (PendingIntent.java:415)
com.applozic.mobicomkit.api.notification.NotificationService.notifyUserForNormalMessage (NotificationService.java:402)
com.applozic.mobicomkit.broadcast.BroadcastService.sendNotificationBroadcast (BroadcastService.java:184)
com.applozic.mobicomkit.api.conversation.MobiComMessageService.sendNotification (MobiComMessageService.java:249)
com.applozic.mobicomkit.api.conversation.MobiComMessageService.addMTMessage (MobiComMessageService.java:230)
com.applozic.mobicomkit.api.conversation.MobiComMessageService.processMessage (MobiComMessageService.java:136)
com.applozic.mobicomkit.api.conversation.MobiComMessageService.syncMessages (MobiComMessageService.java:297)
com.applozic.mobicomkit.api.conversation.ConversationIntentService.onHandleWork (ConversationIntentService.java:84)
androidx.core.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:396)
androidx.core.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:387)
android.os.AsyncTask$3.call (AsyncTask.java:394)
java.util.concurrent.FutureTask.run (FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:920)

Note: the code has been checked only for the template ids: 3, 6, 7, 9, 10 i.e excluding 11 and faq. non-generic messages have not been checked. Messages are rendered as required for payloads given in docs.

1. a new one step image/video upload flow has been added (open the image chooser, select multiple images/videos and click open), required files have been modified
2. the MobicomAttachmentSelectorActivity has be modified to better seperate and UI and the controlling fucntions
3. The file async task has been improved to be more generic and moved to a seperate file
4. the KmAttachmnetsControllr has been created to seperate the code( refer to point 2) and the functions common between the new flow and the old flow
5. comments have been added where ever i found difficulty in understanding in what the function did (only for the attachment upload parts)

Issue:

• Device was sending 2 device-key from 2 different API: For Agent app: /loginv2 and register/update For SDK: register/client and register/update

Fix:

• We were earlier sending x-authorization which is not required in register/update.
• Changing this boolean will send device-key to the API connection.setRequestProperty(DEVICE_KEY_HEADER, userPreferences.getDeviceKeyString());

Issue with Notification:

1. Assignment messages are not coming
2. Notifications are received even when chat is assigned to Bot
3. For "Notify everybody" - Agents are receiving notification for all messages, same in Android and Web, except the assignment message (edited)

How was the code tested?

• Compared with dashboard and tested it for Agent app - Notify Everybody and Automatic assignment feature
• Tested SDK notification flow

Summary

• Observe events -> message, attachment message, agent leave
• Added chat log logic to sync zendesk and kommunicate messages

Tasks completed:

• When message event triggered, send message to /rest/ws/zendesk/message/send
• When attachment event triggered, send attachment to /rest/ws/zendesk/file/send
• When Agent ends chat from Zendesk, call Resolve conversation API and resolve the conversation.
• When "Restart conversation" is clicked, a new conversation is created to maintain a single chat thread.
• Handled Chat logs -> If the app is closed and opened again, it will sync the messages sent from Zendesk dashboard