Why do the <KMM sample repos> manually create the shared module’s iOS targets for each architecture,...

# multiplatform

[Casey Brooks]

Why do the KMM sample repos manually create the shared module’s iOS targets for each architecture, rather than using the common ios() target?

[Konstantin Tskhovrebov]

because ios() - it is just function which registers iosX64 and iosArm64 targets and setups hierarchy between them.

but usually we need iosSimulatorArm64 target too (for Mac M1 development).

moreover, explicit targets declaration is more explicit 😂

[Casey Brooks]

Will iosSimulatorArm64 be added to the ios() shortcut? I have a library I published using the ios() shortcut, but couldn’t seem to get the ios-specific declarations from that repo to be accessible unless I used ios() in the KMM app, too

[Konstantin Tskhovrebov]

we've thought about it but it breaks backward compatibility and a build reproducibility on m1/non-m1

so, it's better to use explicit targets declaration

[Casey Brooks]

Good to know, thanks!