[$8000] Investigate: 💥 Crash 💥 com.facebook.react.uimanager.ViewGroupManager.addView

[melvin-bot]

Firebase has reported a new crash that we need to fix, here are all the details we found:

Fatal Exception: java.lang.IllegalStateException

java.lang.IndexOutOfBoundsException: index=1 count=0

ViewGroupManager.java line 37 com.facebook.react.uimanager.ViewGroupManager.addView

Number of Crashes: 1

Device Information

• Platforms: Android
• App Versions: 1.2.0-4
• Devices: Xiaomi MI MAX 3 10

Stacktraces

Android 1.2.0-4

com.facebook.react.bridge.ReactContext.handleException (ReactContext.java:429)
com.facebook.react.bridge.ReactContext$ExceptionHandlerWrapper.handleException (ReactContext.java:436)
com.facebook.react.bridge.GuardedRunnable.run (GuardedRunnable.java:32)
android.os.Handler.handleCallback (Handler.java:883)
android.os.Handler.dispatchMessage (Handler.java:100)
android.os.Looper.loop (Looper.java:224)
android.app.ActivityThread.main (ActivityThread.java:7562)
java.lang.reflect.Method.invoke
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:539)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:950)

---

Internal Firebase Info

💥 DO NOT EDIT THIS SECTION 💥

Crash IDs: 3726e8c3029fce9bad93718c70e3cd7c
Exception: java.lang.IndexOutOfBoundsException: index=1 count=0

[melvin-bot]

Triggered auto assignment to @adelekennedy (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

@adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[adelekennedy]

internal
external

[melvin-bot]

Current assignee @adelekennedy is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

[melvin-bot]

Triggered auto assignment to @tgolen (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[tgolen]

Still looking for proposals

[tgolen]

Still ^

[tgolen]

I think the price of this should double @adelekennedy ?

[adelekennedy]

Still waiting on proposals

[melvin-bot]

@tgolen, @mananjadhav, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

[adelekennedy]

Doubling again!

[adelekennedy]

waiting on proposals but not time to double yet

[melvin-bot]

@tgolen, @mananjadhav, @adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@tgolen, @mananjadhav, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

[tgolen]

Still no proposals. It's fine to let this keep doubling.

[adelekennedy]

Doubling time!

[tgolen]

Waiting for proposals still

[melvin-bot]

@tgolen, @mananjadhav, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

[mananjadhav]

Still waiting for proposals

[adelekennedy]

And we're doubling again!

[Justicea83]

The crash doesn't have enough context, I did a bit of digging and realized it has to do with the zIndex of views. Saw an SO here. The error is coming from here.

[mananjadhav]

Thanks @Justicea83.

A couple of things here,

1. I spent time in digging the root cause, trying to reproduce but I couldn't. We have a similar issue for zIndex property here

@adelekennedy @tgolen Coming from this thread it mentions we cap the Crash 💥 issues for $500. I know @tgolen mentioned earlier no caps. But wanted to double check if we should be doubling it?

3. Another question, does the Number of Crashes update when multiple crashes are reported? Currently it says 1, and the version as 1.2.0-4, where as we're at: v1.2.21-4. Do you think closing this out might also be an option?

[tgolen]

Do you think closing this out might also be an option?

I think we can close it if there hasn't been any more instances of the crash. I looked in Crashlytics and found that this crash only happened once on Sep 19, and hasn't happened since. Because of that, I am going to close this issue.

[tgolen]