Build Android with non-maui workflow

[smoogipoo]

The .NET SDK was updated to 8.0.400 over the weekend/very close to it, and our workflows started intermittently failing since. I don't know why, but I'm hoping this fixes it...

• (-8h, fail): https://github.com/ppy/osu/actions/runs/11883407684/job/33110128684
• (-6h, pass): https://github.com/ppy/osu/actions/runs/11884177358/job/33111984290
• (-6h, pass): https://github.com/ppy/osu/actions/runs/11884186730/job/33112007786
• (-1h, fail): https://github.com/ppy/osu/actions/runs/11887442003/job/33120212673

Related issues:

• NETSDK1139: The target platform identifier android was not recognized on windows-2022 image version 20241113.3.0 actions/runner#3578
• Fix: NETSDK1139: The target platform identifier android was not recognized getsentry/sentry-dotnet#3764

Of note, sentry also uses maui-android. Our build appears to pass without it.

[bdach]

and our workflows started intermittently failing since

At least in the ones you've linked in the OP, all failures are on the newer github runner image (this is visible if you "download raw logs").

[peppy]

Confirms my AB testing runners on live theory 👍

[bdach]

Um... the android action failed here. And it's already supposedly getting the "correct" non-maui one. So I think this is a swing and a miss, unfortunately...

[smoogipoo]

Well... At least that's two more data points because this same commit passed on my fork. Will report even further upstream.

Edit: nvm it didn't pass on my fork

Though I believe this is still fine to merge in, the ios build already uses non-maui so if anything this is standardising it.

[bdach]

Actually you know what, I believe there used to be something weird in the past wherein the changes don't actually take effect until they're in master, so maybe the UI is just confused somehow...? Dunno. Let's try and get this in I guess 🤷

[bdach]

Nah framework is on android and not maui-android and still breaks, so my hopes aren't high.

[smoogipoo]

Worst case we can rollback the sdk or workflow so not all is lost. Not too important for now regardless since we have an existing mostly-up-to-date build, will just report upstream and figure it out if it isn't f fixed by next time.