AkesiSeli
commented
6 days ago It turned out, since the URL is opened in another application, that the issue is related to state restoration after process death. I hope common ViewModels will allow to solve the issue using SavedStateHandles just like in plain native code.
However, they are compatible with Voyager only starting from 1.1.0-beta01 so I should either:
- wait Voyager 1.1.0 to become stable or switch to the beta version of Voyager;
- switch to another navigation library, e.g. standard androidx navigation compose which in alpha supports KMP.
After opening an external URL in the browser, the current timelines resets back to its top position and the original scroll position is lost.
Original report here.