You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Encountered an unhandled error in the injected client.js script while debugging a Flutter application in Google IDX, with the Google Chrome web browser. The error message suggests a SecurityError, stating that the construction of a WebSocket failed due to attempting to initiate an insecure connection from a page loaded over HTTPS.
Start debugging a Flutter application in Google IDX.
Monitor the console output for any errors.
Observe the error related to the construction of a WebSocket and the SecurityError message.
Expected Behavior:
Debugging should proceed smoothly without encountering any unhandled errors related to WebSocket construction.
Actual Behavior:
Encountered an unhandled error in the injected client.js script, specifically related to WebSocket construction and SecurityError.
Additional Information:
The error message suggests that disabling the injected client.js script using the --no-injected-client flag in webdev might resolve the issue, but it would also disable debugging and hot reload/restart functionality.
Description:
Encountered an unhandled error in the injected client.js script while debugging a Flutter application in Google IDX, with the Google Chrome web browser. The error message suggests a SecurityError, stating that the construction of a WebSocket failed due to attempting to initiate an insecure connection from a page loaded over HTTPS.
IDX version: 1.83.1
Chrome version: 125.0.6422.142
Steps to Reproduce:
Expected Behavior:
Debugging should proceed smoothly without encountering any unhandled errors related to WebSocket construction.
Actual Behavior:
Encountered an unhandled error in the injected client.js script, specifically related to WebSocket construction and SecurityError.
Additional Information:
The error message suggests that disabling the injected client.js script using the --no-injected-client flag in webdev might resolve the issue, but it would also disable debugging and hot reload/restart functionality.
The text was updated successfully, but these errors were encountered: