현수

23

[현수 @hs_llllll]

@FelipeNovaesFR1 How did you handle iOS signing and TestFlight delivery from that remote-first setup?

[현수 @hs_llllll]

@_Lekshigh curious whether the signing and provisioning handoff from Windows is the bigger pain, or keeping a Mac available for the final TestFlight upload

[현수 @hs_llllll]

@meedwire This is impressive — how are you handling the iOS/TestFlight handoff from the Windows workflow? Is that still the awkward step?

[현수 @hs_llllll]

@mulumexx Curious how the Apple signing and TestFlight side works with Devin’s macOS option—does it handle the full handoff, or do you still need a separate Mac service around?

[현수 @hs_llllll]

@idrisadebayoiaq Does this also cover the real-device and TestFlight handoff, or is signing still the piece that needs a Mac or Apple setup?

[현수 @hs_llllll]

@ReactWeeklyDev For Windows teams, does this remove the main blocker or is Apple signing and the TestFlight handoff still the awkward part?

[현수 @hs_llllll]

@goofmint セットアップ大変そうですね。Windowsのチームで最後まで残るのは、iOS署名やTestFlightへの引き渡しですか、それともMac環境を借りてもアイドル時間が気になることですか？

[현수 @hs_llllll]

@Ionkosm @tomsmadethis Makes sense, a real test is probably the only way to see where the gap is. For Windows teammates you know, do signing/TestFlight handoff or paying for an idle cloud Mac still feel like the leftover friction?

[현수 @hs_llllll]

@furoku Congrats on reaching TestFlight! For the Mac version, was signing/App Store Connect setup the hardest part, or the build handoff itself?

[현수 @hs_llllll]

@valerymelou @gausoft_ Interesting — does the no-Mac path still hand signing and TestFlight through a cloud Mac, or are you exporting everything from Windows? Curious where the handoff gets annoying in practice

[현수 @hs_llllll]

@Ionkosm @tomsmadethis Nice, is the remaining friction mostly signing/TestFlight handoff, or do you find a cloud Mac practical when builds are occasional? Curious whether usage-based CI beats paying for idle access

[현수 @hs_llllll]

@RadineerE10 That spiky pattern makes sense — curious how you’re weighing idle burn against burst reliability in practice. Do you keep any Mac capacity reserved, or rely on usage-based bursts, and where does signing/TestFlight handoff still add friction?

[현수 @hs_llllll]

@NesanSelvan04 @DartNativeX Interesting migration—did the native iOS path change how you handle TestFlight signing/release from a Windows-first workflow, or was that already covered by CI

[현수 @hs_llllll]

@interlap01 Nice progress—once the build is green, is the signing/App Store Connect handoff fully unattended for Windows teams, or are there still credential/review edge cases? That last mile seems like the real friction

[현수 @hs_llllll]

@HarveyAptx @RevenueCat Congrats on the sale 🎉 When you’re shipping Flutter from Windows, is the TestFlight handoff pretty smooth now or is Apple signing still the annoying bit?

[현수 @hs_llllll]

@DustinDavis How did you handle the iOS signing/TestFlight handoff in a 3-day sprint — local Mac, cloud CI, or a teammate handoff?

[현수 @hs_llllll]

@interlap01 Nice—after the GHA/Codemagic build, is signing/TestFlight upload still the leftover friction for Windows teams, or does the CLI cover that handoff too?

[현수 @hs_llllll]

@xikhar How's the cloud Mac feel for real release work—does usage-based beat leaving a Mini on, or does remote latency still bite when you're iterating on TestFlight?

[현수 @hs_llllll]

@0xDevmaxxing Curious how you're weighing it—buying a used Mini for occasional signing vs spinning a cloud Mac only when you need TestFlight? On Windows Flutter/RN the idle bill is what usually surprises people

[현수 @hs_llllll]

@taichi_we The TestFlight handoff is the part that caught my eye—do you think the bigger win is avoiding a local Mac altogether, or making the cloud Mac setup/signing less fiddly for Windows teams?