Is it best practice to have separate builds without detox or can detox builds be shipped to the app stores?

[nicolls1]

I haven't been able to find any docs on this and am curious what is considered best practice. I could see it going both ways where it would be ideal to have the bundle that gets sent to the app stores is the bundle that has had end to end test run on it, but at the same time it probably doesn't make sense to have the extras detox adds in the final build.

Appreciate any thoughts!

[MuckT]

@nicolls1 to my knowledge you should not submit your detox build as you've likely enabled cleartext traffic for your Android Builds.

When your app communicates with servers using cleartext network traffic, such as HTTP, the traffic risks being eavesdropped upon and tampered with by third parties. This may leak information about your users and open your app up to injection of unauthorized content or exploits: source.

[noomorph]

Overall, I'd recommend using debug builds where possible for Detox testing – it requires more effort with fighting your console.warn and console.error (although it is possible to turn off the LogBox anyway), but it is just easier to understand why tests don't work, and many instrumentation/tooling features just work better.