TypeErrorCannot read properties of undefined (reading ‘hasOwnProperty’)

TypeErrorCannot read properties of undefined (reading ‘hasOwnProperty’)

Level: Error

Unhandled

|

New

|

h(widgetapp/2025-01-21-14-07-56/widget_app_base_1737468476256)

Most RelevantFull Stack TraceNewestTypeErrorCannot read properties of undefined (reading ‘hasOwnProperty’)mechanisminstrumenthandledfalsefunctionsetInterval

• /widgetapp/2025-01-21-14-07-56/widget_app_base_1737468476256.js in h at line 3:23900Unminify CodeIn App
• /widgetapp/2025-01-21-14-07-56/widget_app_base_1737468476256.js in c at line 3:20994Unminify CodeIn App
• /widgetapp/2025-01-21-14-07-56/widget_app_base_1737468476256.js at line 3:22752Unminify CodeIn App
  
  

Chatgpt:

This particular error indicates that somewhere in the UserWay widget script (the widget_app_base_*.js file), the code is calling .hasOwnProperty() on something that turns out to be undefined. In other words, a script variable or object (commonly yt.services in UserWay’s code) isn’t defined when the code expects it to be.

Below are common reasons and troubleshooting steps you can take to solve (or at least narrow down) the cause: Why This Error Happens

1. Failed to load or fetch configuration (“tunings”)
   From the logs, the script tries to fetch https://api.userway.org/api/v1/tunings/... and encounters a TypeError: Failed to fetch. If the widget depends on that response to properly create the yt.services object, then failing to fetch the tunings can lead to a situation where yt.services is undefined. Any subsequent code calling yt.services.hasOwnProperty(...) would then fail with the exact error you’re seeing:

   Cannot read properties of undefined (reading 'hasOwnProperty')

2. Blocked or misconfigured script
   A firewall or a browser extension could be blocking the script from api.userway.org, or there may be network or DNS issues preventing that script from loading. If the script never initializes, the code that references yt or yt.services will be missing the objects it expects.
3. Version or embedding issues
   If the UserWay widget script is out of date or has been embedded incorrectly (e.g., partial embed code, a stale snippet, or placed in the wrong spot in the HTML), there can be race conditions where the code tries to run before the yt object is fully available.
4. Conflict with other scripts
   Occasionally, third-party scripts (e.g., caching or bundling plugins, or other accessibility or analytics scripts) can interfere with the loading order, override global variables, or block requests, causing the UserWay code to break unexpectedly.

How to Fix or Work Around It

1. Verify the UserWay widget is correctly configured

• Double-check the embed code in your site header or the plugin settings if you installed UserWay via a WordPress plugin.
• Make sure the domain or license key you’re using is valid for api.userway.org.

1. Check for fetch/cors/firewall issues

• In the DevTools Network tab (or in your hosting logs), ensure the request to https://api.userway.org/api/v1/tunings/... is not being blocked.
• If you see an error (403, 404, CORS, or timeouts), you’ll need to address that at the server or plugin level.
• Temporarily disable any security/caching plugin (Cloudflare, WordFence, etc.) to see if they’re blocking or altering the request.

1. Update or reinstall the UserWay plugin

• If you’re using WordPress, try updating the plugin to its latest version.
• If you’re loading the script manually, get the freshest embed code from UserWay’s portal.

1. Check for script conflicts

• If you have multiple accessibility widgets installed, or if there are custom scripts manipulating the same global objects, try temporarily disabling them to see if the error goes away.
• Sometimes minification or bundling tools can cause these conflicts.

1. Contact UserWay support if needed

• Since the failing URL is on api.userway.org, sometimes the issue can be on their side or relate to your account settings.
• Provide them the error logs: specifically the fetch error and the Cannot read properties of undefined (reading 'hasOwnProperty') stack trace.

1. As a last resort, remove or disable the widget

• If you cannot resolve the error and it is causing site breakage, you may remove or deactivate the script from your site until a fix or updated script is available.

Summary

The short version is that the UserWay script expects certain data (the "tunings", or yt.services object) to be present. Because that data is never successfully retrieved, the script tries to call .hasOwnProperty() on undefined. Fixing the root cause—usually a failed fetch to api.userway.org—should make the error disappear.

1. Make sure the script is up to date and embedded correctly.
2. Confirm nothing on your site (plugins, firewall, etc.) is blocking or modifying requests to api.userway.org.
3. If errors persist, consult UserWay support with these log details.