ProgressNS / sidekick-feedback

This repository is for feedback regarding NativeScript Sidekick. Use the issues system here to submit feature requests or vote for existing ones.
45 stars 9 forks source link

Create a Guide for Recovery from "Spawn failed. , Error: Spawn failed." #441

Open EdJones opened 4 years ago

EdJones commented 4 years ago

Please, provide the details below:

Sidekick publish to Apple often ends with the unhelpfully terse message :

Spawn failed.
, Error: Spawn failed. 

Together we can examine the hidden logs, as well as attempted solutions, and produce a guide that allows developers to check potential causes and attempt potential solutions.

Did you verify whether this issue has already been reported here?

Yes/No Yes

Tell us about the problem

Give us a concise description of the feature you suggest or the issue you report. Add a guide that allows developers to get past this issue.

Which platform(s) does the issue occur on?

iOS/Android/Both (if applicable, tell us the specific version of the platform)
Windows/macOS/Linux/Multiple (if applicable, tell us the specific version of the platform) Probably Windows/MacOS/Linux. (I'm on Windows)

Provide the following version numbers that the issue occurs with:

How to obtain this information is explained in the Gather information about your development environment section.

Tell us how to recreate the issue in as much detail as possible

  1. Start the application ..
  2. ...Click "publish" for a working app.
  3. Await build and download processes to complete without error.
  4. Await for Sidekick to request Apple developer credentials
    Starting Cloud publish iOS. Cloud operation id: d89a9d8e-890d-40e6-94c2-fc995121a63b
    [19-11-15 07:47:35.918] (CLI) Starting publishing.
    [19-11-15 07:47:42.028] (CLI) Build machine host name: administrators-Mac-18.local
  5. Upload fails with "Spawn error", e.g.
    [19-11-15 07:48:31.634] Spawn failed.
    , Error: Spawn failed.
    at CloudPublishService.getiOSError (C:\Users\ed_000\AppData\Roaming\.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:79:21)
    at CloudPublishService.<anonymous> (C:\Users\ed_000\AppData\Roaming\.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:96:29)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\ed_000\AppData\Roaming\.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:4:58)

    Does this issue happen every time?

    Yes/No Varies

    Send the client logs

    How to obtain the Sidekick logs is explained in the Access the NativeScript Sidekick logs section. To share them with us, you can create a gist with the app logs and send the produced link. Errors may vary. My latest said

    [19-11-15 07:47:48.984] (Info) ab.publish.shell.inputRequested - {"type":"inputRequest","cloudOperationId":"d89a9d8e-890d-40e6-94c2-fc995121a63b","body":{"inputType":"text","inputRequestId":"bdd4134f-7e60-41ee-b8e9-8922a6ecf55a","message":"Please enter the 6 digit code: "}}
    [19-11-15 07:48:28.236] (Info) ab.publish.ui.sendCloudMessage - {"requestData":{"body":{"inputRequestId":"bdd4134f-7e60-41ee-b8e9-8922a6ecf55a","inputType":"text","message":"Please enter the 6 digit code: "},"cloudOperationId":"d89a9d8e-890d-40e6-94c2-fc995121a63b","type":"inputRequest"},"response":"224955"}
    [19-11-15 07:48:28.576] (Info) ab.publish.shell.sendCloudMessage - No value provided
    [19-11-15 07:48:31.634] (Error) ab.publish.shell.publishToItunesConnect - Spawn failed.
    , Error: Spawn failed.
NickIliev commented 4 years ago

@EdJones it seems that you are hitting a bug related to a changed API on iOS (related to this comment).

I will post as soon as we have a stable fix (which will be published in a new version of Sidekick)

prabh08 commented 4 years ago

@NickIliev I am also getting same issue. Please help asap.

EdJones commented 4 years ago

@EdJones it seems that you are hitting a bug related to a changed API on iOS (related to this comment).

I will post as soon as we have a stable fix (which will be published in a new version of Sidekick)

@NickIliev, it may be that's my issue this time. But either way, the "Spawn failed" error is cryptic, and more info can sometimes be gleaned from the logs hidden under Sidekick's Help menu. I've seen enough people ask to think a guide would be appreciated.

NitBlockchain commented 4 years ago

any fix for this?

asharghi commented 4 years ago

Bump

Edit: My workaround was to build with tns prepare ios --release. Opened the appname.xcworkspace (located in the platforms/ios folder) in xcode and from there Product>Archive and "Distribute App". If something goes wrong it will give you a much more detailed error message.