Set underlying sdk version to a lower version

[yunusefendi52]

Description

When I upgraded from Maui 7.0.49 -> 7.0.59 there is a minimum sdk version that maui needs, but I will ios for an example because it causes me to update xcode 14.0 to 14.2, and xcode is really huge to download
7.0.49 -> Microsoft.iOS.Sdk/16.0.1478
7.0.59 -> Microsoft.iOS.Sdk/16.2.1004

As you can see there is bumped version. if I compile maui 7.0.59 using Microsoft.iOS.Sdk/16.0.1478 it wouldn't work because Maui minimum requirement is using 16.2.1004 when it doesn't have to

Solution? I think pin the underlying sdk to the lowest version, for ios instead of net7.0-ios use net7.0-ios16.0

Steps to Reproduce

1. compile maui app 7.0.59 using Microsoft.iOS.Sdk/16.0.1478

Expected: Compile just fine
Outcome: Error build

Link to public reproduction project repository

do you need to? it's a dependency issue

Version with bug

7.0 (current)

Last version that worked well

7.0 (current)

Affected platforms

iOS, Android

Affected platform versions

iOS, Android

Did you find any workaround?

Upgrade, but it's not a workaround, it's an obligation from Maui sigh

Relevant log output

No response

[yunusefendi52]

Related issue dotnet/sdk#30103

[mattleibow]

I had a chat with the team working on Apple things and it appears that we use the latest versions of things because Apple requires that. Maybe not the instant we get the update, but often very soon after:

Apple will reject submissions if they are not done with the current stable Xcode 
Also Xcodes stop working, for example Xcode 13 no longer runs on Ventura at all
and lastly Xcode forces users to upgrade macOS too, we are close to the next Xcode to require Ventura in order to work 

[mattleibow]

I am going to close this as we are really driven by the schedule of the Apples.

[yunusefendi52]

Sorry @mattleibow 1 question. Isn't possible for library (maui in this case) to set minimum version to 16.0 for example? It will pickup whatever the user has (16.2). So library author doesn't have to force you (unless there is a difference api breaking change)

I am comparing current state with xamarin.forms. Xf has minimum version of Xamarin.iOS10 but it can be still compile using the targeted version (currently can be 16.0 or 16.2)

[yunusefendi52]

Here is for comparison inside nuget package, this is also the case for other platforms not just ios

[mattleibow]

@dalexsoto ?

[rolfbjarne]

Isn't possible for library (maui in this case) to set minimum version to 16.0 for example?

Kind of, but it gets complicated because MAUI is a workload, and not just a library. That means that you'd have to update the MAUI workload(s), but not the iOS workload, and then you're combining workloads from different versions, and that's not something we're testing (the test matrix would become huge after a while).

Also, due to dotnet/sdk#30103, it's not currently possible (but that will hopefully be fixed).

[yunusefendi52]

Maui is kinda workload-ish now, maui will use nuget package changes from @mattleibow #11206 is that changing anything?

So because maui will use nuget package instead of full workload, maui can use lower version?

just a reminder: this is also the case for other platforms, not just ios

[yunusefendi52]

Hi @mattleibow should this issue be open again? The reason is because Apple will reject app that uses old xcode version but not the library it self. So i think maui isn't going to be causing the problem if lower the minimum version (see xamarin.forms, uno.ui, basically other libraries)

[yunusefendi52]

Here is how it would look like (see net7.0-android30.0, net6.0-android30.0)

[yunusefendi52]

Ok, just spent GBs of bandwidth just to update maui. I am really wondering how can it be? 🤡 it shouldn't have to

[yunusefendi52]

Found another issue related to this I think #12122 (but closed)