-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
TabNavigator not Allowing Theme change #480
Comments
I downgrade my voyager version and problem fixed:
|
I'll downgrade and try it out |
@shageldi-dev Thank you so much! It finally worked after downgrading my voyager version. |
@RaheemJnr did this work for you in iOS as well? Downgrading version works on Android, but doesn't work on iOS. I have the below versions with another fix to make voyager work with kotlin 2.1.0 as suggested in iOS Doesn't build with kotlin 2.1.0 and voyager 1.1.0-beta03 or lower I have also tried upgrading the compose version to 1.8.0-alpha06, still the same result.
|
I haven't tried it out on IOS yet
…On Sat, 4 Jan 2025, 12:40 am Jayesh Nair, ***@***.***> wrote:
@RaheemJnr <https://github.com/RaheemJnr> did this work for you in iOS as
well? Downgrading version works on Android, but doesn't work on iOS.
I have the below versions with another fix to make voyager work with
kotlin 2.1.0 as suggested in iOS Doesn't build with kotlin 2.1.0 and
voyager 1.1.0-beta03 or lower
<#515 (comment)>
I have also tried upgrading the compose version to 1.8.0-alpha06
<https://issuetracker.google.com/u/1/issues/374263387>, still the same
result.
compose = "1.7.6"
compose-plugin = "1.7.3"
kotlin = "2.1.0"
voyager = "1.1.0-alpha04"
—
Reply to this email directly, view it on GitHub
<#480 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APZFSRMH5LKO4OKRDBVN5UD2I4NVJAVCNFSM6AAAAABNN6OG6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRZHEZTOMBTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I have been trying to implement theme change in 2 of my app but it being a hassle after extensive debug period I figured the common thing between them is that both app uses Voyager because they are a multiplatform app, I figured after a successful theme change and the state changes Voyager doesn't recompose to reflect the current (newly) selected theme until I close the app and open again, so my question now is had anyone faced similar issue and what advice will you give me on how to overcome it or probably a code example.
note: After lot of time spent debugging i found out it's the ### TabNavigator causing it. in two separate example where i use and didn't use the tab navigator the issue persist in the former and not the latter.
` @composable
override fun Content() {
val vm: ProfileViewmodel = koinScreenModel()
val modifier = Modifier
val isDark = remember { mutableStateOf(false) }
the second example
`@Composable
override fun Content() {
val vm: ProfileViewmodel = koinScreenModel()
val modifier = Modifier
val isDark = remember { mutableStateOf(false) }
The text was updated successfully, but these errors were encountered: