[$2000] Investigate: 💥 Crash 💥 `com.facebook.react.uimanager.ViewManagersPropertyCache$FloatPropSetter.getValueOrDefault`

[melvin-bot]

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

Fatal Exception: com.facebook.react.bridge.JSApplicationIllegalArgumentException

Error while updating property 'zIndex' of a view managed by: RCTView

ViewManagersPropertyCache.java line 250 com.facebook.react.uimanager.ViewManagersPropertyCache$FloatPropSetter.getValueOrDefault

Number of Crashes: 4

Device Information

• Platforms: Android
• App Versions: 1.2.3-0
• Devices: Google AOSP on IA Emulator 9

Stacktraces

Android 1.2.3-0

com.facebook.react.uimanager.ViewManagersPropertyCache$PropSetter.updateViewProp (ViewManagersPropertyCache.java:101)
com.facebook.react.uimanager.ViewManagerPropertyUpdater$FallbackViewManagerSetter.setProperty (ViewManagerPropertyUpdater.java:136)
com.facebook.react.uimanager.ViewManagerPropertyUpdater.updateProps (ViewManagerPropertyUpdater.java:56)
com.facebook.react.uimanager.ViewManager.updateProperties (ViewManager.java:48)
com.facebook.react.uimanager.ViewManager.createViewInstance (ViewManager.java:144)
com.facebook.react.uimanager.ViewManager.createView (ViewManager.java:77)
com.facebook.react.uimanager.NativeViewHierarchyManager.createView (NativeViewHierarchyManager.java:281)
com.facebook.react.uimanager.UIViewOperationQueue$CreateViewOperation.execute (UIViewOperationQueue.java:194)
com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.dispatchPendingNonBatchedOperations (UIViewOperationQueue.java:1110)
com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded (UIViewOperationQueue.java:1081)
com.facebook.react.uimanager.GuardedFrameCallback.doFrame (GuardedFrameCallback.java:29)
com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame (ReactChoreographer.java:175)
com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame (ChoreographerCompat.java:85)
android.view.Choreographer$CallbackRecord.run (Choreographer.java:947)
android.view.Choreographer.doCallbacks (Choreographer.java:761)
android.view.Choreographer.doFrame (Choreographer.java:693)
android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:935)
android.os.Handler.handleCallback (Handler.java:873)
android.os.Handler.dispatchMessage (Handler.java:99)
android.os.Looper.loop (Looper.java:193)
android.app.ActivityThread.main (ActivityThread.java:6669)
java.lang.reflect.Method.invoke
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

---

Internal Firebase Info

💥 DO NOT EDIT THIS SECTION 💥

Crash IDs: b4b64ee516fd3cc09bb472809f4686ce
Exception: Error while updating property 'zIndex' of a view managed by: RCTView

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[arielgreen]

https://www.upwork.com/jobs/~01bc72f85491adcfc9

[AwaisKhan128]

Hi there,
I found your job proposal and jumped out here. The crash has mentioned that "Error while updating property 'zIndex' of a view managed by: RCTView" which implies that all story evolves around zIndex.

I researched several issues that were caused in time back reflecting that there are mostly three possibilities that might ensure its existence.

1. ViewManager has no ZIndex property sounds like it would never scaleable in the z direction.
2. Property param type was supplied wrong while updating zIndex ( e.g required int but supplied string).
3. ViewManager was not initialized before updating its zIndex but caused crash.

Over 4 years of React Native development mobile application development. I can ensure its resolution soon.
Lets discuss if anything I got missed and something you would like to add.

I will be waiting for your response.
Thanks,

Regards,
Awais Khan

[mananjadhav]

Thanks for the interest @AwaisKhan128, please refer our contributing guidelines, how to write a proposal and how we work on the jobs here.

We would need the technical proposal crisp and solid enough to solve the issue.