Error: Expected message to have sourceDomain
See original GitHub issueAfter upgrading from xcomponent to zoid, my window.xprops are not populated anymore, and i’m seeing the following error in the browser console on startup:
Error: Expected message to have sourceDomain
I literally only installed the latest zoid version, uninstalled xcomponent and replaced the corresponding xcomponent.create
with zoid.create
. I have no clue what is causing that error.
I have also noticed that when i inspect my window.xprops
, they are now undefined, when they used to be populated.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why do I get error "Expected a message object, but got kind
I resolved the problem. The error was due to version difference. Datastore worked with library protobuf 3.20.1 but didn't with 4.21.0.
Read more >Friday Mail Sack: Unintended Hilarity Edition
Let's get it. Question. When we change security on our group policies using GPMC, we always get this disturbing message: “The permissions for ......
Read more >RED & WHITE TAXI
sourceDomain) throw new Error("Expected message to have sourceDomain"); 0 !== message.sourceDomain.indexOf(__WEBPACK_IMPORTED_MODULE_1__conf__.b.
Read more >DNS errors - common codes and messages - Paessler
Switch to PRTG to get rid of all the DNS errors. Use the all-in-one DNS monitoring tool PRTG now to save you worries,...
Read more >e10113.pdf - Oracle Help Center
Oracle Fusion Middleware Error Messages Reference, 11g Release 1 ... Oracle customers have access to electronic support through My Oracle Support. For.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No prob at all! Glad it’s working
You’re right, after some close inspection I’ve noticed that the component URL was pointing to another frame that was loading a different version of my script 😓. Thank you