This appears to have started when users updated to iPad FSA App 3.8.4
This seems to mainly occur on the WLD Line Qty fields. When users tap into the field, the cursor seems to flash and disappear (so the field is not selected) and the users can't enter any data. Multiple hits are required to activate the field. Some users say it works if they do a long tap.
This is occurring in Production and our Full Sandbox.
Here are some more details.
We have approx 75 users in the US and 4 (out of 40) in the EU that have switched from iPad Classic Last week. We have about 15% of our users reporting problems on 3.8.3 and 3.8.4. (I have a feeling more will report these issues). Here are other SFMs affected, I don't have full details on that.
I was able to replicate this on my iPad and was on iOS 13.4.x. I updated to iOS 13.5.1 and the jumping screens in the WO Debrief appeared to be fixed. The Output Document (Field Service Report) still had the issue where the Technician Signature kept opening a blank field to sign - if I tap cancel, the signature is accepted and I can Finalize the FSR.
I had 4 users update to iOS 13.5.1 on the iPads and this helped resolve the issue in the WO Debrief.
I have not heard back from Support yet.
Unfortunately same issues here (across 100+ users in EU) using FSA if you press into a text field, the keyboard launches and then when you start to type the cursor is no longer in the field you typed in. Meaning you have to tap it once, launch keyboard and then tap again to enter text here.
Regrettably this seems to have re-appeared - when pressing into text fields on the GO iPad app 1.7, I am trying to get a recording of this behavior. The cursor in a text fields jumps back and forth and the user results in typing a load of random letters. This has been noticed when filling in custom fields on child records to the work order object.
@archana_krishna yes, this is with iOS 14.3 and was raised as a case, and was deemed a known defect (Case: 00095783). It is scheduled for fix in the next GO release at end-Feb. As for FSA, it did happen in FSA and then was repaired, I was just suggesting it was the same issue that was previously identified. We no longer use FSA so I cannot advise if this is present still on this app. Hope this helps?
@archana_krishna did you check this support case and related defect, I am told it will be fixed at the release at the end of Feb - can you confirm, it's really irritating as a problem. Makes completing work orders really difficult? Thanks!
While this issue was addressed in FSA iPad, this started happening in Go iOS apps.
This issue will be fixed in Go iOS version 1.7.2, scheduled for end of Feb '21.