Jotform Cards: fields are filled but getting Require Field error on mobile devices

  • Profile Image
    onerudyburger
    Asked on December 21, 2017 at 04:26 PM

    I have a form with 42 conditions and they all work beautifully on a desktop. When I check it on my phone, even though i fill all the questions in, Field 22 "What Airline?" field still reports "required field".

    To get to that, you have to choose "Return Trip?".

     

    Phone only.

     

    I may have conflicting conditions hiding somewhere...

    The form is Lake Oconee Transportation Quick Pay

     

    Thanks

  • Profile Image
    onerudyburger
    Answered on December 21, 2017 at 04:28 PM
  • Profile Image
    John_Benson
    Answered on December 21, 2017 at 07:51 PM

    I did test your form on a desktop computer and it is working properly. Upon testing it on my mobile phone, I was able to replicate the issue. The "What Airline" field is already filled out and I was still not able to click the Next button.

    151390371353353az.png

    Is this the issue you're encountering when using a mobile phone? Please confirm so we will forward it to our developers immediately.

    We'll wait for your reply. Thank you.

  • Profile Image
    onerudyburger
    Answered on December 22, 2017 at 08:38 AM

    Yes it is a mobile phone. Android OS.

    Thank you.

    p.s. you need to charge your phone.

  • Profile Image
    TREVON
    Answered on December 22, 2017 at 09:11 AM

    Thank you for your confirmation and apologies for any inconveniences caused. I have escalated the issue to our Level 2 support team for further investigation and resolution. We will update you on this thread once the issue is resolved.


  • Profile Image
    onerudyburger
    Answered on December 23, 2017 at 07:54 AM

    no answer yet?

  • Profile Image
    Ardian_L
    Answered on December 23, 2017 at 08:08 AM

    We are sorry for any inconvenience caused. We are still waiting for an answer from our developers. You will be notified on this thread soon.

    Thank you!


  • Profile Image
    onerudyburger
    Answered on December 26, 2017 at 01:02 PM

    HOW CAN WE EXPEDITE THIS? MY CLIENT HAS CALLED TO TELL ME THAT 3 CUSTOMERS ATTEMPTED TO BOOK ONLINE WITH THEIR PHONE AND COULD NOT. I HAD TO DO A QUICK FIX AND UNREQUIRE "WHAT AIRLINE?". THIS IS NOT THE FIX I NEED. 


    I NEED THIS FIXED AND YOU GUYS HAVE HAD SEVERAL DAYS TO RESOLVE THE ISSUE.

  • Profile Image
    Nik_C
    Answered on December 26, 2017 at 01:46 PM

    We're sorry for the inconvenience and delay. The issue is still being worked on.

    I tested your form now, from Android phone, but I wasn't able to replicate this issue anymore, I was redirected to PayPal upon submitting.

    I tested on Chrome on Android 5.

    Are you still able to replicate this issue on your phone?

  • Profile Image
    onerudyburger
    Answered on December 26, 2017 at 01:51 PM

    Please read the WHOLE prior email and you will see:

    HOW CAN WE EXPEDITE THIS? MY CLIENT HAS CALLED TO TELL ME THAT 3 CUSTOMERS ATTEMPTED TO BOOK ONLINE WITH THEIR PHONE AND COULD NOT. I HAD TO DO A QUICK FIX AND UNREQUIRE "WHAT AIRLINE?". THIS IS NOT THE FIX I NEED. 


  • Profile Image
    Ardian_L
    Answered on December 26, 2017 at 02:15 PM

    We are sorry for any inconvenience caused. I cloned your form and made the "What Airline" field required and I was able to submit with no problem. My device is running on Android 7.1.1 

    We are waiting for an answer from our developers and you will be notified as soon as possible. Meanwhile can you please try to clear the cache of your form.


    Hoping in your understanding. Thank you!

  • Profile Image
    onerudyburger
    Answered on December 26, 2017 at 03:04 PM

    Thanks. Clearing Cache did the trick.


  • Profile Image
    Ardian_L
    Answered on December 26, 2017 at 03:06 PM

    I am glad that you figure it out. And we are sorry for any inconvenience caused. Please let us know if you have any other question.

  • Profile Image
    berkay
    Answered on December 27, 2017 at 06:46 AM

    Hey


    it looks this issue is fixed.


    Thanks.