Bitrise Build Issue Report template
Description of the issue
I’m not able to test my iOS app using detox.
The same exact config works fine locally using bitrise-cli but it fails on CI.
Environment:
Where did the issue happen?
Bitrise.io using latest detox & react native.
Which build Step causes the issue and which version of the step?
detox build --configuration ios.sim.release
detox test --configuration ios.sim.release --cleanup
Reproducibility
- Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
-
Does a rebuild without caches help? (You can remove the
Cache:PullandCache:Pushsteps temporarily to not to use the cache, or you can delete all the caches on theSettingstab of the app. : NO - Does the issue happen sporadically, or every time? : Every time
- Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : Since the beginning
Local reproduction
Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.
Can’t reproduce locally
Local reproduction: Linux / Android (docker based) stack builds
Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Redirecting… .
No, the tests run locally fine using bitrise-cli.
Build log
Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - Contact us ), with a link to the related Discuss issue.
