-
Notifications
You must be signed in to change notification settings - Fork 43
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
kotlin 2, ksp 1 and ktorfit clashing in multimodule project #634
Comments
I arrived to the same problem with your example multiplatform project. All that was needed is create basic module with the Person data class and connect a dependency to the module from shared module. |
Hi, I just updated the example project to multi module and i don't have any issues https://github.com/Foso/Ktorfit/tree/master/example/MultiplatformExample |
This is fascinating problem. If I take your example project, I can build it. However, if I remove all lines regarding ios in build.grade.kts, I will arrive to the bug. **IMPORTANT EDIT: **You must do build>clean after/before syncing for gradle changes. Otherwise, the problem won't show up, because it takes a cached successful build or something. |
js target is also making it work. I honestly guess it is a KSP problem but maybe you could find out exactly what and work your way around it? |
okay, thank you for trying it. Maybe i find a solution |
Ktorfit version
2.0.1
What happened and how can we reproduce this issue?
Upgrading from kotlin 1.9.24 to kotlin 2.0.x and ktorfit 2.0.1 in my multimodule project has been giving error messages while trying to compile.
I have ktorfit interface inside module A, which sees on module B where class TeamResponse is located.
And it will always give this error:
If I comment out the TeamResponse, TeamRequest will be the next error.
If I turn on ksp2, then the nullability issue of ksp2 is first to be served.
What did you expect to happen?
no error
Is there anything else we need to know about?
No response
The text was updated successfully, but these errors were encountered: