:wave: Building an embedded Xcode framework takes too long for the first time. This is not a problem...

# multiplatform

[Nacho Ruiz Martin]

👋 Building an embedded Xcode framework takes too long for the first time. This is not a problem locally, because then the Gradle cache starts making magic and each consecutive build is good enough, but on CI this means that:
1. On GitHub: It consumes all the free monthly build minutes because Mac machines cost 10 times more in minutes
2. On Bitrise: It always encounters the timeout of 30 minutes that the free tier offers.
Do you have any strategy to ease this pain point?
Thanks!

[hfhbd]

Do you use the Gradle build cache GutHub action? Did you also try the M1 macOS runner on GitHub?

[Nacho Ruiz Martin]

Gradle build cache GutHub action

Ah, I don’t. I wasn’t aware of its existence. Is it this one?

Did you also try the M1 macOS runner on GitHub?

I think so? I added this on github actions:

runs-on: macos-latest

[hfhbd]

Nope: https://github.com/gradle/actions

[hfhbd]

Nope: macos-14

[Nacho Ruiz Martin]

Nope: https://github.com/gradle/actions

I think I can’t really use this one because I’m using Fastlane to build my iOS App.

[hfhbd]

It should work too

[Nacho Ruiz Martin]

So just adding :

- name: Setup Gradle
      uses: gradle/actions/setup-gradle@v3

Should magically cache the output from Fastlane?

[hfhbd]

Yes

[Nacho Ruiz Martin]

That sounds… awesome.

[Nacho Ruiz Martin]

Thanks, mate, I’ll try 👍

[hfhbd]

By default it only caches the main branch, so you need to merge/commit it in main branch first to get the effect. (And wait for a PR/change after successful run creating the cache).

[Nacho Ruiz Martin]

Ok, that makes sense! 🙂 Thank you.