technically 4, but that's due to a dependency of the MPP project

and how you handle versioning of your project

I've linked my shared and Android project (repo1) to my iOS one (repo 2)

and i'm trying to find out the best way to make is easier for the other devs when we start making changes in the shared library (script etc). Do you have any ideas around this

IMO the easiest is using the cocoapods plugin with a self hosted repo for your podspecs

you can also add the project as a submodule, and point to the podspec file in the repo root

the latter takes versioning out of the equation, but git submodules can be a pain sometimes

i ran into a very strange issue w/ cocoapods, due to a cinterop dependency, and ended up having to fallback to embedding a fat framework

So to conclude, each dev on your side has to manually pull the code across all your repositories?

but in this case. there's no reason any dev will need to work with the source.