no-arg and settings persistence

Hello!

I’m facing the next issue: I’ve tested with no-arg module and everything looks good but… every time I close the app (Android), the preferences are being deleted, is that behaviour expected??

For example, i’m testing something like this:

val settings = Settings()
println("Setting: " + settings.getBoolean("TEST"))
settings.putBoolean(("TEST", true)
println("Setting: " + settings.getBoolean("TEST"))

Every time I close the app, I get this output:

Setting: false
Setting: true

Lib version: 0.6 Kotlin version: 1.3.72

Maybe I’m missing something? Thanks for the lib!

[dzolnai]

I finally found the culprit. The issue was that I was using a build type with a non-default name (prelease). That’s why it did not pair it with neither the debug version or the android release version of the library. I guess it matched with the jvm version because that one does not have any subtypes, so it matches anything, and android is a subtype of jvm… Anyways, the solution was to add release as a matching fallback for my prerelease build type:

buildTypes {
        ...
        prerelease {
            matchingFallbacks = ["release"]
            ...
        }
    }

I had to do this at all places where I had the prerelease build type defined, in common and also the android app. I still don’t know why this came up just now, I have at least 10 other Kotlin MP libraries in my app. Perhaps because this library publishes separate debug and release variants?

[russhwolf]

I’m pretty sure there’s nothing left to do here, so I’m closing this. Feel free to reopen, or start a discussion, if anyone is still having trouble.