Crash detected by Google Play pre-launch report

[guarani]

This error is flagged by Google Play's Pre-launch report overview:

java.lang.IndexOutOfBoundsException: offset(17) should be less than line limit(16)

with this stack trace:

Exception Process: com.android.vending, PID: 4221
java.lang.IndexOutOfBoundsException: offset(17) should be less than line limit(16)
  at android.text.TextLine.measure (TextLine.java:353)
  at android.text.Layout.getHorizontal (Layout.java:1225)
  at android.text.Layout.getHorizontal (Layout.java:1202)
  at android.text.Layout.getPrimaryHorizontal (Layout.java:1172)
  at android.text.Layout.getPrimaryHorizontal (Layout.java:1161)
  at fbe.d (PG:1)
  at fbe.a (PG:38)
  at fbv.e (PG:1)
  at fap.l (PG:11)
  at epl.t (PG:30)
  at eor.addExtraDataToAccessibilityNodeInfo (PG:3)
  at android.view.AccessibilityInteractionController$AccessibilityNodePrefetcher.prefetchAccessibilityNodeInfos (AccessibilityInteractionController.java:1040)
  at android.view.AccessibilityInteractionController.findAccessibilityNodeInfoByAccessibilityIdUiThread (AccessibilityInteractionController.java:341)
  at android.view.AccessibilityInteractionController.access$400 (AccessibilityInteractionController.java:75)
  at android.view.AccessibilityInteractionController$PrivateHandler.handleMessage (AccessibilityInteractionController.java:1396)
  at android.os.Handler.dispatchMessage (Handler.java:107)
  at android.os.Looper.loop (Looper.java:237)
  at android.app.ActivityThread.main (ActivityThread.java:8016)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1076)

Tested on samsung SM-G981U1, Android 10, WPAndroid 1348.aab (according to report

[mbalajee]

We see the same error.

There's also this warning,

"Double splash screen
Users launching your app on Android 12 or higher are seeing 2 splash screens. To fix, update your app to use the SplashScreen API." but we don't see double splash screens.

Are these false positives ?

[irfano]

@mbalajee, thanks for sharing your idea. I don't think it's related to SplashScreen API.
There is an issue with compose layout about this crash. It was fixed with androidx.compose.ui:ui-text:1.6.0-alpha01, but we currently use 1.4.3. Since the new version is still alpha01, I would suggest waiting for the stable version and accepting this rare crash.

[ravishanker]

We're now at Compose BOM v1.5.0, and v1.6.0 is still at alpha03

[guarani]

Since it looks like we need to wait longer to address this, I've left this open and added a label. Feel free to adjust as necessary.