Chrome Client Issue on iOS about suma HOT 7 CLOSED

Yikes...could you tell me what version of iOS you are using? We'll try it
out here. Also, could you try going into the iOS preferences and resetting
the Safari cache and databases?

Thanks,
Jason

On Mon, Apr 18, 2016 at 9:46 AM, senyah [email protected] wrote:

I recently set up Suma at my school and assumed that mobile Safari or
Chrome on an iPad would work. However, I ran into problems selecting
initiatives on Safari and a websql issue on Chrome.

After some searching, it looks like Chrome for iOS switched to WKWebView
in version 48 and it doesn't work with Web SQL. The bug report is located
at https://bugs.webkit.org/show_bug.cgi?id=137760. Here is a screenshot
of the error:

[image: chrome error]
https://cloud.githubusercontent.com/assets/18532387/14605866/9c8462ba-0548-11e6-94fd-68428926f8bd.png

Since Safari is the default browser and listed as supported I tried it
next. However, whenever I visit the page and attempt to select an
initiative I only get a drop down menu containing 'Select an initiative'. I
wasn't able to view the other currently enabled option regardless of any
combination of taps or swipes. Here is a screenshot of the empty list:
[image: safari broswer]
https://cloud.githubusercontent.com/assets/18532387/14605865/9c7f6bca-0548-11e6-9113-61d7fc8cc44f.png

Finally, I downloaded the Dolphin browser and the page loaded and
functioned as expected. Here is a screenshot of it working in Dolphin
browser on an iPad:
[image: dolphin browser works]
https://cloud.githubusercontent.com/assets/18532387/14605864/9c783e36-0548-11e6-96ca-7849cf5e3327.png

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#61

from suma.

I edited my initial post just minutes after submitting it because I also encountered the empty initiative selection on Dolphin. Dolphin was a caching issue. I realized that a previous user of Safari set it to open in private browsing so once I disabled it everything started working.

The only issue at this point is Chome, but it's not a show stopper since Safari works when not in private browsing.

from suma.

OK, great. I'll close this for now and keep an eye out on Chrome. Third party browsers on iOS have always been an oddity, since they haven't been able to use their own engines.

from suma.

This issue has reared its head again, and not just with Chrome. I think Apple has done something with its recent updates. The Web SQL error suddenly began showing up with Safari and Chrome (77.3865.103) on iOS (13.1.2) and Safari (13.0.2 )on the desktop (OS 10.14.6). I've tried clearing all app data to no avail.

from suma.

Unfortunately, we just discovered that the iOS browser engine has disabled Web SQL, which is required for the client to function. We're working on writing this up but I'll keep this issue open until then. The two main options:

1. Use an Android device AND Chrome or Firefox instead.
2. Reenable Web SQL in iOS Safari following the instructions at the bottom of this page: https://blog.appstudio.dev/2019/09/the-future-of-sqlite/

We have confirmed at UNC at Chapel Hill that option #2 will work.

from suma.

Looks like Apple finally removed the option that allowed one to reenable WebSQL on Safari in iOS 15.

from suma.

We just released a new version of the client that fixes this issue

from suma.