fastlane: MATCH does not comply with Apple (developer) profiles for iOS Apps running on Apple Silicon (M1)
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.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 7
- Comments: 32 (2 by maintainers)
Any news about it ? 🙏
@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.Bump, M1 still have this issue
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?
We still require this functionality 😃
Bump here too. Would be awesome to integrate easily our mac’s uuid ! +100
👀
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.