David Otasek
11/21/2025, 10:01 PMThe slice reducer for key "localizationSlice" returned undefined during initialization. is what I can see in the browser console. I can get rid of that exception with some changes, but that leads to other runtime errors and I can't tell if it's actually an improvement.
If anyone has any ideas on the path I should take, or suggestions on more appropriate places to ask for help, please let me know.Wayne
11/21/2025, 10:42 PMPhodal
11/22/2025, 5:17 AMSajid Ali
11/22/2025, 8:14 AMplugins {
alias(libs.plugins.android.kotlin.multiplatform.library)
alias(libs.plugins.kotlinMultiplatform)
alias(libs.plugins.kotlinCocoapods)
}
kotlin {
jvmToolchain(17)
androidLibrary {
namespace = "dev.sajidali.onplayer.vlc"
compileSdk = 35
minSdk = 21
}
jvm("desktop")
val xcfName = "VlcKit"
listOf(
iosSimulatorArm64(),
iosArm64(),
iosX64(),
tvosX64(),
tvosArm64(),
tvosSimulatorArm64(),
// macosArm64(),
// macosX64()
).forEach {
it.binaries.framework {
baseName = xcfName
// linkerOpts.add("-framework")
// linkerOpts.add("VLCKit")
isStatic = false
}
}
cocoapods {
summary = "Shared LibVLC Implementaion"
homepage = ""
version = "1.0"
ios.deploymentTarget = "18.0"
tvos.deploymentTarget = "18.0"
// osx.deploymentTarget = "15.0"
framework {
isStatic = false
baseName = xcfName
}
pod("VLCKit") {
version = "4.0.0a16"
extraOpts += listOf("-compiler-option", "-fmodules")
}
}
sourceSets {
commonMain {
dependencies {
api(project(":oneplayer")) // Consider making this api if you want to export it too
implementation(libs.kermit)
}
}
androidMain {
dependencies {
implementation(libs.core.ktx)
implementation(libs.appcompat)
implementation(libs.constraintlayout)
// Add LibVLC dependency
// implementation(libs.libvlc.all)
}
}
appleMain {
dependencies {
// Any iOS-specific dependencies
}
}
}
}
This is my gradle config. What am I doing wrong?electrolobzik
11/22/2025, 9:01 PMRANJAN
11/23/2025, 8:39 PMcomposeApp and shared modules. and shared would be containing logic till domain layer.
But after migrating my application to domain and started composeApp module with UI and viewmodel I realised in composeApp don't have way for viewmodel to be initialised via koin.(If have way then please let me know)
But now when we create new project using KMP plugin it do not provide shared module instead official documentation suggest to put shared logics in same module too.
My question: is KMP really stable. without knowing it changed a lot in 4-5 months for me. Can it be trusted.Colton Idle
11/24/2025, 2:01 AMBhadra Vaghela
11/24/2025, 5:35 AMFrançois-Xavier Beuvry
11/24/2025, 9:02 AMInt16, Int32, Int64, etc.).
• However, the iOS developers in my company are primarily using Swift, and they strongly prefer to use the standard Swift Int (which, on modern 64-bit architectures, is effectively a 64-bit integer, Int64).
They are reluctant to deal with the specific Objective-C-derived integer types (Int32, Int64, etc.) as it breaks Swift idiomatic usage and requires constant casting.
I initially suggested exposing the numbers as NSNumber, but this was also rejected for similar reasons (non-idiomatic Swift).
My question is: Is there an established, idiomatic way (a KMP feature, a specific wrapper, a build setting, or a best practice) to make KMP expose Kotlin integer types (especially Int and Long) in a way that maps directly to the standard Swift Int type, or at least something closer to it than the current Obj-C derived types?
I suspect this question has come up before, but I haven't been able to find a clear solution or discussion thread. Any advice or pointer would be greatly appreciated!
Thanks!Gustavo E Bonilla
11/24/2025, 10:52 AMAlexandru Caraus
11/24/2025, 11:05 AMSmoothie
11/24/2025, 3:11 PMDumitru Preguza
11/24/2025, 3:46 PMliverm0r
11/24/2025, 10:15 PMCompose Multiplatform for Desktop IDE support but it doesn't allow to click on a view and move cursor into the code.Karen Frangulyan
11/25/2025, 3:29 AMplus and minus operators for PaddingValues in 1.10.0-alpha05 , however, CMP 1.10.0-beta02 (which is based on jetpack compose of the same version) doesn’t seem to have those operators.Simileoluwa Aluko
11/25/2025, 6:44 AMymaskin
11/25/2025, 2:49 PMmarkturnip
11/27/2025, 9:30 AMDamjan Miloshevski
11/27/2025, 11:36 AMpablisco
11/27/2025, 12:40 PMBhadra Vaghela
11/27/2025, 1:36 PMBrill
11/27/2025, 2:46 PMStylianos Gakis
11/27/2025, 3:23 PMkotlinx.datetime.toJavaLocalDate which comes from inside kotlinx.datetime, which is defined in the jvm target.
If I have the android and the jvm source sets separately, each one of them can import this function and just use it, no problem. However if I make a new sourceset like:
applyDefaultHierarchyTemplate()
val jvmAndAndroidMain by creating {
dependsOn(commonMain.get())
}
jvmMain.get().dependsOn(jvmAndAndroidMain)
androidMain.get().dependsOn(jvmAndAndroidMain)
it is not resolved since as I understand it can't figure out that both those targets are supposed to be able to call the jvm target of the kotlinx.datetime library.
Perhaps there might be a way to make this happen by not using the applyDefaultHierarchyTemplate and doing something more custom?Mikolaj
11/27/2025, 6:06 PMKaren Frangulyan
11/27/2025, 8:41 PMJack Boyce
11/27/2025, 11:21 PMDaria Voronina [JB]
11/28/2025, 8:38 AMMichal Klimczak
11/28/2025, 9:00 PMw: Xcode Version Too High for Kotlin Gradle Plugin despite kotlin 2.2.20 🧵Jeremie D
11/29/2025, 12:08 AMMichal Klimczak
11/29/2025, 9:57 AM