Issue with Intercom Android SDK 15.6.1

  • 16 February 2024
  • 3 replies
  • 37 views

We are experiencing a few crashes with the following exception on Intercom Android SDK 15.6.1. Can you help handle the exception gracefully?

 

Fatal Exception: java.net.MalformedURLException: no protocol: 
at java.net.URL.<init>(URL.java:601)
at java.net.URL.<init>(URL.java:498)
at java.net.URL.<init>(URL.java:447)
at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.prepareBitmap(PreviewViewModel.kt:114)
at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$get_state$p(PreviewViewModel.kt:33)
at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$prepareBitmap(PreviewViewModel.kt:33)
at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend(PreviewViewModel.kt:68)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)

 

mateusz.leszkiewicz 1 month ago

Hi there,

I can’t be 100% sure if the update resolves the issue, but if you do that and the issue persists, please reach out to us via Messenger, and we will try to figure this out together.
 

View original

3 replies

Userlevel 2
Badge +3

Hi there, It’s Mat from the Support Engineering Team 😀

Can you please update your SDK to 15.6.2 (the latest SDK) and check if the issue persists?

If not, please reach out to us via Messenger to further investigate the issue.

Hi Mateusz,

The changelog of 15.6.2 and 15.6.3 doesn’t indicate this issue was fixed. Can you verify if it was resolved?

Userlevel 2
Badge +3

Hi there,

I can’t be 100% sure if the update resolves the issue, but if you do that and the issue persists, please reach out to us via Messenger, and we will try to figure this out together.
 

Reply