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
Please retest with 3.0.0 — and if it still fails, 3.0.0 will tell us why, which 2.4.2 could not.
This was reported against 2.4.2, where a bundle the tool could not read produced a silently empty report and exit code 0. That failure mode is gone: 3.0 added fault collection, so unreadable invocation records, unresolved attachments and failed payload exports are now reported explicitly and the tool exits 3 rather than pretending success. (--lenient restores the old always-exit-0 behaviour if you have tooling that depends on it.)
So one of two things will happen on 3.0.0:
the report generates correctly — Xcode 15 bundles work here now, and this can be closed; or
it still fails, but prints the specific fault instead of an empty page, which is the information needed to actually fix it.
Either outcome is more useful than the original report. If you can share the fault output from the second case, that would be ideal.
Activity
shahidlatif2021 commentedon Mar 27, 2024
Warning: Can't find invocation record for : /.xcresult
tylervick commentedon Aug 11, 2026
Please retest with 3.0.0 — and if it still fails, 3.0.0 will tell us why, which 2.4.2 could not.
This was reported against 2.4.2, where a bundle the tool could not read produced a silently empty report and exit code 0. That failure mode is gone: 3.0 added fault collection, so unreadable invocation records, unresolved attachments and failed payload exports are now reported explicitly and the tool exits 3 rather than pretending success. (
--lenientrestores the old always-exit-0 behaviour if you have tooling that depends on it.)So one of two things will happen on 3.0.0:
Either outcome is more useful than the original report. If you can share the fault output from the second case, that would be ideal.