Driving a locked iPhone from a coding session
WebDriverAgent needed an always-unlocked phone on my desk. iPhone Mirroring plus mirroir-mcp let an agent tap and verify MusicKit with the screen dark.
WebDriverAgent needed an always-unlocked phone on my desk. iPhone Mirroring plus mirroir-mcp let an agent tap and verify MusicKit with the screen dark.
The trust gate exists because a real tap got compromised. Twenty minutes of reading the formula, the permissions, and the maintainer beat ten seconds of running the suggested command.
An npm uninstall that leaves a 44MB binary behind, and a stash whose label records where HEAD was pointing, not what the diff is about.
A clean stash apply, a SwiftLint rule pattern-matching syntax instead of tracing consumption, and a three-tab stall that wasn't the bug I'd fixed.
Authorization is not subscription, an error type that doesn't exist, and a finished fix sitting invisible in git stash while I rebuilt it from notes.
The reported filter worked fine - the real issue was a different, deliberately independent filter, and the fix was a third option nobody had considered.
A three-wins gate, one requestReview() call, and a piece of received wisdom about simulator behavior that turned out to be wrong when actually tried.
The bug I filed was a write-time guard for something that couldn't happen. The real fix was a read-time exclusion, and its fixture broke four other tests.
A rename artifact, an API with no author field to update, and a device test proving the bug had already fixed itself - closed as accept-as-is.
There's no isEssential flag - Essentials is a song playlist. featuredAlbums is the real signal, and a fixture change exposed a test nobody had re-run.
Page 1 of 5