wordpress-mobile / wordpress-mobile/WordPress-Android
Crash detected by Google Play pre-launch report
Open
Nobody has claimed this yet.
[Type] Crash
Tooling
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Android accessibility and text-layout path implicated by the Google Play pre-launch stack trace, then investigate how the reported offset and line limit arise on the tested device and app build. Done means identifying a reproducible cause and validating a fix against the pre-launch crash, with regression coverage if the project provides a suitable test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- accessibility, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100