You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 120ae34
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios-runner): carry the device's answer onto the failure it explains
Developer Mode off was the only device state no later step could change, and it is the only one
that keeps refusing a run before the build. The developer disk image is mounted on demand by
CoreDevice during build and launch since iOS 17, so a phone that has just been rebooted reports it
down while the very next build clears it: refusing there turned a self-clearing state into a failed
run. The preflight now hands the states back, the build carries them, and an unavailable image is
published onto a build that named no cause of its own — beside xcodebuild's own sentence, never in
place of it.
A log flush gained the deadline and abort it was missing, and a refused append is recorded instead
of dropped, because an offset measured over bytes that never landed is not a boundary.
Promise.reject(newError('this case records no device report')),
53
59
);
54
60
@@ -59,8 +65,8 @@ beforeEach(() => {
59
65
});
60
66
});
61
67
62
-
for(constfixtureofREPORTS){
63
-
test(`a device reporting ${fixture.deviceReport.developerMode} mode and ${fixture.deviceReport.developerDiskImage} disk image publishes${fixture.reason}`,async()=>{
68
+
for(constfixtureofREFUSALS){
69
+
test(`a device reporting ${fixture.deviceReport.developerMode} mode refuses the run with${fixture.reason}`,async()=>{
"note: Using provisioning profile \"match-development\" to sign the app bundle (in target 'AgentDeviceRunner' from project 'AgentDeviceRunner')\nerror: cannot find 'AgentDeviceRunnerCommand' in scope (in target 'AgentDeviceRunnerUITests' from project 'AgentDeviceRunner')\n** TEST BUILD FAILED **\n",
227
231
note: 'The hazard the bare `provisioning profile` trigger carried (#2688 review): a failing build can print the profile it used while the failure is a compile error. A benign mention must keep cache-recovery advice; it also says nothing Xcode calls code signing, which is its own honest row.',
"error: cannot find 'AgentDeviceRunnerCommand' in scope (in target 'AgentDeviceRunnerUITests' from project 'AgentDeviceRunner')\n** TEST BUILD FAILED **\n",
note: 'The corroborated pairing (#2683 review): a build that names no cause, on a phone core read directly as reporting its image down. Naming the image beats cache-recovery advice; the state also travels as details.developerDiskImage.',
243
+
},
244
+
{
245
+
id: 'team-id-failure-on-device-with-image-down',
246
+
reason: 'signing_no_development_team',
247
+
site: 'build-for-testing',
248
+
xcodeVersion: UNOBSERVED,
249
+
provenance: 'shipped-sniff-trigger',
250
+
output:
251
+
"error: Signing for \"AgentDeviceRunner\" requires a development team (in target 'AgentDeviceRunner' from project 'AgentDeviceRunner')\n** TEST BUILD FAILED **\n",
note: 'The decisive pairing, and the one #2682 used to answer with Developer Mode advice: the toggle is on and only the image is down. The enabled half is the captured state; a device waiting on device support has not been captured.',
275
+
note: 'The decisive pairing, and the one #2682 used to answer with Developer Mode advice: the toggle is on and only the image is down. It is NOT a pre-build refusal (#2683 review): iOS 17+ mounts the image on demand during build and launch, so this report has to survive to a failure — which is what `unclassified-build-on-device-with-image-down` records. The enabled half is captured on some devices; a device waiting on device support has not been captured.',
0 commit comments