Decorate all APIs with correct SupportedOSPlatform attributes #10170

marek-safar · 2020-11-27T15:22:35Z

As part of netcore migration, we need to correctly annotate all APIs with .NET 6 to work correctly with existing tooling (primary existing analyzers). The attributes already exist in .NET5 and could be extended if necessary.

Available attributes are listed at https://github.com/dotnet/designs/blob/main/accepted/2020/platform-checks/platform-checks.md#attributes

Required Actions

~~Generator: read existing attributes but generate the new ones for dotnet~~
Manual bindings: Add new attributes under a #if NET and hide existing ones under #else -> in progress
Update introspection tests to use the new attributes when doing the checks -> done, but parts disabled until manual bindings updates are completed

~~Time estimate: 2 weeks.~~

The text was updated successfully, but these errors were encountered:

spouliot · 2021-02-01T16:36:10Z

Beside the two issues above the migration means we lose the helper messages, usually the alternative API to use for obsolete/deprecated attributes. E.g. bindings

[Deprecated (PlatformName.iOS, 7, 0, message : "Use 'UbiquitousItemDownloadingStatusKey' instead.")]
[Deprecated (PlatformName.MacOSX, 10, 9, message : "Use 'UbiquitousItemDownloadingStatusKey' instead.")]
[Field ("NSMetadataUbiquitousItemIsDownloadedKey")]
NSString UbiquitousItemIsDownloadedKey { get; }

becomes

[BindingImpl (BindingImplOptions.GeneratedCode | BindingImplOptions.Optimizable)]
static NSString? _UbiquitousItemIsDownloadedKey;
[Field ("NSMetadataUbiquitousItemIsDownloadedKey",  "Foundation")]
[UnsupportedOSPlatform ("ios7.0")]
[UnsupportedOSPlatform ("macos10.9")]
public static NSString UbiquitousItemIsDownloadedKey {
...
}

marek-safar · 2021-02-02T08:34:54Z

You could consider using ObsoleteAttribute for that (extended in .net5).

https://github.com/dotnet/designs/blob/main/accepted/2020/better-obsoletion/better-obsoletion.md

spouliot · 2021-02-02T22:34:31Z

Unlike both [SupportedOSPlatform] and [UnsupportedOSPlatform] the [Obsolete] attribute is not allowed multiple times - but it does allow to use our Message property where it's the most useful.

We can use conditionals to work around that limit. That would look like:

[SupportedOSPlatform ("macos10.12.2")]
[SupportedOSPlatform ("watchos5.0")]
#if __WATCHOS__
[Obsolete ("API obsoleted in 'watchos7.0': Removed in Xcode 12.")]
#endif
[SupportedOSPlatform ("tvos14.0")]
public unsafe partial class MPMediaEntity : NSObject, INSCoding, INSSecureCoding {
...
}

The new Url and DiagnosticId could be used. That would allow developers to ignore the Apple obsoletion warnings (per platform?) independently of other normal obsolete.

Note that we might have case where .NET [Obsolete] and Xamarin [Obsoleted] (d suffix) were both used. That should not be common since they were used to indicate different things.

spouliot · 2021-02-03T02:21:06Z

The attribute messages are quote with ' but I think we can get something that's understandable with our normalized messages (or when there's none).

.../Xamarin.iOS.cs(449,46): warning BI1234: 'CTTelephonyNetworkInfo' is obsolete: 'Starting with ios14.0 Use the 'CallKit' API instead.'
.../Xamarin.iOS.cs(601,46): warning BI1234: 'IAdPreroll' is obsolete: 'Starting with ios12.0'

Also having a single [Obsolete] attribute reduce the platform assemblies sizes.

Before

-rw-r--r--  1 poupou  staff  19930624  2 Feb 20:07 _build//Microsoft.iOS.Runtime.ios-x64/runtimes/ios-x64/lib/net6.0/Xamarin.iOS.dll
-rw-r--r--  1 poupou  staff  22490624  2 Feb 20:04 _build//Microsoft.macOS.Runtime.osx-x64/runtimes/osx-x64/lib/net6.0/Xamarin.Mac.dll
-rw-r--r--  1 poupou  staff  13635072  2 Feb 20:06 _build//Microsoft.tvOS.Runtime.tvos-x64/runtimes/tvos-x64/lib/net6.0/Xamarin.TVOS.dll
-rw-r--r--  1 poupou  staff   8311296  2 Feb 20:03 _build//Microsoft.watchOS.Runtime.watchos-x86/runtimes/watchos-x86/lib/net6.0/Xamarin.WatchOS.dll

After

-rw-r--r--  1 poupou  staff  19801600  2 Feb 20:56 _build//Microsoft.iOS.Runtime.ios-x64/runtimes/ios-x64/lib/net6.0/Xamarin.iOS.dll
-rw-r--r--  1 poupou  staff  22390784  2 Feb 20:56 _build//Microsoft.macOS.Runtime.osx-x64/runtimes/osx-x64/lib/net6.0/Xamarin.Mac.dll
-rw-r--r--  1 poupou  staff  13563904  2 Feb 20:54 _build//Microsoft.tvOS.Runtime.tvos-x64/runtimes/tvos-x64/lib/net6.0/Xamarin.TVOS.dll
-rw-r--r--  1 poupou  staff   8262656  2 Feb 20:53 _build//Microsoft.watchOS.Runtime.watchos-x86/runtimes/watchos-x86/lib/net6.0/Xamarin.WatchOS.dll

even if the linker will remove all of them inside the final/release bundles.

This moves our current/legacy attributes to the ones added in dotnet 5 [1]. Short Forms (only in bindings) | Old | New | |---------------------------------------|-------------------------------------| | [iOS (7,0)] | [SupportedOSPlatform ("ios7.0")] | | [NoIOS] | [UnsupportedOSPlatform ("ios")] | Long Forms | Old | New | |---------------------------------------|-------------------------------------| | [Introduced (PlatformName.iOS, 7,0)] | [SupportedOSPlatform ("ios7.0")] | | [Obsoleted (PlatformName.iOS, 12,1)] | [Obsolete (...)] | | [Deprecated (PlatformName.iOS, 14,3)] | [UnsupportedOSPlatform ("ios14.3")] | | [Unavailable (PlatformName.iOS)] | [UnsupportedOSPlatform ("ios")] | Other changes * `[SupportedOSPlatform]` and `[UnsupportedOSPlatform]` are not allowed on `interface` [2] which means they cannot be used for protocols. This is currently handled by inlining the existing attributes on all members. * `[ObsoletedInOSPlatform]` was removed in net5 RC. This PR is now mapping the existing attributes to `[Obsolote]`, however multiple ones cannot be added so they need to be platform specific. Still Missing * [ ] Generator deduplication of type/members attributes for interfaces (due to [2]) * [ ] Manual bindings * [ ] Introspection tests updates References * [1] xamarin#10170 * [2] dotnet/runtime#47599 * [3] dotnet/runtime#47601

…te` (#10580) This moves our current/legacy attributes to the ones added in dotnet 5 [1]. Short Forms (only in bindings) | Old | New | |---------------------------------------|-------------------------------------| | [iOS (7,0)] | [SupportedOSPlatform ("ios7.0")] | | [NoIOS] | [UnsupportedOSPlatform ("ios")] | Long Forms | Old | New | |---------------------------------------|-------------------------------------| | [Introduced (PlatformName.iOS, 7,0)] | [SupportedOSPlatform ("ios7.0")] | | [Obsoleted (PlatformName.iOS, 12,1)] | [Obsolete (...)] | | [Deprecated (PlatformName.iOS, 14,3)] | [UnsupportedOSPlatform ("ios14.3")] | | [Unavailable (PlatformName.iOS)] | [UnsupportedOSPlatform ("ios")] | Other changes * `[SupportedOSPlatform]` and `[UnsupportedOSPlatform]` are not allowed on `interface` [2] which means they cannot be used for protocols. This is currently handled by inlining the existing attributes on all members. * `[ObsoletedInOSPlatform]` was removed in net5 RC. This PR is now mapping the existing attributes to `[Obsolote]`, however multiple ones cannot be added so they need to be platform specific. Remaining work (manual bindings update) tracked in #11055 References * [1] #10170 * [2] dotnet/runtime#47599 * [3] dotnet/runtime#47601

rolfbjarne · 2021-06-29T19:03:53Z

It seems we need to generate the SupportedOSPlatform attribute if there are attributes for other platforms, because otherwise it's implied that the lack of an SupportedOSPlatform attribute means the API isn't available.

Ref: https://discord.com/channels/732297728826277939/732297808148824115/859501966349565992

dotMorten · 2021-06-29T19:46:58Z

Here's the list I have so far:

warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.StopUpdatingHeading()' is only supported on: 'macOS/OSX' 11.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.RequestWhenInUseAuthorization()' is only supported on: 'macOS/OSX' 11.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.StartUpdatingHeading()' is only supported on: 'macOS/OSX' 11.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIApplication.StatusBarOrientation.get' is unsupported on: 'ios' 9.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIApplication.StatusBarOrientation' is unsupported on: 'ios' 9.0 and later, 'macOS/OSX' 10.14 and later, 'maccatalyst' 13.1 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.AuthorizationStatus.get' is only supported on: 'macOS/OSX' 11.0 and later, 'tvos' 14.0 and later, 'ios' 14.0 and later, 'maccatalyst' 14.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.AuthorizationStatus' is only supported on: 'macOS/OSX' 11.0 and later, 'tvos' 14.0 and later, 'ios' 14.0 and later, 'maccatalyst' 14.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.Status.get' is unsupported on: 'ios' 14.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.Status' is unsupported on: 'ios' 14.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLFloor.Level' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Floor.get' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Floor' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Course' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Course.get' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLFloor.Level' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Floor.get' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Floor' is only supported on: 'macOS/OSX' 10.15 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Speed.get' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Speed' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Course' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Course.get' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Speed' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocation.Speed.get' is only supported on: 'tvos' 13.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.HeadingAvailable.get' is only supported on: 'macOS/OSX' 11.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'CLLocationManager.HeadingAvailable' is only supported on: 'macOS/OSX' 11.0 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIStringDrawing.StringSize(NSString, UIFont, nfloat, UILineBreakMode)' is unsupported on: 'ios' 7.0 and later, 'macOS/OSX' 10.14 and later, 'maccatalyst' 13.1 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIKey.ModifierFlags' is only supported on: 'ios' 13.4 and later, 'tvos' 13.4 and later, 'maccatalyst' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIStringDrawing.StringSize(NSString, UIFont, nfloat, UILineBreakMode)' is unsupported on: 'ios' 7.0 and later, 'macOS/OSX' 10.14 and later, 'maccatalyst' 13.1 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIKey.CharactersIgnoringModifiers' is only supported on: 'ios' 13.4 and later, 'tvos' 13.4 and later, 'maccatalyst' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIStringDrawing.StringSize(NSString, UIFont, nfloat, UILineBreakMode)' is unsupported on: 'ios' 7.0 and later, 'macOS/OSX' 10.14 and later, 'maccatalyst' 13.1 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIStringDrawing.StringSize(NSString, UIFont, nfloat, UILineBreakMode)' is unsupported on: 'ios' 7.0 and later, 'macOS/OSX' 10.14 and later, 'maccatalyst' 13.1 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIPress.Key.get' is only supported on: 'ios' 13.4 and later, 'tvos' 13.4 and later, 'maccatalyst' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIPress.Key' is only supported on: 'ios' 13.4 and later, 'tvos' 13.4 and later, 'maccatalyst' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIScrollTypeMask.Continuous' is only supported on: 'ios' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIPanGestureRecognizer.AllowedScrollTypesMask.set' is only supported on: 'ios' 13.4 and later.
warning CA1416: This call site is reachable on: 'iOS' 13.0 and later. 'UIPanGestureRecognizer.AllowedScrollTypesMask' is only supported on: 'ios' 13.4 and later.

spouliot · 2021-07-28T15:46:12Z

hmm... I thought it would fall back to the assembly-level attribute

from src/MinimumVersions.cs.in

[assembly: SupportedOSPlatform ("ios@DOTNET_MIN_IOS_SDK_VERSION@")]

into src/MinimumVersions.cs

[assembly: SupportedOSPlatform ("ios10.0")]

rolfbjarne · 2021-09-13T07:31:04Z

A user reported this:

/Users/Hamish/Projects/MandelbrotMakerTest/MandelbrotMakerTest.MacOSWindow/ViewController.cs(205,16): warning CA1416: This call site is reachable on: 'macOS/OSX' 10.14 and later. 'NSSavePanel' is unsupported on: 'macOS/OSX' 10.15 and later. [/Users/Hamish/Projects/MandelbrotMakerTest/MandelbrotMakerTest.MacOSWindow/MandelbrotMakerTest.MacOSWindow.csproj]
/Users/Hamish/Projects/MandelbrotMakerTest/MandelbrotMakerTest.MacOSWindow/ViewController.cs(195,8): warning CA1416: This call site is reachable on: 'macOS/OSX' 10.14 and later. 'NSFileHandle.WriteData(NSData)' is unsupported on: 'macOS/OSX' 10.15 and later.

which is a bit weird, because neither NSSavePanel nor NSFileHandle have any availability attributes, which means they should get the assembly-level default.

Ref: https://discord.com/channels/732297728826277939/732297808148824115/886792528697901057

spouliot · 2021-09-13T15:44:16Z

which is a bit weird,

@rolfbjarne not really :) it's right there

		[Deprecated (PlatformName.MacOSX, 10,15, message: "Use 'Write (out NSError)' instead.")]
		[Deprecated (PlatformName.iOS, 13,0, message: "Use 'Write (out NSError)' instead.")]
		[Deprecated (PlatformName.WatchOS, 6,0, message: "Use 'Write (out NSError)' instead.")]
		[Deprecated (PlatformName.TvOS, 13,0, message: "Use 'Write (out NSError)' instead.")]
		[Export ("writeData:")]
		void WriteData (NSData data);

That becomes an [UnsupportedOSPlatform ("macos10.15")] which gave the correct warning

That attribute does not allow us to tell why (the string part) so that should be generated as a separate [Obsolete] attribute

wrt SavePanel

		[Advice ("You must use 'SavePanel' method if the application is sandboxed.")]
		[Deprecated (PlatformName.MacOSX, 10, 15, message: "All save panels now run out-of-process, use 'SavePanel' method instead")]
		[Export ("init")]
		IntPtr Constructor ();

so I guess the code is trying to instance the type, which is not something it should do (anymore), and the default .ctor gets mapped to the type (for the compiler warning).

- The tool I wrote to convert attributes [mellite](https://github.com/chamons/mellite) does single pass through each file - This means files that define Foo and !Foo, each with availability attributes inside can not be proccessed - These 2 locations were easy to fix by moving defines inside binding definations, so I did that - About 10 other locations were not so easy, so those will be worked around by hand in the conversion process. Part of xamarin#10170

- The tool I wrote to convert attributes [mellite](https://github.com/chamons/mellite) does single pass through each file - This means files that define Foo and !Foo, each with availability attributes inside can not be proccessed - These 2 locations were easy to fix by moving defines inside binding definations, so I did that - About 10 other locations were not so easy, so those will be worked around by hand in the conversion process. Part of #10170

- Disable check "[FAIL] Both '{t}' and '{m}' are marked with `{s}`." type and member on that type in NET - Due to the behavior of NET6 style attributes, we are forced to duplicate availability attributes in many cases - See xamarin#10170 for details

- Disable check "[FAIL] Both '{t}' and '{m}' are marked with `{s}`." type and member on that type in NET - Due to the behavior of NET6 style attributes, we are forced to duplicate availability attributes in many cases - See #10170 for details

rolfbjarne · 2022-04-26T15:06:19Z

I have a new proposal:

Availability attribute mapping between legacy Xamarin and .NET

Suggestion:

Current	Dotnet (planned)
[Introduced (PlatformName.iOS, 7,0)]	[SupportedOSPlatform ("ios7.0")]
[Obsoleted (PlatformName.iOS, 12,1)]	[UnsupportedOSPlatform ("ios12.1")] + [Advice ("Starting in iOS 12.1, use XYZ instead.")]
[Deprecated (PlatformName.iOS, 14,3)]	[UnsupportedOSPlatform ("ios14.3")] + [Obsolete ("Starting in iOS 14.3, use XYZ instead.")]
[Unavailable (PlatformName.iOS)]	[UnsupportedOSPlatform ("ios")]

The main problem is the following scenario:

Developer needs to keep their app working an older iOS version, say iOS 14.
Apple obsoleted some API in iOS 15, providing an alternative.

If we want to provide a good message to the user when they use the old API (telling them about the new API in iOS 15), we currently have to use the Obsolete attribute.

However, this means that the user have to do something like this to have a warning-free build:

#pragma warning disable 618
    CalliOS14API ();
#pragma warning restore 618

adding a version check won't change anything:

    if (checkForiOS15) {
        CalliOS15API ();
    } else {
#pragma warning disable 618
        CalliOS14API ();
#pragma warning restore 618
    }

We need improvements in the .NET API to be able to handle this better.

The suggestion above has the advantage that if .NET 7 adds additional API
(such as a Message property on UnsupportedOSPlatformAttribute, or a new
ObsoleteInPlatformAttribute( we should be able to convert our .NET 6 to the
new .NET 7 hotness, because we have enough information to go backwards.

Ref: dotnet/runtime#47601
Ref: dotnet/runtime#40945
Ref: #10170

rolfbjarne · 2022-04-26T15:50:56Z

I've started a discussion about improving this in .NET 7: dotnet/runtime#68557

chamons · 2022-04-26T19:20:16Z

So I looked into implementing Rolf's suggestion, (though I think you flipped the advice/obsolete in the table) and I've run into a major problem:

error CS0579: Duplicate 'Advice' attribute

You can only have one Advice per item. Now for our attributes, that's "fine", as I can generate a #if array around the defines, just like we are today with Obsolete.

However, a number of our bindings are using Advice directly:

                [Advice ("Use 'UTType' constructor overloads.")]
                [DesignatedInitializer]
                [Export ("initWithURL:inMode:")]
                NativeHandle Constructor (NSUrl url, UIDocumentPickerMode mode);

or indirectly:

	[AttributeUsage (AttributeTargets.Method, AllowMultiple = false)]
	public sealed class RequiresSuperAttribute : AdviceAttribute {
		public RequiresSuperAttribute ()
			: base ("Overriding this method requires a call to the overriden method.")
		{
		}
	}

And thus mixing a Deprecated (or Obsolete if we aren't flipped) with one of those is non-obvious a compile error.

rolfbjarne · 2022-04-27T06:06:42Z

You can only have one Advice per item

My vote is for changing the Advice attribute to AllowMultiple=true.

I think you flipped the advice/obsolete in the table)

My thinking was that the Deprecated attribute is "stronger" than the Obsoleted attribute (in that if something is [Deprecated] Apple might reject your app, while [Obsoleted] is just a recommendation for the future), and in the same vein [Obsolete] is "stronger" than [Advice].

I'm fine with either way though.

That said, I'm not really sure we really need the distinction between [Deprecated] and [Obsoleted], we seem to use it somewhat interchangeably in the bindings. That's probably a discussion for the future though, this is whole attribute conversion is already complicated enough.

spouliot · 2022-04-27T19:02:55Z

AFAIK the [Advice] was only shown in the old/legacy adding for VS and VSfM. IOW those messages are not visible/helpful unless support for the attribute is present inside the IDE.

chamons · 2022-05-04T15:23:55Z

I'm going to finally, after like 5 months of work, call this good enough and done.

There are some clean up tasks for the future, but the known work is done, and I was able to test 4 NET sample and a large MAUI app and saw no spurious availability warnings.

dotMorten · 2022-05-10T04:02:06Z

What version is this in? With RC2 I'm still seeing lots of warnings in:

LocationManager.StartUpdatingHeading
LocationManager.RequestWhenInUseAuthorization
LocationManager.StopUpdatingHeading
CLLocation.Speed
CLLocation.Course
CLLocation.Floor
CLLocation.Floor.Level
CMGyroData.RotationRate
CMMagnetometerData.MagneticField
CMAccelerometerData.Acceleration

chamons · 2022-05-16T21:48:43Z

Apologies for the delay in response.

This only landed 12 days ago (#14877), so I'm not surprised it didn't make it to you 5 days after landing.

Let me look into when it should be available publicly.

chamons · 2022-05-16T21:51:23Z

Sorry for the trouble, the fix won't hit public until MAUI’s stable release, which will be "soon".

dotMorten · 2022-05-16T22:03:22Z

@chamons thanks for following up and sorry for being "too" eager :-) I was just really happy I could re-instate all my platforms warnings only to find I couldn't... patience... ugh 😁

chamons · 2022-05-18T18:52:02Z

🤞 that it's fixed for you soon @dotMorten - This was one of the most difficult fixes I've made since starting at Xamarin, and required writing custom tools and manually fixing hundreds of locations.

If after MAUI stable release you are seeing warnings unnecessarily, please open a new issue.

dotMorten · 2022-05-18T21:47:13Z

@chamons Glad you're getting to do challenging and VERY MUCH APPRECIATED work :-)

marek-safar mentioned this issue Nov 27, 2020

Xamarin developers get warnings when they call APIs that aren't available on the OS version they target dotnet/runtime#45193

Closed

3 tasks

rolfbjarne added dotnet An issue or pull request related to .NET (6) iOS Issues affecting iOS macOS Issues affecting macOS labels Nov 27, 2020

rolfbjarne added this to the .NET 6 milestone Nov 27, 2020

rolfbjarne added the bug If an issue is a bug or a pull request a bug fix label Nov 27, 2020

spouliot self-assigned this Jan 27, 2021

This was referenced Jan 28, 2021

Allow using SupportedOSPlatformAttribute on interfaces dotnet/runtime#47599

Closed

Add back ObsoletedInOSPlatformAttribute for net6 dotnet/runtime#47601

Closed

spouliot added enhancement The issue or pull request is an enhancement and removed bug If an issue is a bug or a pull request a bug fix labels Jan 28, 2021

spouliot mentioned this issue Feb 1, 2021

[.NET 6] External dotnet issues #8901

Closed

61 tasks

rolfbjarne added the dotnet-pri0 .NET 6: required for stable release label Feb 3, 2021

spouliot mentioned this issue Feb 4, 2021

[generator][dotnet] Add support for [Uns|S]upportedOSPlatformAttribute #10580

Merged

3 tasks

rolfbjarne added the estimate-2w label Feb 9, 2021

samhouts mentioned this issue Jul 7, 2021

Developers can target macOS UI with .NET 6 dotnet/runtime#44736

Closed

32 tasks

dalexsoto assigned tj-devel709 Aug 19, 2021

dalexsoto assigned chamons Dec 7, 2021

rachelkang mentioned this issue Dec 13, 2021

MTLDevice.GetAllDevices incorrectly annotated on macOS #13540

Closed

chamons mentioned this issue Jan 6, 2022

Prepare for NET6 attribute conversion with hand fixes #13658

Merged

chamons mentioned this issue Jan 14, 2022

[tests] Disable attribute duplication check #13745

Merged

dalexsoto removed the estimate-2w label Feb 1, 2022

chamons mentioned this issue Apr 4, 2022

Platform annotation issues in Microsoft.iOS assembly #14619

Closed

chamons mentioned this issue Apr 19, 2022

[NET Attribute Conversion][generator] Generate NET style attributes #14779

Merged

rolfbjarne mentioned this issue Apr 26, 2022

[API Proposal]: Add back ObsoletedInOSPlatformAttribute for .NET 7 dotnet/runtime#68557

Closed

chamons mentioned this issue Apr 29, 2022

Add a cecil test to compare [Availability] attributes (legacy) with [SupportedOSPlatform] (net6) #12544

Closed

vs-mobiletools-engineering-service2 mentioned this issue May 3, 2022

[release/6.0.3xx] [NET Attribute Conversion][generator] Generate NET style attributes #14877

Merged

chamons closed this as completed May 4, 2022

chamons mentioned this issue May 23, 2022

AVAudioEngine InputNode available only on TvOS #15093

Closed

ghost locked as resolved and limited conversation to collaborators Jun 18, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Decorate all APIs with correct SupportedOSPlatform attributes #10170

Decorate all APIs with correct SupportedOSPlatform attributes #10170

marek-safar commented Nov 27, 2020 •

edited by dalexsoto

Loading

spouliot commented Feb 1, 2021

marek-safar commented Feb 2, 2021

spouliot commented Feb 2, 2021 •

edited

Loading

spouliot commented Feb 3, 2021

rolfbjarne commented Jun 29, 2021

dotMorten commented Jun 29, 2021 •

edited

Loading

spouliot commented Jul 28, 2021

rolfbjarne commented Sep 13, 2021

spouliot commented Sep 13, 2021 •

edited

Loading

rolfbjarne commented Apr 26, 2022

rolfbjarne commented Apr 26, 2022

chamons commented Apr 26, 2022

rolfbjarne commented Apr 27, 2022

spouliot commented Apr 27, 2022

chamons commented May 4, 2022

dotMorten commented May 10, 2022

chamons commented May 16, 2022

chamons commented May 16, 2022

dotMorten commented May 16, 2022

chamons commented May 18, 2022

dotMorten commented May 18, 2022

Decorate all APIs with correct SupportedOSPlatform attributes #10170

Decorate all APIs with correct SupportedOSPlatform attributes #10170

Comments

marek-safar commented Nov 27, 2020 • edited by dalexsoto Loading

Required Actions

spouliot commented Feb 1, 2021

marek-safar commented Feb 2, 2021

spouliot commented Feb 2, 2021 • edited Loading

spouliot commented Feb 3, 2021

rolfbjarne commented Jun 29, 2021

dotMorten commented Jun 29, 2021 • edited Loading

spouliot commented Jul 28, 2021

rolfbjarne commented Sep 13, 2021

spouliot commented Sep 13, 2021 • edited Loading

rolfbjarne commented Apr 26, 2022

Availability attribute mapping between legacy Xamarin and .NET

rolfbjarne commented Apr 26, 2022

chamons commented Apr 26, 2022

rolfbjarne commented Apr 27, 2022

spouliot commented Apr 27, 2022

chamons commented May 4, 2022

dotMorten commented May 10, 2022

chamons commented May 16, 2022

chamons commented May 16, 2022

dotMorten commented May 16, 2022

chamons commented May 18, 2022

dotMorten commented May 18, 2022

marek-safar commented Nov 27, 2020 •

edited by dalexsoto

Loading

spouliot commented Feb 2, 2021 •

edited

Loading

dotMorten commented Jun 29, 2021 •

edited

Loading

spouliot commented Sep 13, 2021 •

edited

Loading