3.2 JSON Parse error: Unrecognized token '<' Password bug

Charlie

Save settings in local storage: Unchecked.
Save cache in local storage: Checked.

Screen Shot 2021-01-07 at 2.07.12 PM.png

Ill try toggling both and see if there is any change.

Yeah, its pretty far from the router, though Ive never had any issues before using 1.21, 2.0.3, or 3.1.1 (even when it was in a steel case, lol).

Phaedrux

@Charlie Also try with both off and both on.

I'm just poking in the dark here. I'm not certain it's related.

Charlie

@Phaedrux

Definitely will do. Your guesses are way more educated than mine, so I greatly appreciate it. Ill let you know the results.

Phaedrux

My theory is that it's trying to save the cache or settings on the SD card and the weak wifi signal is causing issues.

I'm not sure which storage the "local storage" is referring to. It's a bit ambiguous and I never got clarification last time it came up. It's either the SD card as in local to the machine, or the browser side, as in local to the viewer.

@chrishamm will know for sure, but he's probably sleeping like a baby at the moment.

Charlie

@Phaedrux

Unfortunately all four configurations (emptying browser cache each time) still had the same error come up.

Phaedrux

My last suggestion is to manually replace the contents of the /www folder with a fresh set from https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/DuetWebControl-SD.zip

And if that doesn't work, try a fresh SD card.

And if that doesn't work, wait for chrishamm

Charlie

@Phaedrux

Unfortunately manually replacing the www folder did not change anything, and neither did a new SD card. Thank you for your input though!

Charlie

@chrishamm

If you have any insight, I would greatly appreciate it.

chrishamm

@Charlie Some response doesn't seem right, no valid JSON should start with '<' so you're getting an error. Try to open the developer console with F12 and check the log for further details. You should be able to see an error trace in there.

What browser are you using? Can you open DWC from a different device?

Charlie

@chrishamm

Thank you for your response.

I opened the developer console in Safari (Develop > Show Web Inspector > Console). I found the following errors and warnings:

Screen Shot 2021-01-08 at 12.58.28 PM.png

Im currently using Safari.

Charlie

The first error does not seem to be the cause of the issue, and was resolved by inserting a blank "dwc-plugins.json" file in the sys/ folder using DWC.

The subsequent errors seem to be the cause of the issue. Ive diffchecked both the "pollconnector.js" and the "BaseConnector.js" files against the files in GitHub and they appear to be identical. Im pretty out of my depth when it comes to coding, so any help would be greatly appreciated.

Phaedrux

Can you test with Chrome just to see if it's isolated to safari on your machine? What MacOS and Safari version are you running?

Sindarius

The 401 error would mean the < you are getting is because it's sending an HTML 401 error page response.

What happens if you take out the M551 in your config? Maybe there is an issue going on with passwords?

Charlie

@Phaedrux

I will try to see if I can replicate the issue on Chrome, though its difficult to reliably replicate the issue. I am using macOS Big Sur 11.1 and Safari 14.0.2 (most up to date I believe).

alankilian

(I'm NOT a JavaScript guy, so....))

It looks like the code is trying to parse a JSON tesponse, but the response is not JSON, it's text.

I notice in PollConnector.js this code:

				if (xhr.status >= 200 && xhr.status < 300) {
					if (responseType === 'json') {
						try {
							if (!xhr.responseText) {
								resolve(null);
							} else {
								resolve(JSON.parse(xhr.responseText));
							}
						} catch (e) {
							reject(e);
						}
					} else {
						resolve(xhr.response);
					}

But in BaseConnector.js I see this code:

				if (xhr.status >= 200 && xhr.status < 300) {
					try {
						if (!xhr.responseText) {
							resolve(null);
						} else {
							resolve(JSON.parse(xhr.responseText));
						}
					} catch (e) {
						reject(e);
					}

Maybe if you use the code from PollConnector.js in BaseConnector.js you'll fix the issue.

Charlie

@Phaedrux

It appears as though this is NOT occurring in Chrome, though Ive been having issues replicating the error recently.

Phaedrux

Wouldn't be the first time Safari has behaved oddly.

Charlie

@Phaedrux

Hahaha! Very true.

I am testing out the solution by @Sindarius and I will report back the results.

Charlie

@Sindarius

Your solution appears to have worked! I deleted M551 and no more error messages in Safari.

Charlie

@alankilian

Thank you so much for your response, but I have no clue how I would go about changing this, as I have no clue where these files (don't even know if the files sit on the Duet, lol).