Xcode 15 beta 5 error: Invalid Swift parseable output message (malformed JSON)

Question

Created Jul ’23

Replies 7

Boosts 2

Views 1.2k

Participants 4

This is new in Xcode 15 beta 5. Command SwiftCompile emitted errors but did not return a nonzero exit code to indicate failure.

error: Invalid Swift parseable output message (malformed JSON): `0` (in target 'HiCoffee' from project 'HiCoffee')
error: Invalid Swift parseable output message (malformed JSON): `1` (in target 'HiCoffee' from project 'HiCoffee')
error: Invalid Swift parseable output message (malformed JSON): `{
  "kind": "finished",
` (in target 'HiCoffee' from project 'HiCoffee')

  "name": "compile",
  "pid": -1139,
  "process": {
    "real_pid": 95136
  },
  "exit-status": 0
}
Command SwiftCompile emitted errors but did not return a nonzero exit code to indicate failure

Answered by Gong in 761287022

Xcode 15 beta 6 fixed the issue.

Boost

Answer 1

ptsochantaris OP

Jul ’23

Having exactly the same issue

Screenshot 2023-07-26 at 08.40.59.png

0

Answer 2

Gong OP

Jul ’23

The error occurs on Xcode Cloud and blocks the CI 😔

截屏2023-07-26 21.07.45.png

0

Answer 3

Gong OP

Jul ’23

FB12755741

0

Answer 4

Urkman OP

Aug ’23

@Gong Having exactly the same problem. Any news on this?

0

Answer 5

Gong OP

Aug ’23

@Urkman No update and no workaround. I have to create a branch for the CI which using Xcode 15 beta 4...

0

Answer 6

malc OP

Aug ’23

Same problem here, it happens when I try this in my AppIntent:

   @Parameter(title: "Image")
    var file: IntentFile

error: Invalid Swift parseable output message (malformed JSON): `1` (in target 'IntentTest2' from project 'IntentTest2')
error: Invalid Swift parseable output message (malformed JSON): `{
  "kind": "finished",
` (in target 'IntentTest2' from project 'IntentTest2')
  "name": "compile",
  "pid": 64892,
  "process": {
    "real_pid": 64893
  },
  "exit-status": 0
}
Command SwiftCompile emitted errors but did not return a nonzero exit code to indicate failure

0

Answer 7

Gong OP

Aug ’23

Accepted Answer

Xcode 15 beta 6 fixed the issue.

0