@Eric_c 

Same problem from 4 months .. Thinking to replace now...

Can we have an ETA about the next firmware release or just an update saying TP-Link won't fix the issue? If that's the case, can you consider open sourcing the firware so the community can fix it?

@Kevin_Z 

hi seems that i can't see my sms also just brought mr600 this month and yesterday it was working perfectly, tried to look for the beta firmware to have it fixed but could not locate it.

After initially reporting the new firmware has worked, I am still on the test firmware and SMS are still non readable. I have 9 I cant access. Please fix this as a formal firmware soon. The fact this is a very recent router with seemingly very little in terms of support i will be going o the trading standards council and wriing reviews where ever I can. Past the initial engagement there has been LITTLE in the way of meaningful feedback to this issue.

Thanks @Kevin_Z you have missed my first question, asking for an ETA for the release of the firmware with the fix. I understand it's been in beta for several months now, and surely, given the number of users affected your QA team should be able to reproduce the issue and qualify the fixed version to release an official built to all the affected users. Those routers are all new and still under warranty, so it's only fair to expect a reasonable turnaround time for defect fixes that affect functionallity that is advertised in the functional specs.

Looking forward to hearing from you, and hopefuly to see a release in the coming weeks.

Thanks

@Kevin_Z 

What I can find the latest beta is Archer_MR600v1_1.1.0_0.9.1_[191017-rel39388]_up_boot_2019-10-17_11.06.05

I have been running this version for some time and I can confirm it does not fix the issue.

I can also confirm that the previously presented workaround works for this version and should contain enough hints to what the source of the problem might be.

It looks like it happens for me when the "Phone number" field contains non-ascii characters, such as "Tandläkaren" (the dentist, in swedish)

This can be confirmed by running this code in the browser console.

decodeURIComponent(escape("Tandläkaren"))

You can find this code in in a crash site your javascript source that is the reason messages are not appearing. 

decodeURIComponent(escape(a.stringify(t)))