Sitefinity 5.1 login issue with Mobile Safari

Development has recently completed on a site built on Sitefinity 5.1 and has launched, but users with iPads trying to login via Mobile Safari cannot. Testing this myself, trying to login shows red text with "error:" and then the page refreshes.

Logging in via Chrome or Dolphin does work, but Mobile Safari fails. If logging in via the Sitefinity Admin page, then this does work in Mobile Safari, but is not the desired flow.

Is there any known bug or configuration that the login widget would need to fix this problem?

Were you able to find an answer to this?  We are also getting these errors...sometimes clearing cache and/or updating iOS fixed the issue, but I would like a clearer answer.  Thanks!

The problem seemed to arise if the user had logged-in on another device and did not logout before attempting to login on their iPad. The solution that we found was to completely close Safari and then delete cookies. After this, the user was able to login on the iPad without any error.

We initially tried to simply logout on the original machine and then try to login on the iPad, but that resulted in the error. There seems to be a problem with handling cookies and server-side authentication, but I can't really say for sure.

Being the first Sitefinity project, I can definitely say that it is a challenging platform and has a high learning curve.

Hello Bryan,

Can you please confirm if you are using iOS5 on the devices you've experienced the issues with?

Further investigation on the issue has confirmed that there are problems in the Safari browser version used in iOS5, that conflict with the default ASP.NET <a href="#" onclick="return false"> approach for rendering clickable hyperlink. More information on the topic can be found on this discussion at StackOverflow.

We have verified that the behavior is working correctly in newer and older versions of the iOS software(4 and 6), so we would strongly recommend upgrading the iOS version of the devices to the latest officially supported one to benefit from their bugfix for the issue.
As an alternative you can try adapting the behavior of the hyperlink, using jQuery and setting the onclick attribute, as specified int he above mentioned thread. The fastest way to achieve this would be by placing a JavaScript widget on the page or template where your public login control is placed, and write:

$('.sfSubmitBtn').attr('onclick', 'event.preventDefault(); return false;')