TypeError: The expression cannot be converted to return the specified type.
See original GitHub issueI have a file sending app that works fine on localhost with local testing but when hosted remotely even when the two browsers are on the same computer I get this error:
TypeError: The expression cannot be converted to return the specified type.
Which is thrown from here: https://github.com/feross/simple-peer/blob/master/index.js#L243
Not sure why it’s happening only on remote. If it helps the apps source is here: https://github.com/Arcath/file-from-me
Issue Analytics
- State:
- Created 4 years ago
- Comments:8
Top Results From Across the Web
Xpath is invalid: TypeError: The expression cannot be ...
xpath is invalid : TypeError: The expression cannot be converted to return the specified type. The code I used is
Read more >The expression cannot be converted to return the specified type.
TypeError : The expression cannot be converted to return the specified type.
Read more >The expression cannot be converted to return the specified type
Missing ServiceWorker script gives confusing TypeError message - The expression cannot be converted to return the specified type.
Read more >Common issues and solutions - mypy 0.991 documentation
ImportError from circular imports · NameError: name "X" is not defined from forward references · TypeError: 'type' object is not subscriptable from types...
Read more >SQLSTATE values and common error codes - Db2 - IBM
01517, A character that could not be converted was replaced with a ... 10507, A type error was encountered processing an XPath or...
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 Free
Top 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
I found the reason for this. Firefox respects the max message size of the peer it is connected to, so if you try to send data larger than the max message size, Firefox throws this error. The default max message size is
65535
if the peer does not provide it (and currently no browser provides it other than Firefox).So if you’re sending data larger than
65535
bytes, this is probably the source of the error.Tracking in #546