unity-actions VS react-native-code-push

> https://game.ci

I don't recommend it.

Game CI has been in development for a long time. It only really supports GitHub Actions. It can't correctly build il2cpp Unity projects. The licenses needed to run it are more expensive than Unity Build Automation / Unity Cloud Build. If you want to automate Unity builds and you don't want to learn the Windows Containers ecosystem, Jenkins and/or Tekton, you should use Unity's service.

CI/CD is a bad choice for most developers, on most platforms, for most clients. That said, it makes sense to do for your backends.

> or (as has happened to us with different game web service/API/middleware providers) they may choose to abruptly deprecate the service upon which you built.

Which service was that? GameSparks? That sucks.

> with inappropriate cloud dev tooling

Well everyone takes their own journey to discover how shitty Lambda, Cognito, CloudFormation and related are.

> with basically any datastore other than Redis you will run in to issues matchmaking

Matchmakers do not have to be complicated.

I've been struggling with getting the docker images provided by https://game.ci/ to build his project at all, let alone automating it in a pipeline.

https://game.ci/ has fantastic GitHub actions to automate all of this on each PR or push to main etc and then just upload the result of the build as an artifact and job done - takes minutes to setup and you can use your own machine as a self hosted runner to get the same build speed as local builds

These guys did a wonderful job at providing a docker-based build environment for Unity, btw: https://game.ci/

(Someone's built something similar for Unity, but it wasn't as one click when I last looked -- especially since Unity may require licenses.)

My repositories are on github, so I'm using Github Actions for build automation - I found it really easy to setup compared to other platforms. + There's basically a ready-made action for building with unity - game.ci (although I wrote my own solution for iOS).

Game CI seems to be pretty good, given the fact that it is open source and you can fix it if needed

Your testing team is using AppCenter.

Appcenter will allow you to build your app for iOS and install on your device without submitting to the App Store. https://appcenter.ms/

I used expo-updates with a CI script to push updates. CodePush is also a good alternative.

We've been using app center for build distribution (https://appcenter.ms/)

But, https://appcenter.ms/ and others like it are already available with generous free tiers and a lot more features (which you don't have to use, but can grow into), not to mention GitHub actions as others have noted. Does this advantages over existing, standard solutions?

There are lots of choices. Google android device testing. Offhand https://appcenter.ms comes to mind.

you don t need a mac, use microsofts app center to build it. https://appcenter.ms

I've heard good things about App Center from Microsoft https://appcenter.ms/

Don’t muck with automating simulators, it’s a PITA: we used https://aws.amazon.com/device-farm/ and it was ok. This was pretty ok: https://bitrise.io As much as I hate Microsoft, https://appcenter.ms was workable, but required the most calories and was slow.