You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"resource-id" or "content-desc" for react native apps on Android not populating #16748
I must be able to be able to view the resource-id and content-desc attributes for Android when inspecting
Actual Behavior
No resource-id and content-desc attributes are populated
I already referred the other issues related to this, but finally nothing works for me. Please suggest a solution, as I am not able to proceed with the testing.
Reproducible Demo
I have a react native app to inspect the elements using Appium/UIAutomatorViewer.
For iOS, I could find that by having the elements with "accessibilityLabel" or "testID" solves the problem. But for Android, it seems that there is no solution at all. I tried with various combination of the "accessibilityLabel" or "testID". Nothing finally worked out.
Hey @sasasa42, thanks for posting this! It looks like your issue is missing some required information. Can you please add all the details specified in the Issue Template? This is necessary for people to be able to understand and reproduce your issue. I am going to close this, but please feel free to open a new issue with the additional information provided. Thanks!
Yeah this turned out for me to be because CodePush was pulling my un-labeled elements and old code from the Staging deployment, not running my newer code on my own local machine which had these tags(and which debug used just fine since it's programmed to not use CodePush).
Activity
react-native-bot commentedon Nov 8, 2017
@facebook-github-bot no-template
facebook-github-bot commentedon Nov 8, 2017
Hey @sasasa42, thanks for posting this! It looks like your issue is missing some required information. Can you please add all the details specified in the Issue Template? This is necessary for people to be able to understand and reproduce your issue. I am going to close this, but please feel free to open a new issue with the additional information provided. Thanks!
How to Contribute • What to Expect from Maintainers
bhgames commentedon Jan 22, 2018
I also experience this issue, but when building for debug they are there, and for release, they are not.
jnrepo commentedon Feb 22, 2018
I believe this is needed for functional testing...
bhgames commentedon Feb 22, 2018
Yeah this turned out for me to be because CodePush was pulling my un-labeled elements and old code from the Staging deployment, not running my newer code on my own local machine which had these tags(and which debug used just fine since it's programmed to not use CodePush).