After upgrading from Meerkat to Narwhal, we've not...
# compose-iosa
aidanvii
08/28/2025, 1:48 PMAfter upgrading from Meerkat to Narwhal, we've noticed a change in how iOS run configurations are done. We are working in a monorepo with 3 apps, 2 of which are compose multiplatform. Even after setting the working directory to the app we actually want to run, it will always run the other. Obfuscated the names in the screenshot, but for example it would run app-1 instead (the working directory doesn't seem to have any effect here):
aidanvii
08/28/2025, 1:52 PMin Meerkat it looked like this and worked just fine, we had a run configuration for each app
aidanvii
08/29/2025, 6:30 AMany help on this would be greatly appreciated, the new Narwhal way of doing things just doesn't seem up to the task here
c
Clément Vandendaelen
09/10/2025, 9:06 AMhttps://youtrack.jetbrains.com/projects/KMT/issues/KMT-1298/Support-multiple-iosApp-target-in-the-same-project
Created a ticket month ago, still no solution
Clément Vandendaelen
09/10/2025, 9:08 AMAh but you responded to the ticket ahah
a
aidanvii
09/10/2025, 9:08 AMYep I saw and commented. It's really not great, I'm still using Meerkat with an older KMP plugin. This is not suitable for large non standard projects, aka monorepos 🙈
aidanvii
09/10/2025, 9:09 AMOkay for small projects, I guess...
c
Clément Vandendaelen
09/10/2025, 9:09 AMI agree, what I ended-up doing was to concentrate all the project under the same iosApp and redo the "piping" so that the path are connected to the right project at build time. It works for me, but I think it might be an issue in some use-cases
a
aidanvii
09/10/2025, 9:11 AM@Shahzar Ahmed can you try this? I think you did right?
2 Views