I started a KMM project in fall and now it would b...

# multiplatform

[Matti MK]

I started a KMM project in fall and now it would be time for another one. In my previous project I did not use the new MM, nor have to worry about M1 issues. However, going into the new project I would like to support M1 and perhaps also use the new MM.

With those constraints in mind, are there currently any known pitfalls when it comes to M1 and KMM?

[Marc Reichelt]

By ‘support M1’, do you mean writing apps natively running on an M1 Mac - or do you mean compiling a KMM project on an M1?
If it’s the latter - we’re having no issues running our KMM iOS builds on an M1 so far.

[Matti MK]

Ah yes, compiling a multiplatform project with M1 is what I mean, targets being iOS and Android

[Matti MK]

I seem to remember seeing M1 mentioned here in the channel, so I was wondering if there’s any known pitfalls that could be avoided

[Grégory Lureau]

I need a trick to force the nodejs version when targeting Js (not sure if still required tho) but nothing special for Android/iOS iirc.

[Rick Clephas]

@Grégory Lureau that trick is no longer needed in Kotlin 1.6.20: https://youtrack.jetbrains.com/issue/KT-49109/KJS-Gradle:-Configuration-failed:-Could-not-find-node-14.17.0-da

[Marc Reichelt]

Ok, yeah - no known pitfalls with M1 on our side :)