AppleSettings : Unresolved reference

Hello

I am trying to use AppleSettings constructor, but it seems to me as Unresolved reference.

 val commonMain by getting {
           dependencies {
               implementation("com.russhwolf:multiplatform-settings:0.7.1")
           }
       }

I have added its dependencies like the code above and into module shared:iosMain I try to use the following:

val delegate: NSUserDefaults // ...
val settings: Settings = AppleSettings(delegate)

However the AppleSettings constructor is not available.

[russhwolf]

There’s different issues being conflated here and I want to differentiate what people are asking for better.

One issue is, the library builds but there’s red code in the IDE. This is probably from using a shared iOS source-set (often, from the ios() target builder) when the library doesn’t declare the HMPP gradle properties. I’ve been wary of adding that because I don’t want to break consumers who aren’t using those flags yet, and also I’ve had build issues in the past when enabling it. It’s probably worth re-examining at some point, but it’s been a lower priority for me because it doesn’t block your build and it likely only impacts one file where you’re initializing your iOS Settings instance.

Another issue is, the project doesn’t build at all. That’s what @afaucogney seems to be reporting… That’s a bigger issue that I’d like to understand better, but I’ve never seen it in action in any of my own projects, so I could use some help here with a full project that reproduces it.

@krottv your sample appears to be only a single module from a larger project and doesn’t build on its own, so it doesn’t help me. But I’m also not clear on which of those two buckets you fall into

@cmota brings up a further confounding factor in the new M1 macs. I haven’t used one myself yet so I don’t have a good sense of how it impacts this whole story. If multiplatform-swiftpackage gives you what you need, then that sounds great. I suspect doing an ad-hoc target declaration similar to the sample project would also work, but I’m not sure that’s a solution that scales great for large multimodule projects. In any event, I don’t think there’s anything that makes sense to add at the library level to help here. Packaging is a concern that should really be handled at the application level.

[russhwolf]

You should now be able to resolve AppleSettings in the IDE in shared iOS sourcesets in version 0.8