ILStrip failed when trying to publish net9.0-ios with Google.Maps.Utils.iOS.dll
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp, ios
- Domain
- build-system, mobile
Research direction
Clone the mapsilstriprepro repository and run dotnet publish -f "net9.0-ios" -c "Release" to reproduce the failure. Start at Microsoft.iOS.Sdk.net9.0_18.4/targets/Xamarin.Shared.Sdk.targets around line 917 and the ILStrip step; done means the sample publishes with assembly IL stripping enabled and without the reported index error.
Written by the indexing model from the issue text.
Description
Apple platform
iOS
Framework version
net9.0-ios
Affected platform version
.NET 9.0
Description
We are now in the middle of moving from .Net 8 to .Net 9 with MAUI app.
There is a problem with one of the packages that contains Google.Maps.Utils.iOS.dll and it doesn't matter if we are using Nuget like this: https://www.nuget.org/packages/Onion.Maui.GoogleMaps.Clustering/ or our own binding.
There is an error when publishing:
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk.net9.0_18.4/18.4.9289/targets/Xamarin.Shared.Sdk.targets(917,3): error : ILStrip failed for obj/Release/net9.0-ios/ios-arm64/linked/Google.Maps.Utils.iOS.dll: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
No trimmer settings i helping here as it looks like trimming process is quite ok. The error can be fixed only by setting <EnableAssemblyILStripping>false</EnableAssemblyILStripping> which we do not want.
This behavriour is only observed on .Net 9 while it was fine on previous version.
Steps to Reproduce
clone https://github.com/tklptbs/mapsilstriprepro/tree/main
Run dotnet publish -f "net9.0-ios" -c "Release" on attached repo
Did you find any workaround?
<EnableAssemblyILStripping>false</EnableAssemblyILStripping>
Build logs
No response
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·