Skip to content
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

"resource-id" or "content-desc" for react native apps on Android not populating #16748

Closed
sasasa42 opened this issue Nov 8, 2017 · 5 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@sasasa42
Copy link

sasasa42 commented Nov 8, 2017

Expected Behavior

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.

@react-native-bot
Copy link
Collaborator

@facebook-github-bot no-template

@facebook-github-bot
Copy link
Contributor

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 ContributeWhat to Expect from Maintainers

@facebook-github-bot facebook-github-bot added the Ran Commands One of our bots successfully processed a command. label Nov 8, 2017
@bhgames
Copy link

bhgames commented Jan 22, 2018

I also experience this issue, but when building for debug they are there, and for release, they are not.

@jnrepo
Copy link

jnrepo commented Feb 22, 2018

I believe this is needed for functional testing...

@bhgames
Copy link

bhgames commented 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).

@facebook facebook locked as resolved and limited conversation to collaborators Nov 8, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Nov 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants