Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

facing issue sending algolia insight events #189

Closed
phm1015 opened this issue May 19, 2020 · 9 comments · Fixed by #190
Closed

facing issue sending algolia insight events #189

phm1015 opened this issue May 19, 2020 · 9 comments · Fixed by #190

Comments

@phm1015
Copy link

phm1015 commented May 19, 2020

I am trying to send click and conversion events to algolia for personalization
I am using "convertedObjectIDsAfterSearch" and "clickedObjectIDsAfterSearch" methods for sending events to algolia.

But its causing problems in device having android version 5 and 6.

below is error details

Process: com.example.myapplication, PID: 7659
java.lang.VerifyError: Rejecting class com.algolia.search.model.insights.InsightsEvent$Companion because it failed compile-time verification (declaration of 'com.algolia.search.model.insights.InsightsEvent$Companion' appears in /data/app/com.example.myapplication-1/base.apk)
at com.algolia.search.model.insights.InsightsEvent.(InsightsEvent.kt)
at com.algolia.search.endpoint.EndpointInsightsUserImpl.clickedObjectIDsAfterSearch(EndpointInsightsUserImpl.kt:94)
at com.algolia.search.client.ClientInsights$User.clickedObjectIDsAfterSearch(ClientInsights.kt)
at com.algolia.search.endpoint.EndpointInsightsUser$DefaultImpls.clickedObjectIDsAfterSearch$default(EndpointInsightsUser.kt:97)
at com.example.myapplication.MainActivity$searchItemClickEvent$2.invokeSuspend(MainActivity.kt:51)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

@aallam
Copy link
Member

aallam commented May 19, 2020

Hello @phm1015,
Thank you for reporting the issue. The compiler seems to generate some code that is not compatible with older Android JVMs. We are working on a fix to resolve this issue.

@phm1015
Copy link
Author

phm1015 commented May 19, 2020

@aallam also one more thing to add
this works fine in android 4.2.2 version(api 19)

hope this might help

@aallam
Copy link
Member

aallam commented May 19, 2020

@phm1015 - please try the new beta version 1.4.0-beta04, it should fix this issue.

@phm1015
Copy link
Author

phm1015 commented May 19, 2020

@phm1015 - please try the new beta version 1.4.0-beta04, it should fix this issue.

@aallam thanks for feedback

@phm1015
Copy link
Author

phm1015 commented May 19, 2020

Was there any specific reason why it was working in android 4.2.2 and not android 5?

@aallam
Copy link
Member

aallam commented May 19, 2020

Was there any specific reason why it was working in android 4.2.2 and not android 5?

Android runtime has changed between these two versions: Dalvik for Android 4.4 and below and ART for later versions

@phm1015
Copy link
Author

phm1015 commented May 20, 2020

OK but it was causing problems in 5 and 6 mostly and was working fine in later versions like android 8 ,9 etc.

@aallam
Copy link
Member

aallam commented May 20, 2020

OK but it was causing problems in 5 and 6 mostly and was working fine in later versions like android 8 ,9 etc.

The bug seems in the early versions of ART

@phm1015
Copy link
Author

phm1015 commented May 20, 2020

OK but it was causing problems in 5 and 6 mostly and was working fine in later versions like android 8 ,9 etc.

The bug seems in the early versions of ART

@aallam thanks for the detailed update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants