setMaxLifecycle() should support Lifecycle.State.INITIALIZING [159662173]

Fixed

Feature Request

Status Update

No update yet.

Description

il...@google.com

created issue #1

Jun 23, 2020 12:25AM

Component used: Fragment Version used: 1.3.0-alpha06

Right now, setMaxLifecycle() only supports Lifecycle.State.CREATED or higher. It would be nice if setMaxLifecycle() could also support Lifecycle.State.INITIALIZING only for Fragments that have never moved above CREATED - i.e., only something that could be set alongside the Fragment being added to the FragmentManager.

This would allow developers and libraries built on top of fragments to keep fragments only at the attached state without going through onCreate().

Comments

ap...@google.com <ap...@google.com> #2Aug 14, 2020 01:10AM

Seems to be a DNS problem with systems that have 'obtain DNS server address automatically'. Changed my system to a manual setting and the browser etc now work. SDK 2.2 didn't seem to mind the auto setting though.

jb...@google.com <jb...@google.com> #3Aug 25, 2020 07:19PM

Marked as fixed.

Could you please describe how/where you changed your system to a manual setting?

Issue 159662173

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Aug 14, 2020 01:10AM

jb...@google.com <jb...@google.com> #3Aug 25, 2020 07:19PM

Add comment

Issue metadata