Hi there, our web app (used for scanning) is designed to run as a PWA ("progressive web app") via Chrome. However, when we run it as such on our Zebra TC52, it does NOT autoplay sound until the user interacts with the page.
One of the key benefits of running a web app as a PWA is that autoplay with sound is allowed even without user interaction (see https://developer.chrome.com/blog/autoplay, specifically "Autoplay with sound is allowed if..."). This is crucial for us since we rely on audio cues to alert warehouse employees when new order that needs to be scanned has arrived. As-is, audio cues are frequently blocked.
I will note that this issue seems exclusive to the Zebra TC52. If we run our web app as a PWA on, say a Google pixel device, sounds autoplays without user interaction, as expected. We've tried factory resetting our Zebra TC52, ensuring all app are fully up-to-date, etc, but all to no avail.
I'm wondering if this is simply a defect with our device, or if perhaps there's some special configuration on the Zebra TC52 that's to blame? Additional info:
- Model is TC520K
- Hardware version is 40
- Android version is 13
- SPL (CPL): 2023-12-01\NA
- Build_ID: 13-22-18.00-TG-U01-STD-HEL-04
- Fingerprint: Zebra/TC52/TC52:13/13-22-18.00-TG-U01-STD-HEL-04/79:user/release-keys
- Baseline: 13-22-18.00-TG-U01
- Patch Level: U01
(See here for a prior debugging discussion)
Thanks in advance!
2 Replies
Hi Mirek - I see you are already on the most recent A13 BSP; FYI a newer LG update is available, you might want to install it (Zebra Android 13 13-22-18.00-TG-U04-STD-HEL-04) even though it just provides security updates.
You also shared that you updated all apps, so I guess Chrome is also on the latest dessert.
You are also reporting two clashing facts
- "it does NOT autoplay sound until the user interacts with the page"
- "As-is, audio cues are frequently blocked."
Which one of the two holds? Is the autoplay always blocked or just sometimes?
To my knowledge, PWAs purely rely on web browsers, and we do not bring any restrictions in Chrome.
So, I would suggest the following troubleshooting actions
1.- run your app through another Chromium-based browser (MS Edge, Brave, Opera...) and Firefox
2.- run your app in Chrome on a different Zebra device if you have one handy
3.- open a support case at Zebra and share a sample PWA (with source code) that is reproducing the issue
br
Nicola dzl.
Given the extensive troubleshooting steps you've already taken, including resetting your device to factory settings and keeping all apps up to date, it's reasonable to wonder if this issue is due to a defect in the device or if there is a special configuration on the Zebra. TC52 is causing the problem.
Unfortunately, without additional device configuration information or dedicated support from Zebra, determining the exact cause may be difficult. It may be worth contacting Zebra technical support or checking their documentation for any specific configurations related to audio playback or PWA.
In the meantime, I would suggest exploring alternative solutions or workarounds to ensure this issue does not impact your warehouse operations. This may include exploring third-party applications or tools that provide similar functionality but bypass the autorun limitation on the Zebra TC52.
Finally, I want to highlight your recommendation to use multi-factor authentication (mfa cost) to improve data security. Regardless of the technical challenges you face with your web application, implementing MFA remains an important step in protecting sensitive information and preventing unauthorized access. By requiring multiple forms of verification, MFA significantly strengthens your data protection measures and reduces the risk of security breaches.
If you have additional questions or would like to share additional information, please feel free to do so. We are here to help you in any way we can.