-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[introspection] Fix according to macOS 12.4. Fixes #15229. #15230
[introspection] Fix according to macOS 12.4. Fixes #15229. #15230
Conversation
* Ignore anything Chip-related, the framework was removed from macOS. * Fix reporting errors some protocol-related errors so that they're actually reported as errors (by calling 'ReportError' instead of just adding the errors to a list that doesn't affect anything else). * Ignore the NSUserActivityRestoring protocol, according to the macOS headers it's attached to NSResponder using a category, which is invisible at runtime. Due to the previous point this didn't show up before, but once at least another error (which happened with the Chip framework), then this was listed as well. Fixes xamarin#15229.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chip continues to make trouble!
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ API diff for current PR / commitLegacy Xamarin (No breaking changes)
NET (empty diffs)
❗ API diff vs stable (Breaking changes)Legacy Xamarin (No breaking changes).NET (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:)
✅ Generator diffGenerator diff is empty Pipeline on Agent |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ API diff for current PR / commitLegacy Xamarin (No breaking changes)
NET (empty diffs)
✅ API diff vs stableLegacy Xamarin (No breaking changes).NET (No breaking changes)✅ Generator diffGenerator diff is empty Pipeline on Agent |
This comment has been minimized.
This comment has been minimized.
✅ API diff for current PR / commitLegacy Xamarin (No breaking changes)
NET (empty diffs)
✅ API diff vs stableLegacy Xamarin (No breaking changes).NET (No breaking changes)✅ Generator diffGenerator diff is empty Pipeline on Agent |
❌ [PR Build] Tests on macOS Mac Catalina (10.15) failed ❌Failed tests are:
Pipeline on Agent |
❌ [PR Build] Tests on macOS M1 - Mac Big Sur (11.5) failed ❌Failed tests are:
Pipeline on Agent |
Test failures are unrelated:
|
…marin#15230) * Ignore anything Chip-related, the framework was removed from macOS. * Fix reporting errors some protocol-related errors so that they're actually reported as errors (by calling 'ReportError' instead of just adding the errors to a list that doesn't affect anything else). * Ignore the NSUserActivityRestoring protocol, according to the macOS headers it's attached to NSResponder using a category, which is invisible at runtime. Due to the previous point this didn't show up before, but once at least another error (which happened with the Chip framework), then this was listed as well. * Add ignores for a couple of protocols. Fixes xamarin#15229.
…marin#15230) * Ignore anything Chip-related, the framework was removed from macOS. * Fix reporting errors some protocol-related errors so that they're actually reported as errors (by calling 'ReportError' instead of just adding the errors to a list that doesn't affect anything else). * Ignore the NSUserActivityRestoring protocol, according to the macOS headers it's attached to NSResponder using a category, which is invisible at runtime. Due to the previous point this didn't show up before, but once at least another error (which happened with the Chip framework), then this was listed as well. * Add ignores for a couple of protocols. Fixes xamarin#15229.
/sudo backport d17-2 |
Backport Job to branch d17-2 Created! The magic is happening here |
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6420603 for more details. |
reported as errors (by calling 'ReportError' instead of just adding the
errors to a list that doesn't affect anything else).
it's attached to NSResponder using a category, which is invisible at
runtime. Due to the previous point this didn't show up before, but once at
least another error (which happened with the Chip framework), then this was
listed as well.
Fixes #15229.