👋🏽 hello hello

Got burned by that too. Had to switch everything over to Cocoapods and in the process lost NSExceptionKt since that only works with SPM.

May be it is just me but, sometimes it all reads like an opportunity to manufacture code so that you can do all the maintenance work.... Which wouldn't exist otherwise at the beginning of newly written code

If you are writing a library I recommend trying to go as old as possible. Most supporting libraries can still go back to 21 but it is starting to shift to 23.

If you are writing an app use what works for you. According to apilevels.com targetting 26 can easily get you to 95%+ devices.

No such thing as a silver bullet, agreed

I keep hoping one day Compose can be compiled to native instead of dex and then apps can skip JVM completely. I'd love to see Android Native thrive.

Also the generated framework has to be a direct decedent of the podspec parent; i.e. if the generated podspec uses ../ to get to the framework Cocoapods will not load it correctly. 5/

Additionally all the dependencies from the various modules have to be added to the umbrella KMP module.

The dependencies can actually be skipped in Podfile as the development podspec will correctly list the dependencies. 4/

If you are doing that you MUST include the KMP framework using a podspec. If you don't you get a warning and mostly works but when you deal with a dependencies coming from different modules the final build seems to be random.

Didn't do an RCA when Kotlin slack said it isn't officially supported. 3/

Using Cocoapods is the easiest way to add an iOS dependency specially if you need to access the framework from Kotlin.

However, currently this means everytime the IDE does a Gradle sync it builds those frameworks. Anyone knows how to stop that it would be awesome. 2/

Thanks. Mine is blank dinner I don't regularly wear it to sleep