Description
During migration from macOS 12 -> macOS 14 queue in our testing infrastructure (#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