Our roadmap for this year is already full , depending the update we will have to do on our API/SDK, we may find the place to add it in a release this year. But no guarantee
Original Message:
Sent: 02-06-2026 09:27
From: Mei Tan
Subject: Web Messaging Java SDK failing silently
Hi @Frederic Thomas,
Thanks for the reply. For now, the engineering team has decided to build out the connection and bypass the SDK, but long term, we would definitely like to switch to using the Java SDK to future proof our implementation. Another feedback is whether the SDK repo could contain some unit and integration tests that can help engineers test the implementation?
When you said that it could take some time to release this, do you have some estimate, for example within the year?
Thanks,
Mei
------------------------------
Mei Tan
Senior Solutions Architect
Original Message:
Sent: 02-05-2026 11:50
From: Frederic Thomas
Subject: Web Messaging Java SDK failing silently
Hi @Mei Tan,
I take a note and capture your request to provide more info when it's failed.
By that time we will adress it (and to be honest it could take some time to release it) , if you provide more information on the issue you are facing we can try to help you moving forward in your implementation
regards
------------------------------
Frederic Thomas
Senior Manager, Development
Original Message:
Sent: 01-29-2026 10:42
From: Mei Tan
Subject: Web Messaging Java SDK failing silently
We're trying to get Genesys web messaging integrated into our own UI, using the Genesys Java SDK GitHub - MyPureCloud/web-messaging-sdk-java. When attempting to execute even the sample code that has been provided in the Genesys SDK doc, the code just completes with no respond being sent back from Genesys. The SDK seems to fail silently because there are methods in the WebMessagingClient that are catching exceptions but not throwing them back;
public void configureSession(String deploymentId, String token, String origin, String tracingId, Optional<Boolean> startNew) { try { this.token = token; this.deploymentId = deploymentId; if (apiClient == null) { initializeApiClient(origin); } // Create configuration request ConfigureSessionRequest configureSessionRequest = new ConfigureSessionRequest(); configureSessionRequest.setAction(RequestTypeConfigureSession.CONFIGURESESSION); configureSessionRequest.setDeploymentId(deploymentId); configureSessionRequest.setToken(token); configureSessionRequest.setTracingId(tracingId); startNew.ifPresent(boolValue -> configureSessionRequest.setStartNew(boolValue)); String payload = objectMapper.writeValueAsString(configureSessionRequest); webSocket.sendText(payload, true); } catch (JsonProcessingException e) { // no-op } }
It's difficult to get a full view of what the issue may be without the exception being thrown. Has anyone had any success with this SDK and what have you done to resolve the silent failure?
Even if it's because the parameters passed in such as origin is wrong, it would be nice to get an error to indicate that.
#WebMessaging
------------------------------
Mei Tan
Senior Solutions Architect
------------------------------