On the first day after being upgraded to WMS 2026....
# generale
Edward McGuire
04/27/2026, 4:27 PMOn the first day after being upgraded to WMS 2026.1, all our scan guns have whitescreened. EDIT: I checked the mobile login URL, it's the same after the upgrade. On the client side I've taken basic steps like clearing cache, verifying the device can still connect to other URLs. With a different browser (Chromium) I do get a login page. So there is some new incompatibility introduced by WMS 2026.1 with Kiosk Browser, which is the captive browser that runs all the scanguns. I opened a customer support case. Meanwhile I want to make progress to debug this. There are no error messages that point me toward the cause. No certificate error, that sort of thing. Any suggestions?
s
Steven Scheppelman
04/27/2026, 7:31 PMI know you stated you cleared the cache. Have you deleted the cookies?
e
Edward McGuire
04/27/2026, 8:05 PMIf I delete cookies and restarte the device, I get a normal login screen. But after logging in, we are back to the whitescreen.
The first suggestion made by the Kiosk Browser tech was look at the version of WebView on the scangun. Kiosk Browser does not supply the browser engine itself -- it layers on WebView. I looked and I found like many turnkey devices WebView doesn't get updated and is now more than 9 years old.
I'll have to get and install a recent OS image from Zebra to to confirm whether this is the issue, and that's going to take time and be tricky because the guns are within a few months of EOL.
Edward McGuire
04/27/2026, 8:45 PMI have now also reproduced the problem with the Chromium browser on the same devices. Different WebView version but also quite old as it is part of the original OS image that came with the Zebras.
s
Steven Scheppelman
04/27/2026, 8:48 PMTry a new version device. Are there any browser devtool errors?
e
Edward McGuire
04/27/2026, 9:32 PMOn PC Chrome I could quickly answer that. Unfortunately I'm not familiar with dev tools in the Android edition. It appears this is how you do it (https://developer.chrome.com/docs/devtools/remote-debugging/) but that seems to be through standard Android USB tethering. These devices tether through a Zebra charger and Zebra software. I have calls in to our Zebra dealer and yes if we can't quickly reimage our devices I'm afraid we will be buying all new.
Edward McGuire
04/27/2026, 9:34 PMMy other hope is, surely we're not the only Oracle customer that has suddenly lost all scan gun support. Realistically we can't be. So maybe they'll come up with a workaround.
b
Braedon Saunders
04/27/2026, 11:33 PMWhat broke you in 2026.1 isn't WMS itself, it's the SCM Mobile framework updates. They added toggle switches, dynamic labels, conditional mandatory fields. New components pull in modern JS, one unsupported syntax throws during render, and you get exactly your symptom: login works (server-rendered), SPA shell never mounts, no visible error.
😦 1
e
Edward McGuire
04/27/2026, 11:35 PMam I on the right track to get WebView up to date then?
b
Braedon Saunders
04/27/2026, 11:51 PMIf they're on Marshmallow (Android 6), WebView is baked into the system image and you need a full OS update to get past it. If they're on Nougat (Android 7) or later, WebView is a separate APK you can push without a full reimage. Model number and current Android version will tell your dealer which path
e
Edward McGuire
04/27/2026, 11:58 PMit's 7. I can try to load a WebView apk from a microsd card.
b
Braedon Saunders
04/28/2026, 12:05 AMShould work. Grab the arm64-v8a WebView APK from APKMirror. Don't go too new, WebView 90-ish is a safe ceiling for Android 7.
e
Edward McGuire
04/28/2026, 12:14 AMi think there's an Android max version slider in their advanced search. I should be able to pick up the last one supported by Android 7.
Edward McGuire
04/29/2026, 6:45 PMUPDATE: 2FA has been ruled out. I have not identified the root cause yet. I worked around the problem by sideloading Google Chrome. I used the latest general release APK for arm64-v8a, Android 7.0+. So for the time being I am not using Kiosk Browser and my warehouse is back online.
Other workarounds I tried before Google Chrome:
* Chromium. Opening the mobile URL in Chromium made no difference.
* WebView sideload. Kiosk Browser is supposed to find the latest installed WebView and use that as the browser. It is also supposed to update its User Agent string to reflect the WebView it found. After sideloading a newer WebView, the problem persisted, and the User Agent string did not update. So I suppose Kiosk Browser couldn't find the sideloaded WebView.
👍 1
27 Views