-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow absolute app path #98
Comments
Hi @chirag04, Although not technically hard to implement this feature, I am not in favor of adding absolute paths in configuration (of any kind) for the following reasons:
|
CI builds run in containers so they don't override each others artifacts. what i'm saying is that the artifact directory may not always be inside the project work directory. eg: build 1: artifact directory: build 2: will essentially have the same path just that he container-id changes above. Anyway, i think the bigger point here is that it's not always necessary that ipa path will be inside the project directory. it would be nice to support that. |
@rotemmiz I think this has been resolved. Right? |
No, we don't support absolute paths. I'm still not convinced it's needed, but PRs for a non breaking support are welcome |
What happens if I provide an absolute path in |
My CI environment on Bitrise is dumping my archive in an absolute path outside of my project folder. I'll work around it by adding a copy step for now. |
bitrise is exactly the reason why i opened this issue. |
Hey guys, If this is something you want to take forward a PR would be appreciated. We are unable to put time into this currently. |
Done |
Right now the detox config in package.json expect the app path to be relative to the current project dir. This is not always true especially in CI environments. Locally, xcode default to
/Library/....
which can be overridden but it would be nice to support absolute paths.The text was updated successfully, but these errors were encountered: