-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOS Build failed with kotlin 2.1.0 because of voyager #522
Comments
the same issue was already opened in here. I didin't notice |
Did you find a way how to fix it? |
Unfortunately, I am switching to Decompose, which is being really helpful. Voyager is a great library, but seems it is not ready for production in the earlier releases. |
But voyager works on desktop, decompose doesn't, as I know. |
It does work in Desktop with JVM. Not sure if it works in WASM, but that is in alpha (I guess). https://arkivanov.github.io/Decompose/faq/ |
On Desktop it only works with mac os, but I need windows support. |
Are you sure? Desktop apps built with Compose run on the JVM, so they should work on Windows, macOS, or even Linux without any issues. Maybe there’s just a setup problem on Windows? EDIT: Supported multiplatform targets: Android, JVM/Desktop, Native/iOS, Native/macOS, JS/Canvas and JS/Wasm. |
I get this error when trying to use Firebase with Voyar koin in common, try to remove voyar koin and just use insert-koin.io |
same issue |
Same here 🥲 |
I've switched to decompose, it is much solid library than voyager for now. |
I found a solution. I had two projects, both using Kotlin version 2.1.0. One of them was compiling on iOS, while the other was not. After searching for differences, I noticed that the only difference was that the compiling project had implemented the Rinku library (version 1.3.2) from this GitHub repository. I added this library to the non-compiling project, and now it compiles on iOS as well. It’s a ridiculous solution, but it works! |
|
Voyager Version -> 1.1.0-beta03
The text was updated successfully, but these errors were encountered: