[net6-ios] UIKeyboard.BoundsUserInfoKey member is missing in Preview 12

[jeromelaban]

Description

Similar to #11237, the following member is present in xamarinios10 but is not present in net6.0-ios:

UIKeyboard.BoundsUserInfoKey

Environment

6.0.200-preview.22055.15 and VS 17.1 Preview 4.

[rolfbjarne]

UIKeyboardBoundsUserInfoKey has been deprecated by Apple for over 12 years, and their site says "Use UIKeyboardFrameBeginUserInfoKey or UIKeyboardFrameEndUserInfoKey instead."

Is there any reason you can't use those values instead?

[jeromelaban]

We certainly can. I'm mentioning this because it's a breaking change from net6 APIs, and that increases the overall burden of migrating to net6.

[rolfbjarne]

Ok, I'm going to close this since there's an alternative to the API in question (and recommended by Apple).

Also, there will be numerous breaking changes in .NET: #13087

[jeromelaban]

This is not particularly reassuring for the rest of the changes... Let's hope it'll not make migrating to .net6 too difficult for the rest of the ecosystem as a result.

For this particular change, even if it's deprecated in UIKit, the member is still present and works. Forcing downstream refactoring is implying lots of feature changes your dependents.

[rolfbjarne]

If there's a compelling reason for a particular API we've removed, we're certainly open to add it back. In this case it seems somewhat extreme to keep an API that been deprecated for over a decade, and for which there's an alternative.

[jeromelaban]

I still think the deprecation duration is not relevant in most cases. If Apple does not remove the API, I think .NET shouldn't either.

The code I'm dealing with here has been using this API for around 7 years, and has been working properly ever since.