I’m wondering if we could have a mechanism to “encapsulate” unknown error -1=ffffffffffffffff errors (that are super generic). Similar to MT/MM errors, we could redirect to some documentation where we would explain that this is a generic codesign issue and that we recommend doing X to try to fix it.
I’m wondering if we could have a mechanism to “encapsulate”
unknown error -1=ffffffffffffffff
errors (that are super generic). Similar to MT/MM errors, we could redirect to some documentation where we would explain that this is a generic codesign issue and that we recommend doing X to try to fix it.We do something like that here - https://github.com/xamarin/xamarin-macios/blob/master/tools/mmp/driver.cs#L848 where we special case a few “known” error codes else throw a more generic error.