Can't focus on input

đź’¬ Mobile
1
  1. My goal: We have a multistep app on mobile which we use for data capture. We are not using a multi page app. It’s all one page. We’re using a segmented control and containers which are hidden/revealed based on the step in the capture process. In one of our steps, we scan a barcode (the mobile app is run on an Android scanner), when we arrive on this step we want to clear the barcode input (in case the user is jumping around) and focus on the input.
  2. Issue: The problem we’re encountering is that this works the first time when we focus the barcode input. The second time however causes the input to become completely broken. It clears but isn’t focused and tapping on it manually does not focus it. It comes across as permanently disabled (without visually being disabled). It’s worth noting that this works flawlessly on the web editor and iOS. It’s only on the actual mobile app on Android that it’s an issue.
  3. Steps I've taken to troubleshoot: I’ve tried playing around with delaying the focus, delaying the clearing, not clearing it, not focusing it, not disabling it. Nothing works, it appears to be a bug with the underlying android app.
  4. Additional info: Cloud.
  5. We suffix icon to clear and focus the input, this doesn’t work either, until we’ve waited about 2 seconds, then we can use the suffix icon. Tapping the input normally doesn’t work until we’ve used the suffix icon.

Any help here would be greatly appreciated.

3

Hi, we are experiencing the exact same issue, once a TextInput is disabled it can not get dis-disabled anymore. Neither changing the input in the “disabled” field, nor using setDisabled will change it.

It completely breaks the way we need to use the input, so some bugfix would be very appreciated.

Version: 3.284.3 (self-hosted)

4

Hi @Kevin2 and @flaschenpost-wha,

Apologies for the inconvenience, this is a known bug which we have an open engineering ticket for.

It does seem to only affect mobile apps on android, that you for the detailed write up and I will add +1s to that ticket for you both.

5

Also just to clarify @Kevin2,

In the case where you do NOT focus the input field, you go through the steps and complete all the user steps. Then when the app is set back to the first step, as it passes to the input field step the second go around is when the input field is disabled. Correct? Even with refreshing or reloading the mobile app?