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

iOS react-navigation v5 issue #13940

Closed
nickmccomb opened this issue Feb 14, 2020 · 6 comments
Closed

iOS react-navigation v5 issue #13940

nickmccomb opened this issue Feb 14, 2020 · 6 comments
Labels
Needs Info typically non-actionable; needs author to respond ThirdParty upstream problems XCUITest regarding xcuitest driver

Comments

@nickmccomb
Copy link

The problem

Appium is not navigating on iOS. We are using react-navigation v5. Appium presses the button, which Appium says is successful, although the app does not navigate to the next screen (it does when manually testing, so the navigation is hooked up and working correctly). Appium navigates correctly on Android, just not iOS. I'm hoping someone else has had this issue and has found a way to solve it.

Environment

Node: v13.7.0
React Native: 0.61.5
appiumVersion: '1.16.0' (tried many previous versions too)

Link to Appium logs

https://gist.github.com/nickmccomb/aea239307a2e6b2f372e1a76b1961891

Code To Reproduce Issue [ Good To Have ]

    <Button
        accessibilityLabel={'submit button'}
        accessible={true}
        onSubmitEditing={() => submit()}
        title="Submit"
        onPress={() => navigation.navigate(Texts.screens.Home)}
    />
@mykola-mokhnach
Copy link
Collaborator

Possible duplicate of #13907

@mykola-mokhnach mykola-mokhnach added ThirdParty upstream problems XCUITest regarding xcuitest driver labels Feb 14, 2020
@mykola-mokhnach
Copy link
Collaborator

As a workaround one could also try to tap by coordinates. It might be that not the whole element's area is responsive to touches, so the actual hit point, which xctest calculates for the element is not a valid one.

@imurchie
Copy link
Contributor

@nickmccomb Please try the latest Appium beta. There has been a fix for text input which might affect the functionality here.

@mykola-mokhnach mykola-mokhnach added the Needs Info typically non-actionable; needs author to respond label Feb 25, 2020
@mykola-mokhnach
Copy link
Collaborator

Closed because of no response

@kirillzyusko
Copy link

@nickmccomb Hi! Did you find a solution?

@phillipkey
Copy link

phillipkey commented Oct 20, 2020

This issue should be repoened. It is still reproducible as of October 20 on the latest release of appium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Info typically non-actionable; needs author to respond ThirdParty upstream problems XCUITest regarding xcuitest driver
Projects
None yet
Development

No branches or pull requests

5 participants