App is crushed on Android - No view found for id 0x77 (unknown) for fragment AppcuesWrapperFragment

[morAtStampli]

Hi,
i am encountering an same issue with version 4.4.4

error - >
No view found for id 0x77 (unknown) for fragment AppcuesWrapperFragment{fa93181} (1880fa72-8c2b-46da-aec0-cc4112b699d9 id=0x77 tag=119)

My App is in ->
"react-native": "0.78.0",
"react": "19.0.0",
"@appcues/react-native": "^4.4.4",

it is happening when i am navigating from the first route the any second route.
any leads on this ?

IOS is working ok.
this is blocking me from deploying my app to google console.

[iujames]

Hi @morAtStampli , thank you for the details here. We'll need to investigate this one and see if we can find a root cause. If you have any minimal reproducible project example that can consistently repro the issue, that would be very helpful as well. It seems like this is the same or highly related to #132 as well, and I see your comment there. We'll take a look!

[morAtStampli]

Hi @iujames ,
i will try to see if i can share a test project.
any way i didn't see in the other issue that you resolve it
so this issue is still open in general or you find solution for it ?

[iujames]

@morAtStampli the previous changes were intended to address this issue, but no, we did not confirm it was fully resolved. As I recall, it was a tricky one to reproduce and track down. But since you've provided more feedback here that it is occurring in your project as well, we can continue to pursue a solution.

[crrobinson14]

We are experiencing this as well. Let us know what you need debug-wise and we'll provide a repro.

[iujames]

Thanks @crrobinson14 - we have an example app in this project, and have not had much luck reproducing this issue consistently in there. If there is a way to see this issue in that example, or any other minimal reproducible example project, that would certainly help pinpoint the issue.

[crrobinson14]

I will try to create a repro this afternoon. One difference that does leap out from your example is that we're using Expo 53.0.18 here. Perhaps @morAtStampli can weigh in on what they're using as well.

[crrobinson14]

Update: We've made a repro but it's not happening in there. To try to make things easier to diagnose, our repro excludes things that require special configs to run, like Firebase, Google Login, and so on. Given that, it seems likely that the issue is an interaction between AppCues and some other module. We're still working on identifying the precise mix that causes the issue, but here's a diff of what our repro (working) project removed if anybody wants to dig further:

@chatwoot/react-native-widget
@datadog/mobile-react-native
@datadog/mobile-react-navigation
@react-native-firebase/analytics
@react-native-firebase/app
@react-native-firebase/database
@react-native-firebase/firestore
@react-native-firebase/messaging
@react-native-google-signin/google-signin
@stripe/stripe-react-native

We are working on expanding the repro until it reliably reproduces the issue. Perhaps then we'll also identify any potentially conflicting module.

[crrobinson14]

Here is the stack trace of a crash event in case it's helpful. Note that this happens only on Android.

java.lang.RuntimeException: Unable to pause activity {com.mydomain.MyApp/com.mydomain.MyApp.MainActivity}: java.lang.IllegalArgumentException: No view found for id 0xbe (unknown) for fragment AppcuesWrapperFragment{f6086b6} (15a736e9-02ff-4739-9459-1157e7ccbe68 id=0xbe tag=190)
  android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:5766)
  android.app.ActivityThread.performPauseActivity(ActivityThread.java:5717)
  android.app.ActivityThread.handlePauseActivity(ActivityThread.java:5669)
  android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:60)
  android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
  android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
  android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
  android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
  android.app.ActivityThread$H.handleMessage(ActivityThread.java:2773)
  android.os.Handler.dispatchMessage(Handler.java:109)
  android.os.Looper.loopOnce(Looper.java:232)
  android.os.Looper.loop(Looper.java:317)
  android.app.ActivityThread.main(ActivityThread.java:8934)
  java.lang.reflect.Method.invoke(Native Method)
  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
  com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911)
Caused by java.lang.IllegalArgumentException: No view found for id 0xbe (unknown) for fragment AppcuesWrapperFragment{f6086b6} (15a736e9-02ff-4739-9459-1157e7ccbe68 id=0xbe tag=190)
  androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:567)
  androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:286)
  androidx.fragment.app.FragmentStore.moveToExpectedState(FragmentStore.java:114)
  androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1685)
  androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:3319)
  androidx.fragment.app.FragmentManager.dispatchPause(FragmentManager.java:3255)
  androidx.fragment.app.FragmentController.dispatchPause(FragmentController.java:296)
  androidx.fragment.app.FragmentActivity.onPause(FragmentActivity.java:284)
  com.facebook.react.ReactActivity.onPause(ReactActivity.java:52)
  android.app.Activity.performPause(Activity.java:9294)
  android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1781)
  android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:5756)
  android.app.ActivityThread.performPauseActivity(ActivityThread.java:5717)
  android.app.ActivityThread.handlePauseActivity(ActivityThread.java:5669)
  android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:60)
  android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
  android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
  android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
  android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
  android.app.ActivityThread$H.handleMessage(ActivityThread.java:2773)
  android.os.Handler.dispatchMessage(Handler.java:109)
  android.os.Looper.loopOnce(Looper.java:232)
  android.os.Looper.loop(Looper.java:317)
  android.app.ActivityThread.main(ActivityThread.java:8934)
  java.lang.reflect.Method.invoke(Native Method)
  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
  com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911)```

[crrobinson14]

This is absolutely not a fix (probably breaks Android functionality) but commenting out this block in node_modules/@appcues/react-native/android/src/main/java/com/appcuesreactnative/AppcuesFrameWrapper.kt bypasses the issue on Android (without requiring removal of Appcues itself from the project):

   private val addFragment = Runnable {
        if (!fragmentCreated) {
          try {
              val wrapperFragment = AppcuesWrapperFragment(contentView)
            val activity = (context as? ThemedReactContext)?.currentActivity as FragmentActivity
//            activity.supportFragmentManager
//              .beginTransaction()
//              // the id value here is the react native view id that
//              // has been assigned by the view manager system for this view instance
//              .replace(id, wrapperFragment, id.toString())
//              .commitNow()

As far as I can tell at this point, there is some type of race condition or rendering issue here. I don't know why onPause gets fired on Android while the app is starting, but that event bubbles up through the call stack shown above and ends up in ActivityThread ::performPauseActivityIfNeeded (Android native source code from Google, c.f. https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/ActivityThread.java#5766). I'm super rusty on Android native code and Kotlin in particular but it looks like this routine is trying to emit pause events to various activities registered with it. When it tries to do this with the Appcues wrapper fragment, something is either not registered "yet" or "properly" and we end up in the generic catch at https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/ActivityThread.java#5786 which we can confirm via the Unable to pause activity error.

Commenting out the AppCues attempt to register its Android fragment with the fragment manager breaks some AppCues functionality but does prevent the app from crashing, which hopefully is diagnostic here.

[morAtStampli]

** closed by mistake (please reopen this @iujames)

@crrobinson14
thanks a lot for sharing and helping to figure it out.
i am still facing the same issue, the app crushed on every page.

i am thinking to reach appcues to find some alternatives.

Screen.Recording.2025-07-21.at.16.40.13.mov