Should I report bugs in the following situation I released a

Question

Should I report bugs in the following situation I released an app and I see Crashlytics crash reports with a stack trace in Compose but no frames from my code I can t reproduce the crash My guess is there are some bugs in Compose causing it but is a stack trace and message not enough for a report Example in thread

robnik · Answer

Fatal Exception java lang IllegalStateException Compose assumes that all pointer ids in MotionEvents are first provided alongside ACTION DOWN or ACTION POINTER DOWN This appears not to have been the case

robnik · Answer

```androidx compose ui input pointer MotionEventAdapter createPointerInputEventData MotionEventAdapter java 126 androidx compose ui input pointer MotionEventAdapter convertToPointerInputEvent$ui release MotionEventAdapter java 86 androidx compose ui platform AndroidComposeView dispatchTouchEvent AndroidComposeView java 858 arrow right android view ViewGroup dispatchTransformedTouchEvent ViewGroup java 3863 android view ViewGroup dispatchTouchEvent ViewGroup java 3492 android view ViewGroup dispatchTransformedTouchEvent ViewGroup java 3863 android view ViewGroup dispatchTouchEvent ViewGroup java 3492 android view ViewGroup dispatchTransformedTouchEvent ViewGroup java 3863 android view ViewGroup dispatchTouchEvent ViewGroup java 3492 ```

robnik · Answer

Fatal Exception java lang IllegalArgumentException Can t represent a size of 2147483520 in Constraints

robnik · Answer

```androidx compose ui node MeasureAndLayoutDelegate access$getPostponedMeasureRequests$p MeasureAndLayoutDelegate java 38 androidx compose ui node MeasureAndLayoutDelegate measureAndLayout MeasureAndLayoutDelegate java 207 androidx compose ui platform AndroidComposeView measureAndLayout AndroidComposeView java 510 androidx compose ui platform AndroidComposeView dispatchDraw AndroidComposeView java 666 arrow right android view View draw View java 22353 android view View updateDisplayListIfDirty View java 21226 ```

Stylianos Gakis · Answer

Could it be this Same constraints number in the exception

Stylianos Gakis · Answer

I meant to link this too <https github com google accompanist issues 847> omg man facepalming

robnik · Answer

Could be I m using the HorizontalPager and Accompanist latest stable 0 20 2

Stylianos Gakis · Answer

We are avoiding this by using 0 18 0 for now But if you re feeling adventurous use 0 21 4 beta instead as Andrey Kulikov suggests it might be fixed there from <https github com google accompanist pull 844|this> PR most likely

robnik · Answer

Thanks I ll try the beta or wait for that version to be stable