admin管理员组

文章数量:1291745

Some of our users are getting these errors (getReadModeConfig, getReadModeRender, getReadModeExtract) on form submission. We are using react with Material UI for form. Don't know exactly what these errors mean. Any help would be appreciated

Some of our users are getting these errors (getReadModeConfig, getReadModeRender, getReadModeExtract) on form submission. We are using react with Material UI for form. Don't know exactly what these errors mean. Any help would be appreciated

Share Improve this question asked Oct 2, 2020 at 16:33 Amardeep SinghAmardeep Singh 4134 silver badges6 bronze badges 9
  • 2 I don't have any answers, but don't think it is to do with React or Material UI. I've been seeing a very small number of the exact same errors - usually from the same users. I believe it is a browser extension but don't have any proof yet. In this particular app, I don't use React or Material UI (or any libraries, in fact). – Dan Soper Commented Oct 5, 2020 at 8:10
  • 8 I think this might be caused by the HeyTap browser. All of these errors on my system have that user agent. – Dan Soper Commented Oct 7, 2020 at 8:53
  • Even i'm seeing this in my web app since Sep 21st, my web app uses ReactJS – yashhy Commented Oct 12, 2020 at 10:22
  • Yes, I'm also seeing some errors like these in my react app since last few weeks, not able to figure out what is wrong. – Aditya Commented Oct 28, 2020 at 8:28
  • 1 I agree this looks like its not react specific, we had those pop in our sentry logs too in angular, it looks like they are triggered by button clics but I can not find anything else on these. – Lakston Commented Nov 20, 2020 at 14:43
 |  Show 4 more ments

1 Answer 1

Reset to default 7

I've also been seeing this error reported several times starting around 09/25, and the UA string is always the HeyTap Browser. I agree with what Dan Snoper said in his ment above: the error is most likely being caused by that browser, so I don't think there is anything we can do to fix or prevent it.

本文标签: