-
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
unable to build android with react native 0.71.1, got error android:exported needs to be explicitly specified for element
#3867
Comments
Our only Android developer is on his vacation, so we can't help earlier than the next week, sorry. |
I'm keeping this open but we largely expect this to be resolved via #3884. |
I seem to be running into the same issue. I followed the guide from https://wix.github.io/Detox/docs/introduction/project-setup/#step-4-additional-android-configuration What happened?tried to build the android app with detox build --configuration android.emu.debug but got the following errors:
Was it tested on latest Detox?Yes, I have tested this issue on the latest Detox release and it still reproduces. In what environment did this happen?Detox version: 20.1.5 |
I have the same problem. The main project that I am working on, is a react native library. There is a demo app inside this library and I added detox to that demo app. This error (android:exported needs to...) shows a location from the library, which has no activity (or services, etc...) that needs android:exported. If I remove the library dependency, Then the demo app itself has no problem with detox and the build is successful. |
This is caused by Adding this to
|
Another way of solving that is to find out the package activity name causing that and overwriting it in your own AndroidManifest.xml
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
@arcln That's a great find 💪🏻 Please try to see whether this can be removed with Detox |
@arcln ping |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
This is still an issue 20.11.1 edit: I cannot see it stated I the original description, however we had Fabric and the new RN Arch enabled. We disabled it and for us this issue then stopped. |
A workaround for me was to add this to app/build.gradle
|
@krini have you tried the latest Detox version? As I mentioned, this should have been fixed in Detox |
You are right. It seems to work. I did actually update detox to version 20.11.4, but maybe it was in the wrong order. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
reactivating a stale detox installation, i ran into this error. i walked through the setup-guides and checked everything was in place. looks like there were some changes in the meantime:
It compiles given those changes. |
Closing this in favor of more recent upgrades (RN72 in Detox 20.17.0, RN73 in 20.18.1) |
What happened?
setup android test on a react native (version 0.71.1) app following the instructions.
when building the android app regularly, it does not throw this error. ios test works fine as well.
keep getting error:
What was the expected behaviour?
should not throw above error
Was it tested on latest Detox?
Did your test throw out a timeout?
Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.1.2
React Native version: 0.71.1
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version: 18.11.0
Device model:
Android version:
Test-runner (select one): jest
Detox logs
Detox logs
Device logs
Device logs
More data, please!
No response
The text was updated successfully, but these errors were encountered: