Detox: typeText fails on iOS with Detox `13.3.1`

Describe the bug ✅typeText succeeds with Detox 13.1.1, 13.2.0 (old) ⚠️typeText fails with Detox 13.3.1 (new)

To Reproduce

I have tested this issue on the latest Detox release and it still reproduces

Provide the steps necessary to reproduce the issue. If you are seeing a regression, try to provide the last known version where the issue did not reproduce.

const emailTextBox = element(by.text('Email Address'));
await emailTextBox.typeText(emailAddress);

This is a regression. 13.2.0 worked fine 13.3.0 and 13.3.1 do not work.

If possible, please provide a small demo project that reproduces the issue, or attach a video with the reproduction - this would be very appreciated.

Expected behavior It should simulate typing into text box.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Detox: 13.3.1
React Native: 0.59.10
Node: 10.16.0
Device: MacBook Pro -- iPad 6th Generation Simulator
Xcode: 10.3 (10G8)
iOS: 12.4
macOS: Mojave 10.14.6 (18G84)

Device and Verbose Detox Logs detox test --loglevel trace: e2e.log

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 31 (15 by maintainers)

Most upvoted comments

We have a plan to replace the entire matching and action infrastructure for Detox on iOS. I will see what can be done there. Closing for now.

LeoNatan on Sep 24, 2019

I changed the entire typing mechanism to an internal one, instead of what we used in the past, which was Earl Grey based, and had many issues. The new system is supposed to be more robust, but that also means that it is more general in design. Again, if you have ideas how to solve the issues I’ve brought up before, let’s discuss. This is why the issue remains open.

LeoNatan on Aug 25, 2019

Thanks @LeoNatan for the quick turnaround and in-depth explanations. I understand if you don’t want to support the scenario given the hairiness of the implementation details. My team will proceed with the by.id guidance until we hear otherwise.

PaulMest on Aug 12, 2019

@ayelenmarie I think your issue is different than the one discussed in this thread originally, but due to lazy error reporting in the code, got lumped in the same category. Please see if 14.0.2 solved your issue.

LeoNatan on Aug 12, 2019

Detox 14.0.2 is out with the proposed changes. Please try it out and let me know if something improves, or post the new error output. Thanks

@PaulMest @ayelenmarie

LeoNatan on Aug 12, 2019

There is a PR open with improvements to typing. Let’s see if it helps in these cases. Even if not, it will provide better error messages.

In the case of a placeholder, I don’t think it will be supported. When you select the placeholder view, it’s a label, not the enclosing text field, and so you cannot type in there.

Let’s wait for the PR to see.

LeoNatan on Aug 9, 2019

I don’t see why it should not be supported. I’ll try to reproduce your use case and see.

Using by.id() is always recommended because it’s the most precise.

LeoNatan on Jul 31, 2019

@muraliseveneleven Yes. Same error.

    Error Trace: [
      {
        "Description":  "Reason for action failure was not provided.",
        "Error Domain":  "com.google.earlgrey.ElementInteractionErrorDomain",
        "Error Code":  "2",
        "File Name":  "GREYElementInteraction.m",
        "Function Name":  "-[GREYElementInteraction performAction:error:]_block_invoke",
        "Line":  "268"
      }
    ]

My work around was to add a testID and use the by.id matcher. But I don’t want to have to do that to all of my components.

PaulMest on Jul 30, 2019