New pricing and breaking changes!

[mikhail-tokarev]

As of September 12, 2022, our default machine type will be Mac mini M1 instead of the Intel-based Mac mini. This change comes together with the release of our new Pay as you go plan that lowers the price for M1 machines by half and introduces a $299/month cap for unlimited build minutes, read more about it here.

As a result, you should be aware of the following changes:

• If you haven’t specified an instance type in your codemagic.yaml, your builds will run on Mac mini M1 starting from September 12. Personal accounts will have 500 free M1 minutes every month.

• All Mac mini M1 have Xcode 13.3.1 and later available. To use an older version of Xcode, switch to an Intel-based macOS machine (mac_mini or mac_pro instance type).

• The current version of Apple M1 virtualization does not support Android emulator or Docker containers. If your build requires Android emulator or Docker, change your workflow to run on an Intel-based macOS, Linux or a Windows machine.

To keep using Intel-based Mac mini, set instance_type to mac_mini. As the old Mac mini machines are being discontinued, we no longer provide a free access to mac_mini instance type starting from September 12.

[soygcm]

So basically if I'm paying and I haven't specified mac_mini my pipeline just brake. Why you didn't keep the mac_mini by default for pay users?

[mikhail-tokarev]

Hi @soygcm
not really. If you on pay-as-you-go plan and don't have instance type in codemagic.yaml file your build will be run using mac_mini_m1 instance type. And you can switch back to any other instance type by explicitly adding it to the yaml file.

[brightmind-loredo]

I only use the build UI so I don't have a build yaml. I changed to m1 in my build settings and built again. It took the same time as before. The build summary says "Machine: Mac Pro", build ID: 632cd35c3dad27b532d926fd ... Am I missing something?

[mikhail-tokarev]

Hi @brightmind-loredo
thank you for providing build id, I can see that it indeed used Mac Pro machine. Is there any chance you changed M1 in wrong workflow?

[gslender]

I can only see macOS M1 Standard VM in the workflow, and it seems since adding a billing account details (ie upgrading to pay as I go), I don't get 500 free M1 mins, so maybe I should downgrade back again. Are you supposed to still get 500 mins free even if you're enabled for billing?

[gslender]

The billing page shows that the macOS M1 Standard VM minutes are increasing and charges are being applied and no free m1 minutes are being spent - I don't think it's working the way you have suggested

So far, every time I execute a workflow, it charges my account

[gslender]

My account is personal too

[mikhail-tokarev]

can you share any build id? we will take a close look

[gslender]

6334fe236e6d538fde880540

[mikhail-tokarev]

we've checked your usage history and can see you used M1 minutes before September 12 when it was a paid feature. Right now you are using free minutes, so everything looks correct. Anyway feel free to contact us if you have any further questions!

[Alvaro948]

Hi @mikhail-tokarev, after setting instance type from mac_mini to mac_mini_m1 the build is failing on ionic capacitor:

      - name: Build ionic app
        script: |
          ionic cap build android --configuration production

Failed build: 63638b8db83454e5368c79ca
Successful build: 63638c6a49418626798bb6de (after reverting the instance type back to mac_mini)

[HCDevSG]

I did not used the code magic free minutes more then 6 minutes but I'm getting this issue