Whats the correct way for lazy Router?

Hi, I have a layer in the UI that is only used rarely (pin code feature). I implemented it via new controller container above the "default" controller container.

Now I'd like to lazily initialize the Router, however it takes the savedInstanceState, and I presume its designed to be called in onCreate, not lazily anywhere for example in onResume

Has anyone encountered this? Is it worth avoiding at all? I'd also like to use ViewStub for best optimization however, its pointless if Router needs to be created in onCreate where savedState is accessible

Start by tracing how Router receives savedInstanceState during onCreate and compare that with the proposed lazy initialization in onResume. Examine whether ViewStub can defer the rarely used pin-code layer without violating the Router lifecycle contract; done means an agreed, documented initialization path.

Written by the indexing model from the issue text.