At the moment the CI is done with the help of a shell build script. This appeared to be somewhat cumbersome in the past so here's the PR for switching to fastlane for the build and test.
Instead we now use the direct fastlane scan integration of CircleCI because it has the least boilerplate while still covering all the functionality we need.
Also we changed the workflow a bit so the tests of the example projects now run in parallel. This saves us a lot of time but has one drawback that when you add a new example project you would also need to add a separate job in CircleCI for it. But the process should be quite straight forward and not happen very often. (As we currently have 2 example projects)
At the moment the CI is done with the help of a shell build script. This appeared to be somewhat cumbersome in the past so here's the PR for switching to fastlane for the build and test.
Instead we now use the direct fastlane scan integration of CircleCI because it has the least boilerplate while still covering all the functionality we need.
Also we changed the workflow a bit so the tests of the example projects now run in parallel. This saves us a lot of time but has one drawback that when you add a new example project you would also need to add a separate job in CircleCI for it. But the process should be quite straight forward and not happen very often. (As we currently have 2 example projects)