-
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
assembleRelease isn't using metro exts replacements (mocks) #1557
Comments
We use the issue tracker exclusively for bug reports and feature requests. This issue appears to be a general usage or support question. Instead, please ask a question on Stack Overflow with the Feel free to post your Stack Overflow question here for more visility. We'll take a look at it. For more information on bots in this reporsitory, read this discussion. |
This comment has been minimized.
This comment has been minimized.
It actually the bot did its job as expected. This is a usage question and we are asking that those be posted on Stack Overflow. Instead of posting meme spam, ask your question there and link it here. |
I'm trying really hard to make my tests run on the release version of my apk, but the
assembleRelease
task seems to be ignoring any exts I've added tometro.config.js
, even through thesourceExts
get is called at some point, it is being ignored, here's my conf:And here is my build definition
assembleDebug
works fine, and uses the exts defined by my env vars, butassembleRelease
ignore them.I know this is not a direct detox issue, but at the advanced mock docs there's a example pointing to use the
assembleRelease
without any warning, it would be nice to have some note on this issue (also, there are a lot of issues on stackoverflow and here not answered/solved about it)Note: the reason why I'm trying to use the release version is cuz the debug version is slow on tests (typing is really slow, i suspect that it's cuz there's the RN ws looking for the metro server and making the event loop occupied every X seconds during the tests)
The text was updated successfully, but these errors were encountered: