Tuist inspect bundle Hanging Indefinitely

Troubleshooting & how to
1

Question or problem

I am trying to set up a Circle workflow that will run “tuist inspect bundle” on a pull request branch. I have the environment set up, and everything goes well until actually running the tuist command. At that point, I’m left seeing “⠙ Analyzing bundle…” in my CircleCi console indefinitely. It never succeeds or fails, and there are no subsequent messages printed to the console.

  1. We have a valid tuist config token set up (already using it for tuist share)
  2. I am able to build an .xcarchive file (using the same method I do with the CircleCi job) and run the tuist command locally just fine.

Expectation

Ideally the command itself works but I realize that I might have an issue on my end. At the very least it would be helpful if there were debug logs that I could turn on for the command, or if it would timeout with some specific error. My problem right now is that I’m really not sure at all what could be going wrong.

Context

  • Tuist version: 4.50.1

Give us some context on what you were trying to do when you stumbled upon the need to create this topic in the community forum.

Reproduction (mandatory for problems)

Set up a CircleCi job
Create an .xcarchive of your app
Setup a TUIST_CONFIG_TOKEN
Attempt to run tuist inspect bundle on the .xcarchive within the Circle environment

2

Hey @rockyev :wave:

Can you confirm that you can successfully inspect the bundle in your local environment? Can you run the tuist inspect bundle command on the CI with the --verbose flag and send the logs over? If the data is sensitive, feel free to send them as a DM either directly here or @ [email protected].

3

Thank you for the response! Just sent you an email :+1:

4

Thanks for sending over the report. Unfortunately, it does not provide a lot more information.

Can you try to run tuist inspect bundle path-to-bundle --json? Does that work?

Additionally, can you SSH into the machine when the analysis gets stuck? I wonder if we’re triggering some access for permissions in which case the machine gets stuck (such as when accessing a locked keychain, however, we should not be doing that).

If you can’t, I might try to set up a CircleCI env of our own to debug.