-
-
Notifications
You must be signed in to change notification settings - Fork 85
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: Error when updating to 3.1.0 (PageScrollAnimation) #727
Comments
What compose version are you using? Could you please try using Essenty 2.1.0 and Compose 1.6.10? |
@arkivanov yep I used Essenty 2.1.0 (just tried with 2.0.0 to ensure which version bump was related to the issue). I am using 1.6.11:
|
Would it be possible to provide a reproducer? |
This looks like a compiler bug. |
I have the app here: I am assuming the minimal reproducible scenario would be a Pager with this animation, but haven't set that up to validate. But yes, it does seem like a compiler bug. |
That issue looks related, thanks! I would check a reproducer and report a bug to Compose, if you could provide a link to a runnable project with the failing changes. |
I pushed the bump here: |
Thanks! I managed to create a minimal reproducer. Reported here: JetBrains/compose-multiplatform#4809 (comment) Let's keep this bug open for visibility purposes. |
The suggested workaround works. Add the following lines to
|
Great, thank you, the workaround works for me too. But yes let's keep it open until the related CMP issue is resolved. |
Looks like this issue should be fixed in Kotlin |
I have a KMP project (Kotlin 2.0.0) with an iOS target.
Updating from 3.0.0 to 3.1.0 (Essenty at 2.0.0) works fine on Android and Desktop, but on iOS I get the following build failure:
This is a composable in my app which is a page in a pager.
and is specifically related to this line:
scrollAnimation = PagesScrollAnimation.Default,
commenting out this line solves the issue.
The root stacktrace below:
Please let me know if I can provide any further info.
The text was updated successfully, but these errors were encountered: