Replies: 1 comment
-
I experience the exact same issue when attempting to build maccatalyst outside the Mac App Store. Any guidance to remedy this would be appreciated as it is blocking our CI build testing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am not sure if here is the right place, but maybe someone is around to help.
I can use the dotnet publish command locally with my MacCatalyst app to produce a signed .pgk. This .pkg is accepted by Testflight without any problems.
After the initial, manual release, I wanted to set up a Github Action to build and upload to Testflight once I merge into my main branch.
I use the established action https://github.com/marketplace/actions/download-apple-provisioning-profiles to download the provisioning profiles, and they get stored in the worker's MobileProvision folder, according to the action output:
The dotnet publish command however always says there is no matching profile...
The same command (copy and pasted) works on my local machine, though.
Here is the code for both action steps as well:
Thanks in advance for any tip/help with that.
Beta Was this translation helpful? Give feedback.
All reactions