Hey everyone 👋 We have the following “standard” use case: Android and shared modules in one repo and iOS in a different repo. Q: Is it possible to publish the artefacts and the

Package.swift

file in a different repository other than where the Android code and the shared code lives? Something like:

kmmbridge {
    spm(githubUrl = "<https://api.github.com/repos/company/company-ios-all-shared>")
}

I am asking cause I fear that if we use the Android repository for publishing iOS artefacts could lead to increased build time if the Android repo contains lots of files (e.g. images from snapshot tests,…)

That was a use case Russell had early on. It's less common and more complex, so it was pulled before we released the initial version. I'll have to think through how to best approach it. Short answer, that is certainly possible, but would need some plumbing.

So the suggestion for such teams is to extract shared code into a third repo or bring iOS into monorepo right?

I just had a wild idea. I don’t know if I want to say it out loud just yet.

So the suggestion for such teams is to extract shared code into a third repo or bring iOS into monorepo right?

Yes, we want to extract the shared code into a third repo. By shared code in this context we mean the binaries that are created, but not the code itself

then again, that might not work. If Xcode tries to get sub modules, it’ll be the same problem.

So you are saying this won’t work anyway? When you talk about sub modules, do you mean the functionality in Github? Just asking as I don’t have any experience with that. All in all, do you think it is a lot of overhead if we just publish the binaries in the repo where the Android code and the shared code lives (Normal KMMBrisgde approach)? One of our iOS devs just raised the concern that it could lead to increased build times when the whole repo needs to be loaded on iOS. Which I understand as this is unnecessary because as far as I know SPM just needs to know the location of

Package.swift

right? We were already using KMP in a repo that was outside of the Android one. We did exactly that • The

Package.swift

file was published to it’s own repo while the

binaryTarget

url was pointing to the released zip file that lived in the shared repo

> So the suggestion for such teams is to extract shared code into a third repo or bring iOS into monorepo right?

Yes, we want to extract the shared code into a third repo. By shared code in this context we mean the binaries that are created, but not the code itself

To clarify, you are talking about different things. Pulling shared code into a 3rd repo and using a 3rd repo only to manage SPM dependencies. As a general recommendation, it really depends. If Android is where the main dev really happens, and iOS generally follows after, I wouldn't pull the shared code into a 3rd repo. It will likely slow down dev. If the team is larger and you'd pull an SDK out anyway, then it makes more sense. Also, if you are just trying out KMP or for whatever reason start with a 3rd repo, that's OK too.

Alright, was not sure if you mean the Git feature. Our main development for Android and shared happens in one Repo. iOS is in a different repo. We don’t want to pull the shared code into a 3rd repository as it makes Android development easier if we keep it in the same repo. My question was more like about publishing the binaries into a 3rd repo. As this is not possible with KMMBridge right now, we need to stitch this solution if using KMMBridge. Thanks for the fast replies guys. You are doing a great job there 👍

Interestingly, there was a discussion kinda on the same topic (sharing the SPM package somewhere else) over here https://x.com/GakisStylianos/status/1722965584080429537 today

No, I get what you're saying. It is possible to just publish to a 3rd repo, but that isn't supported out of the box right now, certainly. What I was saying is maybe it could be supported with the following... (it'll be a minute. Doing diagrams)

Haha, alright waiting for it….

This is the setup where Android, the shared Kotlin module, and SPM publishing would all live. Simple, but it'll be a mess for a number of reasons mentioned above

So KMMBridge doe not have a good story regarding doing this https://kotlinlang.slack.com/archives/CTJB58X7X/p1699630743292279?thread_ts=1699464128.748599&cid=CTJB58X7X scenario right?

Alright, got it. Indeed those small diagrams make it so much easier to understand 💪 . We will give it a try and let you know what worked for us. Before we have to solve some different problems as KMMBridge is not running on CI for us on the first place. I posted an issue on the KMMBridge GHA plugin page. I think I will open another discussion in this slack channel if no one can help on Github for the next days

I'll be getting back to KMMBridge updates over the next few days. This week got a little busy (had a baby Monday 🙂 )

Congrats on the baby! 🥳🥳