FragmentScenario should use setMaxLifecycle() for moveToState() [156527405]

Fixed

Bug

Status Update

No update yet.

Description

il...@google.com

created issue #1

May 13, 2020 08:50PM

Component used: Fragment Version used: 1.3.0-alpha04

FragmentScenario's moveToState() calls through to ActivityScenario's moveToState(), which means it is not possible to move to the STARTED case prior to API 23 and strongly couples the Fragment to the underlying Activity's state.

It would be nice if FragmentScenario could be entirely decoupled from changes in the Activity's state by using setMaxLifecycle() for its implementation of moveToState().

Comments

ap...@google.com <ap...@google.com> #2Jun 8, 2020 10:19PM

Thanks for trying out Room KMP! This looks like an issue with Android 9+ and armv7 and the way we compile sqlite3.c, specifically linking to the atomic library in C. We'll try to get this fix as soon as possible.

il...@google.com <il...@google.com> #3Jun 17, 2020 02:27AM

Marked as fixed.

Very related: https://sqlite.org/forum/info/aa703e86823efca3, as suspected seems like a linking issue.

Issue 156527405

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Jun 8, 2020 10:19PM

il...@google.com <il...@google.com> #3Jun 17, 2020 02:27AM

Add comment

Issue metadata