[infra][maccatalyst] Fix IO test compatibility issues occurring on MacCatalyst CI with macOS 14
@kotlarmilos is already working on this.
Since Jul 11, 2025.
- #131206 by @copilot-swe-agent — closed without merging
Assessment
This issue has not been assessed yet.
Description
During migration from macOS 12 -> macOS 14 queue in our testing infrastructure (https://github.com/dotnet/runtime/pull/113313), we encountered several issues related to permissions when running MacCatalyst test apps.
Permission pop-up
When trying to run System.IO.IsolatedStorage tests, pop-up with appears
"System.IO.IsolatedStorage.Tests.app” would like to access files in your Documents folder.
requiring user to manually allow access and probably causing timeouts experienced on the CI. The timeouts are coming inside the RemoveTests.cs. A workaround could be to allow the test app in System Settings -> Privacy & Security -> Full Disk Access but that would have to be done on every test machine.
How to reproduce:
./build.sh mono+libs -os maccatalyst -arch arm64 -c Debug./dotnet.sh build src/libraries/System.IO.IsolatedStorage/tests/System.IO.IsolatedStorage.Tests.csproj /p:RuntimeFlavor=Mono /t:Test /p:TargetOS=maccatalyst /p:TargetArchitecture=arm64 /p:Configuration=Debug /p:RunAOTCompilation=true /p:MonoForceInterpreter=true /p:UseNativeAotCoreLib=false
ReadExecute file access triggering SIGKILL
When trying to run System.IO.MemoryMappedFiles tests, the process is killed with
EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)). We should investigate if the test app signature is valid.
How to reproduce:
./build.sh mono+libs -os maccatalyst -arch arm64 -c Debug./dotnet.sh build src/libraries/System.IO.MemoryMappedFiles/tests/System.IO.MemoryMappedFiles.Tests.csproj /p:RuntimeFlavor=Mono /t:Test /p:TargetOS=maccatalyst /p:TargetArchitecture=arm64 /p:Configuration=Debug /p:RunAOTCompilation=true /p:MonoForceInterpreter=true /p:UseNativeAotCoreLib=false
- 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 ·