Gabriel Souza

All Voyager screen has to be serializable in a Bundle, this means that you need to all parameters of your Screen for Android to be or Java Serializable or Parcelable.

I will try to debug hit here soon. But based on that fact that Android works and iOS does not, it seems to be a Compose KMP issue on iOS.

@johnrengelman any update on this?

Hey, sorry the delay! Don't know if I understand your question properly, do you want to navigate to another Screen inside the BottomSheet or you want to navigate to Screen...

@Kashif-E HI, we will have a look on this soon (testing and trying on our samples), don't know if it will be for 1.0 that will be soon released. Btw...

I have baked your API without requiring to change any internal voyager APIs, could you try it out? If it works for you, we could provide this a result API...

Did it work for you @Kashif-E ? @osrl we are planning to create a documentation page with "community extension and third party libraries"

Can you share a reproducible code for this bug?

@ghasemdev there is no currently built-in way of handling deeplink uris in voyager. The issue #387 has a example how you can handle this your self with `replaceAll` for example....

Yes! It should, same navigator. Your LocalComposition does not have "default Navigator", it throws a Exception if it is not provided, what could be happening is that your is recomposing...