Skip to main content

 Crashlitics has reported a `FileNotFoundException` on Android, the resource can not be downloaded within the browser either.

Androdi SDK version: 15.7.0

Fatal Exception: java.io.FileNotFoundException: https://downloads.intercomcdn.com/i/o/1052073407/eabcb799a0515a981f18b011/IMG-20240515-WA0067.jpg
       at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255)
       at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211)
       at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30)
       at com.google.firebase.perf.network.InstrURLConnectionBase.e(InstrURLConnectionBase.java:24)
       at com.google.firebase.perf.network.InstrHttpsURLConnection.getInputStream(InstrHttpsURLConnection.java:3)
       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.prepareBitmap(PreviewViewModel.kt:17)
       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$prepareBitmap(PreviewViewModel.kt)
       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend(PreviewViewModel.kt:18)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:14)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:94)
       at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:4)
       at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
       at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.java:98)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:98)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:98)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:98)

 

Hi @Engineering Support -- Cam from the Intercom Support team here!

I believe the issue you’re seeing is related to a known bug which our Product Support team released a fix for in our most recent Android SDK update - v.15.9.0.

Could you try updating to this most recent SDK version and let me know if you’re still seeing this issue?


Reply