Closed
Bug 1826457
Opened 3 years ago
Closed 3 years ago
[Tabs tray to Compose] Update Compose version to 1.4.0 to fix crash
Categories
(Firefox for Android :: Tabs, defect, P2)
Tracking
()
RESOLVED
FIXED
114 Branch
People
(Reporter: 007, Assigned: 007)
References
Details
(Whiteboard: [fxdroid])
Crash Data
Attachments
(2 files)
There is a crash when rotating the device when the composified Tabs Tray is open while the tabs display as a grid.
According to this google issue, upgrading to version 1.4.0 (or newer) of androidx.compose.foundation:foundation fixes this.
|
||
Updated•3 years ago
|
|
Assignee | |
Updated•3 years ago
|
Assignee: nobody → nbond
Status: NEW → ASSIGNED
|
||
Comment 1•3 years ago
|
||
|
|
Assignee | |
Updated•3 years ago
|
Summary: [Tabs tray to Compose] Update Compose foundation library to 1.4.0 to fix crash → [Tabs tray to Compose] Update Compose version to 1.4.0 to fix crash
|
|
||
Comment 2•3 years ago
|
||
Authored by https://github.com/MozillaNoah
https://github.com/mozilla-mobile/firefox-android/commit/4677cd8f3f3fb90c91ccc928113bc53b2952693e
[main] Bug 1826457 - Update Compose version to 1.4.2 and Lifecycle version to 2.6.1
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox114:
--- → fixed
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
|
|
Assignee | |
Updated•3 years ago
|
Flags: qe-verify+
|
||
Comment 4•3 years ago
|
||
Setting status-firefox113=wontfix because I assume that updating from Compose 1.3.1 to 1.4.2 is too big a change to uplift.
I think bug 1805351, whose crash volume is very low, is a duplicate of this bug.
status-firefox112:
--- → wontfix
status-firefox113:
--- → wontfix
|
||
Comment 5•3 years ago
|
||
Copying crash signatures from duplicate bugs.
Crash Signature: [@ java.util.NoSuchElementException: at kotlin.collections.CollectionsKt___CollectionsKt.first(_Collections.kt:214)]
[@ java.util.NoSuchElementException: at kotlin.collections.CollectionsKt___CollectionsKt.first(_Collections.kt:5)]
[@ java.util.NoSuchElem…
You need to log in
before you can comment on or make changes to this bug.
Description
•