Body
This service is for faculty, staff, and students.
Why would this be happening?
(I don't want an explanation just help me fix it)
Many university and organizational apps on Android rely on a built‑in system component called Android System WebView to load their login pages inside the app. WebView is essentially a mini version of Chrome that lives inside your phone and quietly handles sign‑ins, redirects, and web content without opening a full browser.
Most of the time WebView works behind the scenes and you never notice it. But if it becomes outdated, blocked, or restricted by certain device settings, the login page inside the app may stop working even though the rest of the app seems fine. Because every Android device is slightly different (Samsung, Pixel, Motorola, work‑managed devices, etc.), WebView issues can show up in different ways depending on the phone.
Common problems include WebView not saving cookies, failing to run JavaScript, getting shut down by battery optimization, being interfered with by VPN or private DNS settings, or not updating properly after a system upgrade. When any of these occur, login pages may freeze, go blank, loop endlessly, or show errors like “This browser or app may not be secure.”
To help you identify and fix the issue on your specific device, the troubleshooting section below walks through the most frequent WebView‑related causes and the steps you can take to resolve them.
Before you get started:
We hope these troubleshooting steps help you resolve the issue. However, Android devices vary widely between manufacturers, models, Android versions, and configuration profiles, so we can’t guarantee that every step will appear exactly the same on every device or that these steps will fix the issue in every situation.
Please use your best judgment when changing settings. Troubleshooting is done at your own risk, and any adjustments you make to your device may carry the possibility of unexpected behavior or data loss. Unfortunately, we cannot be responsible for any issues that occur as a result of following these recommendations.
Troubleshooting
(Listed in order from most likely to fix to least likely)
Fully reboot the device - At any or all stages of troubleshooting
- Power the device all the way off, wait 30 seconds, and power it back on
- Simple but surprisingly effective if it's been a while or if WebView has updated recently.
- Then retry logging into the app.
Manually update WebView
- Open Google Play Store
- Search for Android System WebView
- Tap Update
- Also update Google Chrome (WebView depends on it)
- Then retry logging into the app.
Clear WebView and Chrome cache - Corrupted WebView cache breaks redirect flows
- Go to Settings → Apps
- Tap Android System WebView
- Storage → Clear Cache
- Repeat for Google Chrome
- Then retry logging into the app.
Just clear the cache, Do not clear data unless you are comfortable losing your saved browser auto fill info and passwords
Ensure Chrome is enabled - Some users disable Chrome without realizing it and if Chrome is disabled, WebView breaks
- Settings → Apps
- Chrome → Enable (if disabled)
- Then retry logging into the app.
Check your device for Private DNS, VPNs, or ad blockers - These silently cancel redirects
- Temporarily disable:
- Private DNS
- VPN apps
- Ad blockers (AdGuard, Blokada, DuckDuckGo App Tracking Protection)
- Samsung Secure Wi Fi
- Carrier provided “security” apps
- Then retry logging into the app.
Disable any “Open links in apps” restrictions for the problematic app - If opening links in apps is turned off, redirects can fail
- Settings → Apps → Default Apps
- Opening links → Ensure it’s Allowed/On
- Scroll to the affected app → Ensure it’s Allowed/On for "open supported links"
- Then retry logging into the app.
Check battery optimization - Aggressive battery management ends WebView mid redirect (Samsung, Pixel, Motorola)
- Settings → Apps → [App Name]
- Battery → Unrestricted or Not optimized
- Then retry logging into the app.
Clear the affected app’s cache - Not data, just cache
- Settings → Apps → [App Name]
- Storage → Clear Cache
- Then retry logging into the app.
Try the login in Chrome directly - This can help determine whether the issue is WebView or the app.
- Open Chrome
- Go to the university Canvas login page https://stthomas.instructure.com/
- Try signing in
If Chrome fails too then it’s definitely WebView or device configuration.
Is there a Work Profile/MDM profile on your device?
- If you have:
- a work profile
- Microsoft Intune
- Google Work Profile
- Samsung Knox
- These can block necessary WebView redirects
Are you sure the app is installed in the personal profile, not the work profile.
Uninstall/reinstall the app
- This (hopefully) forces the app to rebuild its WebView container.
Reset all browser settings - Nuclear option (rarely needed)
Over time you may have ended up with heavily modified Chrome settings that are affecting your ability to complete app authentication
- Chrome → Settings → Privacy → Clear browsing data → Cached images/files
Or
- Chrome → Settings → Site settings → Reset all permissions
return to the top
To report a problem or receive additional troubleshooting, please contact the Tech Desk.