Default `StateStore` should work across config change about redwood HOT 3 OPEN

If we pass it through the non-config instance of activity then in memory would be sufficient for at least config changes, but not process death from things like memory pressure.

from redwood.

I'm really hesitant about a file-based (or any persistent) store because the structure is guaranteed to not be persisted across app updates. So seems like we need to write the file name into the regular saved instance state and only restore its values when the path remains available. Otherwise we get a new path and clean up the old ones.

from redwood.

If I may share my opinion, I believe that the main issue lies in the way we initialize the MemoryStateStore, rather than the MemoryStateStore itself. Therefore, I suggest implementing an approach that relocates the TreehouseAppFactory, or at the very least, the MemoryStateStore, outside of any risky component. If I were using Redwood in an application, I would initialize the TreehouseAppFactory within the Application/ViewModel class and then expose the instance to the Activity with Dependency Injection or a similar technique.

from redwood.