MATCH does not comply with Apple (developer) profiles for iOS Apps running on Apple Silicon (M1)

[Carlit0]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

To be able to run iOS Apps on Apple Silicon / M1 (Target: My Mac (Designed for iPad)) you have to enable "include Mac devices" and include the desired device in the Apple Developer Profile.
Of course, the UDID of the M1-device had to be registered beforehand :)

However, if If I run fastlane match with --force_for_new_devices or --force the previously included device gets deselected/excluded from the profile and there is no option to avoid it.
btw: The enabled "include Mac devices" switch stays enabled in the profile.

So in short: fastlane match with --force_for_new_devices or --force filters out all macos devices on an iOS profile even though we want them to be included to be able to run iOS Apps on Target: My Mac (Designed for iPad)

related to #17690

Command executed

fastlane match with --force_for_new_devices or --force

Complete output when running fastlane, including the stack trace and command used

The command executes successfully.

Environment

✅ fastlane environment ✅

Stack

Key	Value
OS	11.2.3
Ruby	2.7.2
Bundler?	false
Git	git version 2.24.3 (Apple Git-128)
Installation Source	~/.rbenv/versions/2.7.2/bin/fastlane
Host	macOS 11.2.3 (20D91)
Ruby Lib Dir	~/.rbenv/versions/2.7.2/lib
OpenSSL Version	OpenSSL 1.1.1j 16 Feb 2021
Is contained	false
Is homebrew	false
Is installed via Fabric.app	false
Xcode Path	/Applications/Xcode.app/Contents/Developer/
Xcode Version	12.4

generated on: 2021-04-20

Screenshot of an Apple developer profile highlighting the "include Mac devices" functionality, that fastlane match does not comply with:

One additional note:
The registered (M1) macos device is not a "normal" macos device. We have to register the UDID of the macos device NOT the UUID. The provisioning UDID looks similar to an iOS UUID but looks completely different from a macos UUID.

[fastlane-bot]

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

[patreu22]

Can confirm that issue, would be great if somebody could look into that :)

[max-ott]

As far as I know this is the expected behaviour. Fastlane was initially / historically built for mobile / iOS apps. Some Mac app functionalities were available, but most of the time more by accident than by design. (So I consider this more "working as expected" than an actual bug)

Feel free to open a pull-request to add this functionality!

[Carlit0]

Hello @max-ott , maybe you got me wrong. I meant running iOS Apps. However, with the new Apple Silicon you are able to run iOS Apps on macos natively.
Expected behaviour would be that I can build for that case.
With fastlane match with --force_for_new_devices or --force this can not be achieved.

[max-ott]

It's still a different way than the standard iOS way as you described it yourself. It would definitely be great if that's supported, but it's a feature addition and not a bug.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Kylmakalle]

I Also face this and think it would be a great opportunity to support m1 macs provisioning for iOS apps

[radko93]

Is there any workaround for this?

[Carlit0]

Is there any workaround for this?

1. include the device manually and don't run match again with --force_for_new_devices or --force.
2. change fastlane filter locally: Sigh won't include M1 devices on the provisioning profile. (temp workaround: edit /sigh/runner.rb) #17690 (comment)

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Kylmakalle]

bump

[rockylive]

Bump, M1 still have this issue

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Kylmakalle]

M1 Macs are more common now in development.
I will definitely bump this issue once more.

[CraigSiemens]

@max-ott This is a feature we'd like as well. Do you have any recommendations for what an acceptable solution would look like?

I did a quick look and it could be setup to always add Mac devices to iOS provisioning profiles, or there could be another flag passed sigh and/or match to --include-mac-devices.

[PoissonBallon]

Any news about it ? 🙏

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Kylmakalle]

👀

[Kylmakalle]

We still require this functionality :)

[taschik]

Hi, Thanks so much everyone that works on fastlane. What a great tool! I had a hard time figuring out why my M1 certificate was not added until I found this thread. Is there any update to this?

[juliengdt]

Bump here too.
Would be awesome to integrate easily our mac's uuid ! +100

[fonograph]

Bumpity bump. This just lost me an hour or so.

[zakkhoyt]

Bump. Another consumer in need of this functionality.

[colejd]

Me too thanks. This is going to be pretty important to support now that Xcode 14 supports single targets that can deploy to multiple platforms.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Kylmakalle]

This definitely should not be closed.
M2 macs are already here and we still not able to automatically provision them 😁

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[maxlapides]

I think we should keep this issue open. More work is needed to make it easy to manage Apple Silicon Macs in the Apple Developer system.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[maxlapides]

I still think we should keep this issue open. More work is needed to make it easy to manage Apple Silicon Macs in the Apple Developer system.

[cnordvik]

I think we got away with adding the Mac as ipod in the devices list when registering them 😅
00006001-111119920CEB801E M1MAC ipod

[fastlane-bot]

The pull request #20676 that closed this issue was merged and released as part of fastlane 2.211.0 🚀
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!