Hi, Isabel

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

Since you are not able to replicate this, from your end it works, right?

This is indicating it might be an issue that we are facing for some time now - our developers are working on it, but it is still an ongoing issue.

-

Can you check , if all of the customers that can replicate the issue - if they use iPhone, and if they use autoComplete for the phone field?

If possible, see if someone with an iPhone can try to manually enter the phone field ( in that case it should not have issues)- and compare it when they use autoComplete on the phone field - it is the issue i am talking about.

If you can please confirm if that is the case. Thank you

Hi, Isabel 

Sorry about that, i know what you mean.

I just did tests on my Android phone, and on my desktop  . Both are loading PayPal without issues,

so i believe it is most probably the iPhone autoComplete of the phone number field issue...

I will get colleagues who have iPhones to test just to confirm, but i am already 90 percent sure, to be honest...

I will report back just to confirm it, and i will explain what the developers did so far.

At this time, the only solution is to disable autoFill on the device / browser when customers book with iPhones;

as i mentioned, for email, and all other booking fields it is OK to use autoFill, but just for phone number field with iPhones, there is the issue...

I will come back when i confirm it is the issue i am fearing. We will be as quick as possible.

Hi, Isabel

Colleagues did tests with iPhone - 

unfortunately, i can confirm it is the issue i feared.

When an autoFill is used on a phone field using iPhone, the PayPal does not load, it just spins infinitely, while for other fields it works without issues.

And if we use any other device, it is working.

I am sending an attachment video of how it is working from my desktop ( same as on Android devices);

so you can see what i mean...

-

I have escalated this to our developers and QA testers, to see if they can think of anything that they haven't already tried to fix it at this time.

For the time being, the only "emergency temporary solution" can be for iPhone users to disable autoFill, to avoid this bug.

I will report back immediately as soon as they investigate it further, and will keep you posted on any new information i can get.

Hi, Isabel 

-

We got the feedback from our colleagues and they say that have attempted every possible workaround that we could find, but unfortunately, we were not able to resolve this issue. We used "autocomplete="off"" and we've even added it to be considered a "new-password" so the browser doesn't see it as a phone field, but that failed as well. 

As you can see here (https://stackoverflow.com/questions/22661977/disabling-safari-autofill-on-usernames-and-passwords) this issue has been around for a long time, and Safari doesn't intend to resolve it (so it seems). Our developers explored stack overflow, Apple's forums, GitHub, etc. - all places where possible solutions could be found, and even though some people reported that it sometimes works, in most cases (like in yours) it doesn't. 

As mentioned in Stack Overflow: "The reason browsers are ignoring autocomplete=off is because there have been some web-sites that tried to disable auto-completing of passwords" and we can't get around that. The only solution, for the time being, is to disable the autocomplete feature in the browser and in phone settings. 

Our lead developer will be working on resolving the issue related to PayPal not opening when iPhone's autofill is used, but that will take some time. We're determined to resolve this issue, and we thank you for going through extensive testing, so we could replicate the behavior on our end as well but unfortunately, we're not yet able to successfully resolve the matter. 

We hope the fix will be included in one of our upcoming updates, and want to assure you that our developers are on this task.

-

We will certainly add a note on the changeLog page, when it is fixed; 

If you wish,  you can check it during each update - and when it's finished we will add a note as a bug fix.

We will do our best to fix it as soon as possible.

Thank you again for all your patience and cooperation on the issue.