Skip to main content

Today we start receiving reports of crashes when intercom is opened, it seems to be something to do with a API response:

 

Stacktrace received:

java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType

at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:46)

at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:39)

at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:202)

at retrofit2.Retrofit$1.invoke(Retrofit.java:160)

at java.lang.reflect.Proxy.invoke(Proxy.java:1006)

at $Proxy2.getHomeCardsSuspend()

at io.intercom.android.sdk.api.MessengerApi$DefaultImpls.getHomeCardsSuspend$default(MessengerApi.kt:181)

at io.intercom.android.sdk.homescreen.HomeViewModel$onUiCreated$1.invokeSuspend(HomeViewModel.kt:60)

at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)

at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)

at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)

at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

 

We are using the 10.6.3 version, a few months ago we have to downgrade to this version because of this issue:

 

https://forum.intercom.com/s/question/0D75c000005avgJCAQ/detail?fromEmail=1amp;s1oid=00Do0000000Yp25&s1nid=0DB2G000000XZEa&s1uid=0055c000009C4Np&s1ext=0&emkind=chatterCommentNotification&emtm=1657132116333

 

We are looking to upgrade for the latest version, but will take some time.

 

May this issue be related to the newest android sdk version released today?

Hey @douglas g​! Daniel from Customer Support Engineering here 🔧 

 

My best recommendation here would be to update to the newest version of our SDK, as it will contain in fixes for crashes and bugs. I can't guarantee that it will solve this particular issue, but it is always our fist port of call. Even before this this, I would suggest revising your configuration to ensure that it is in line with our installation docs. Failing that, could you please contact us via the Messenger about the issue, supplying as much detail as possible including the device you tested on, the Android OS version, and how many devices/networks you've tested this on? Thank you!

Reply


Terms & ConditionsCookie settings