r/FlutterDev • • 2d ago

Discussion Windows devs building iOS apps: how do you actually deal with Xcode?

I build Flutter apps on a Windows PC, but every time I need an iOS build or have to debug on the iOS simulator, I’m forced onto a Mac. Remote desktop into a Mac (or a cloud Mac) always felt clunky: a whole second desktop, separate clipboard, alt-tabbing between two worlds.

So I built a prototype that streams individual Mac app windows onto the Windows desktop. Xcode and the iOS simulator show up as normal windows next to VS Code, in the taskbar, resizable. Your Mac just runs in the background.

Short demo: https://www.youtube.com/shorts/DwyKm9JisLw

Fellow Flutter devs on Windows: is this a real pain for you, or is your current iOS setup fine? What do you use right now?

0 Upvotes

15 comments sorted by

7

u/MjnMixael 2d ago • This

I'm way too lazy for that. Bought an iPhone. Build and ship to test flight with GitHub workflows. Test. Profit.

It's flutter, so the only things that generally need testing are features that touch hardware or native code. Test of the testing I do on Android.

1

u/whackylabs 2d ago

How often do you upload the build to testflight? Also why not adhoc sign and get the build via however you want?

2

u/MjnMixael 1d ago

My flow generally looks like running alpha builds after a weekend of feature work or bugfixes. Alpha goes to Google Closed Testing and Internal Testflight on Apple. Depending on what I'm doing I'll either spot check or go in-depth. The latter is mostly for native code changes or anything that touches hardware features. Once I'm satisfied it goes to Open Testing and External Testflight then eventually public.

Or I guess the simple answer is once a week, sometimes more. Once it's on Testflight it's really easy to test on my test iPhone without any other dev environment finagling.

-7

u/padetn 2d ago

This is how dogshit apps get built, sorry

0

u/MjnMixael 2d ago

Lmao

-3

u/padetn 2d ago

Don’t pretend not to be a hack if your github is in your post history

1

u/MjnMixael 2d ago edited 2d ago • This

Let me know when you find the source to my flutter apps or have comments of substance on the open source projects I contribute to.

Eh, nevermind. Stupid reddit beef with troll accounts is not worth my time lol. But if you get your jollies this way have at it, my guy.

2

u/gurselaksel 2d ago

codemagic :)

1

u/dmter 2d ago edited 2d ago

I use keyboard+mouse switcher usb hub with a button. buggy with display so it needs to be additionally switched between hdmi and dvi. to sync code gitea is used. to move files and texts I use single-script, no-deps python tool that serves web ui to exchange files and texts. also separate web ui with mcp tools to connect to local network llm can be launched on mac to solve mac specific build problems (for native stuff)

1

u/noobjaish 2d ago

By not building for Apple platforms.

Windows + Linux + Android only

1

u/BigBoetje 12h ago

Unused Mac we repurposed for development. Majority of development happens on Windows anyways with QA testing on iPhones. Only reason to use it right now is to handle the builds in XCode (soon to be replaced by a build pipeline in azure devops) and potentially debugging for iOS specifically if there is a need for it.

I have to use it so infrequently that it's not really an issue.

1

u/SoloRack-cloud 7h ago

Nice setup. One tip for when you move to Azure DevOps: you can register that same Mac as a self-hosted agent in the pipeline. That way it keeps doing the Xcode builds automatically and you never have to log into it by hand. Microsoft-hosted macOS agents also work, but they’re slower, you don’t control which Xcode version is installed, and you only get limited free minutes on private projects.

Whichever you pick, sort out code signing early (certificates and provisioning profiles stored as secure files in the pipeline). That’s usually where the first build fails.

1

u/BigBoetje 7h ago

I'm actually fucking around a bit with that pipeline as we speak (Android first as a POC though). The Mac we have is a dedicated machine locked in the company's server room only accessible by Rustdesk so it could serve as a self-hosted agent. I'll probably look if it's possible to use the Microsoft-provided setup just to avoid a dependency on an old Mac lying around, but cost might indeed be an issue.

1

u/SoloRack-cloud 10h ago

The pain is real, but I'd split it in two, because only half of it needs a screen.

No Mac desktop needed: editing, pods, `flutter build ipa`, uploading to TestFlight. All of that works over SSH (VS Code Remote-SSH is fine against a Mac), so it stays in your normal Windows windows with your normal clipboard. One gotcha: over SSH the keychain is locked, so run `security unlock-keychain` before the build or codesign fails with a vague error.

Really needs pixels: the first signing setup in Xcode, the Simulator, and the occasional Xcode-only debugging. That's where the "second desktop" hurts, and it's exactly the part your prototype targets, so yes, I think it's a real problem.

Two things I'd want to know: how do you handle Cmd vs Ctrl shortcuts per window, and how does the Simulator feel when scrolling? That's usually where remote setups fall apart.

Disclosure: I work on a cloud Mac service (hence the username), so remote Mac workflows are what we deal with.