Actions - .NET 8 MAUI job just hangs on dotnet build step with no error

[lesnolan]

Select Topic Area

Bug

Body

Hello,

I am close to being able to confirm with my team that we will switch over to GitHub. Unfortunately, I cannot sign-off because I am having this issue that the action/job appears to be just hanging.

It happens on this step which works on other environments like DevOps and GitLab.

To give you more context:

The app is a .NET MAUI 8, and the action is running on macos-latest

This is the step its running on when it just hangs and never stops:

Run dotnet build 'SiteCompass/SiteCompass.csproj' -c Test -f net8.0-maccatalyst
dotnet build 'SiteCompass/SiteCompass.csproj' -c Test -f net8.0-maccatalyst

this is the last couple of output strings on the job itself

/Users/runner/work/sitecompass/sitecompass/SiteCompass/Services/Files/FilesService.cs(17,61): warning CA1416: This call site is reachable on: 'MacCatalyst' 13.1 and later. 'FileSaver.SaveAsync(string, string, Stream, CancellationToken)' is only supported on: 'Android' 26.0 and later, 'iOS' 14.0 and later, 'maccatalyst' 14.0 and later, 'Tizen', 'Windows'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416) [/Users/runner/work/sitecompass/sitecompass/SiteCompass/SiteCompass.csproj::TargetFramework=net8.0-maccatalyst]
  SiteCompass -> /Users/runner/work/sitecompass/sitecompass/SiteCompass/bin/Test/net8.0-maccatalyst/maccatalyst-arm64/SiteCompass.dll
  Optimizing assemblies for size may change the behavior of the app. Be sure to test after publishing. See: https://aka.ms/dotnet-illink
  Optimizing assemblies for size. This process might take a while.
ILLINK : warning MT0182: Not linking with the framework OpenGLES (referenced by a module reference in SkiaSharp.Views.iOS.dll) because it's not available on the current platform (MacCatalyst). [/Users/runner/work/sitecompass/sitecompass/SiteCompass/SiteCompass.csproj::TargetFramework=net8.0-maccatalyst]

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐