[d15-9] Bump Xamarin.MacDev to get fix for #5277. #5286
Conversation
Bump Xamarin.MacDev to get fix for #5277, and use a custom Xamarin.MacDev branch to only get this commit from Xamarin.MacDev. Commit list for xamarin/Xamarin.MacDev: * dotnet/macios-devtools@9b55404 Keys in property list dictionaries aren't necessarily unique. Fixes xamarin-macios#5277. Diff: dotnet/macios-devtools@39ea45b...9b55404 Fixes #5277.
rolfbjarne
added
build-package
|
Build success |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ✅ Build succeeded |
|
build |
|
This build failed main test run with |
|
Build success |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Build' 🔥 : hudson.AbortException: script returned exit code 2 🔥 Build failed 🔥 |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Build' 🔥 : hudson.AbortException: script returned exit code 2 🔥 Build failed 🔥 |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Checkout' 🔥 : hudson.AbortException: There is already a newer build in progress (#5) |
|
Looks like apple fixed it (see last comments in this thread: https://forums.developer.apple.com/message/343811#343811 ). I was able to create new provision (with new bundle id) and VS for Mac saw it successfully. However I guess you need to regenerate old provisions at apple developer portal, as they still have duplicate keys. And maybe VS for Mac should show some logs about provision profiles, as it's very complicated to define the reason, why it don't see the provisioning profile on your machine. |
|
@Saratsin Yes, it looks like Apple fixed this on their side, I was just able to re-generate a provisioning profile that was broken yesterday, and now it's fixed. Thanks! |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : hudson.AbortException: script returned exit code 1 ✅ Build succeeded |
|
I'm closing this since Apple has already fixed the issue on their end; re-generating the provisioning profiles is all that's needed. |
Bump Xamarin.MacDev to get fix for #5277, and use a custom Xamarin.MacDev
branch to only get this commit from Xamarin.MacDev.
Commit list for xamarin/Xamarin.MacDev:
Diff: dotnet/macios-devtools@39ea45b...9b55404
Fixes #5277.