r

    ribesg

    3 years ago
    I’ve been publishing both
    -android
    and
    -android-debug
    variants of my kmp libs until now because I never managed to force a kmp library B to use the kmp library A’s
    -android
    release in its
    -android-debug
    build. Now I’m making another lib and I feel like I should stop publishing debug builds. Anyone encounter this problem and worked around it?
    russhwolf

    russhwolf

    3 years ago
    For the sake of removing friction on the consumer side I typically just do
    publishAllLibraryVariants()
    .
    r

    ribesg

    3 years ago
    I mean, it doesn’t cost a lot, but I find it disturbing that a debug build can’t just fall back to a release version of a dependency 😕
    russhwolf

    russhwolf

    3 years ago
    Yeah, I find it confusing as well. Maybe worth filing a ticket on Youtrack? I think there was some technical reason why Jetbrains doesn't have that default fallback but not sure what it is.