Hi, Clare

Can you tell me, all the clients that are reporting this issue-

is it happening only to people who have iPhones, and use autoFill for the phone number field?

If that is the case, we have this flagged as a bug, and our developers are working intensively to fix it, but unfortunately no luck yet.

I will get a colleague who has an iPhone to test this at Monday for us, to be sure;

But i fear that i know what the issue is.

If you have someone with an iPhone to test this for you before Monday, you can do that to be sure;

For example, all they have to do is try to go to any booking;   and autoFill the phone number field;  if the PayPal can't load, just keeps spinning,  it is the issue i am talking about;

It should look like this, the first screenshot of a phone number autoFilled by iPhone :

And then if they see it spinning like this :

-

If you test this, then you can manually type in any phone number, and in this case the issue should not happen.

But it seems it is working on desktop, and Android devices, as i tested it...

Let me know if you confirm it from your end, i will keep a lookout for your response - 

and if you don't do it by Monday, i will then report back when i get a colleague with iPhone to test it.

Thank you

Hi, Clare

I just forgot to add - if we confirm it is the same issue;  at this time the only emergency measure is to disable the autoFill on the user's device or browser, or to manually type in the phone number field - as that is the only field causing the issue.

Just wanted to add this, and we will still report back - let me know how it goes if you test from your end. Thank you

Hi, Clare

Sorry for the delay, thank you for confirming it is the issue.

-

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.

Hi, Clare 

Unfortunately, we don't have an ETA when or if this will be resolved,

since we discovered that this issue has already been around for a long time for iPhones, and so far it is not possible to resolve. As you can see on one of the posts from StackOverflow - https://stackoverflow.com/questions/22661977/disabling-safari-autofill-on-usernames-and-passwords

- since disabling autoFill for the pages with the booking has that issue that is coming from Safari,

and they seem to not show signs that they intend to resolve it, for the moment

;

But our developers will keep working on it intensively and do everything they can,

as we realise that the issue is hurting businesses;

so i can assure you it is on absolutely highest priority with us.

We will certainly closely follow how it progresses, and if the devs somehow find a way to resolve it at any moment,  

i will make sure to notify you immediately.

Truly sorry for all the inconvenience caused by the said issue.

Hello Clare

I am sorry to hear you're not satisfied with Amelia, but there's been a misunderstanding between Milos and you.

The issue's been around for a long time for iPhones. The link he provided was from Stack Overflow, which has absolutely nothing to do with Amelia, and it's related to autofill option which cannot be turned off in Safari because Apple chooses not to follow other browsers' standards.

Our developers are actively looking for a solution with the autofill issue, but it will take some time since, as you can see in the link Milos shared, it's been around for a while, and web developers are battling this issue for quite some time.

If you'd like to give us a few more weeks to troubleshoot this further, we'd be more than grateful. If we're not able to resolve the issue we'll check with our management if we can refund your last charge. Refunds usually don't apply to upgrades or renewals, but we can understand where you're coming from and hopefully we'll be able to arrange something.

Please let us know.

I understand where you're coming from, Clare and even though the issue you're facing is not caused by Amelia, but by the functionalities of the Safari browser, our management agreed to issue a full refund for the charge made on June 15th, 2022 since you're not able to properly use our plugin due to this issue.

You will receive your money within a few business days, and your license will be terminated immediately.

If there's anything else we can help you with, please let us know.