Hi,
So I’ve implemented the Intercom SDK into our Android app the past few days and stumbled in to a strange thing.
The SDK crash as I’m trying to open the write message view with this error.
java.lang.NoSuchMethodError: No static method FlowRow(Landroidx/compose/ui/Modifier;Landroidx/compose/foundation/layout/Arrangement$Horizontal;Landroidx/compose/foundation/layout/Arrangement$Vertical;IILandroidx/compose/foundation/layout/FlowRowOverflow;Lkotlin/jvm/functions/Function3;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/foundation/layout/FlowLayoutKt; or its super classes (declaration of 'androidx.compose.foundation.layout.FlowLayoutKt' appears in /data/app/~~MDeJzUHvf74b7jpNmGq6Rw==/com.*.staging-7N_jvukfhGCaqNo-t2IqvQ==/base.apk)
at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.QuickReplies(QuickReplies.kt:38)
at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.ComposerSuggestions(QuickReplies.kt:88)
at io.intercom.android.sdk.m5.conversation.ui.components.row.ComposerSuggestionsRowKt.ComposerSuggestionsRow(ComposerSuggestionsRow.kt:15)
at io.intercom.android.sdk.m5.conversation.ui.components.MessageListKt.MessageList(MessageList.kt:369)
at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$30$4$1.invoke(ConversationScreen.kt:629)
at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$30$4$1.invoke(ConversationScreen.kt:601)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.kt:130)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.kt:51)
This is happening on 15.15.0, 15.14.0, 15.13.0, 15.12.0.
So opening the Intercom Home space works. And I can see 2 buttons, Messages and write new message.
Tapping write new kills the SDK and Message → new message also kills it.
I’m developing on a very new codebase. But that should not matter in my opinion.
I’m on compose 1.8.0-rc02 (but this crash is on 1.8.0-rc01 too).
Kotlin 2.1.20 and we compile agains SDK 36 (But SDK 35 also also fails).
Edit: Happens in both debug and signed builds.
I’ve found that downgrading compose to 1.7.8 seem to have fixed the issue.
But I’m using features provided in 1.8.0-x.
Would like to see if there’s something you can do to fix this.
Hey @Curwer Paul here 👋
I appreciate you letting us know that downgrading to Compose 1.7.8 fixed the issue, though I understand this isn't ideal since you need features from 1.8.0.
You're absolutely right that this is something we need to address on our end. The issue occurs because our SDK currently uses an older implementation with a different method signature than what's in Compose 1.8.0.
I'll raise this with the team for review. Thank you.
Please fix this asap 🙏 We are unable to downgrade compose and this is causing a lot of crashes everyday, driving down our crash-free users statistics massively.
Hey @Paul Byrne. I’ve just tested 15.16.0 release just recently.. This issue still happen.
I’d like to point out that the FlowRow that is used in this library is annotated by google as experimental. And with that they warn us that the api could change aka not stable.
I need to question the use of a experimental api in such a large library. The difference between changing a stable and experimental api is if a stable is changed the old implementation is marked as deprecated and still work for some time before removed so devs have time to move to the new version. But experimental versions will just be changed without notice and not keeping the old implementation.
So for projects that use newer apis like we get stuck and need to wait for the the api to be updated.
I understand why you use the latest stable version of compose, and not questioning that.
But maybe you could have a beta version of your library published with the newer version on compose?
Or change the FlowRow for a LazyRow? Understand that you lose the content wrapping, but it would unblock all users. Making both old and new compose work.
Thanks and hope to hear from you soon.
edit: Typo in version tested
We just launched Intercom into our prod app and are now experiencing this crash and our users cannot message us 😬. Is there a timeline on a fix for this?
Same issue here. Our Android app (millions of users) crashes when people try to message us. We just integrated Intercom and have been so happy with it, but this is causing us some major pain. Please fix ASAP or provide a workaround, thanks!
@Paul Byrne any update on this? The 1.8 version of Compose is no longer in RC and is now stable and released.
We are in a bit of a bind as the 1.8 version has some bug fixes that resolve other issues we have, yet if we use it then our users can’t use Intercom functions in the app..
Actually, just tested with 1.8 again and it seems like I am no longer running into Intercom crashes.
Hey @Paul Byrne.
Do you have any plans about this issue?
Stable version of Compose 1.8.0 has been released, so I hope this crash to be resolved as soon as possible.
Thanks.
I’ve just updated to 1.8 stable. Running intercom 15.16.0 and the sdk still crash for me.
I’ve tried a clean build (removed build folder) with the same issue on the flow row.
I’ve also just for the fun of it tried the new Compose alpha 1.9.0-alpha01 just to see if I would get any other error but no. Still the same flow row crash.
@Paul Byrne Please make this a prio.
Showing this: UI tests failed due to either "java.lang.NoSuchMethodError: No static method forceEnableAppTracing()" and "java.lang.NoClassDefFoundError: androidx.test. App
Hi team, do you have a timeline for a release to support Compose 1.8 stable? We have some features we’d like to start depending on the new APIs, and we’re blocked on the Intercom SDK due to this crash.
@Paul Byrne It’s been a few days now since the release of stable 1.8 Compose.
Any updates on the progress here?
I received a response from Intercom team saying they've confirmed this issue and added it to their backlog.
They explained that their product team prioritizes bugs based on severity and impact, and issues like this might take several weeks to address depending on their current workload and upcoming feature releases.
They've logged the problem and will reach out once there's any update.
They said if I don't hear back, it means the engineering team is still working on it.
This has been fixed with the release of 15.16.1
Thanks
This has been fixed with the release of 15.16.1
Thanks
Are you doing any additional dependency resolution? Because I’m still seeing the same issue on 15.16.1 in my app.
@Paul Byrne
The release notes say that you guys updated to compose 1.8.0 via 2025.04.00 BOM, which is impossible, because 2025.04.00 is 1.7.8.
The correct BOM for compose 1.8.0 would’ve been 2025.04.01.
The crash is still in release 15.16.1 as a result.
Please give this fix urgency, because it’s holding back our release.
This has been fixed with the release of 15.16.1
Thanks
Are you doing any additional dependency resolution? Because I’m still seeing the same issue on 15.16.1 in my app.
No nothing speciell on my end sorry.
I tried both with compose 1.8.0 and 1.9.0-alpha1 both worked.
The view I saw crashing was the message composer view. Maybe it’s different from what you see?
This has been fixed with the release of 15.16.1
Thanks
Are you doing any additional dependency resolution? Because I’m still seeing the same issue on 15.16.1 in my app.
No nothing speciell on my end sorry.
I tried both with compose 1.8.0 and 1.9.0-alpha1 both worked.
The view I saw crashing was the message composer view. Maybe it’s different from what you see?
Ask a Question is where I’m crashing.
@Tim Bay You’re right.
BOM 2025.04.00 has 1.7.8 versions of Jetpack Compose yet, so this crash still occurs on 15.16.1. 😥
They should use BOM version 2025.04.01 which contains 1.8.0 versions.
@Paul Byrne Would you please give us some infos or plans about this?
Ohh yeah I just had a crash too..
@Paul Byrne Same as before.
Compose 1.8.1 was release yesterday.
Good news.
Release 1.16.0 was released 3h ago with compose 1.8.1 (BOM 2025.05.00).
I’m not seeing any more issues with flow row crashing.
