Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'toString' of undefined #2123

Open
outoftime opened this issue Jan 31, 2020 · 1 comment
Open

Cannot read property 'toString' of undefined #2123

outoftime opened this issue Jan 31, 2020 · 1 comment
Assignees
Labels

Comments

@outoftime
Copy link
Contributor

outoftime commented Jan 31, 2020

This is a followup to #2121, which tracked a regression in which this error became uncaught and broke user-facing behavior. The proximate cause of that regression was #1954, although through no fault of that PR; my guess is that we are missing graceful uncaught error handling logic in our redux-logic integration. So, a fix for this issue should:

Error in Popcode

TypeError in /
Cannot read property 'toString' of undefined

View on Bugsnag

Stacktrace

validations/Validator.js:26 - t.value
validations/javascript/esprima.js:102 - t.value
validations/Validator.js:33 - t.value
validations/Validator.js:21 - t.<anonymous>

View full stacktrace

Created by Matthew Brown via Bugsnag

@joshling1919
Copy link
Contributor

joshling1919 commented Feb 14, 2020

@outoftime I think I saw a recent reoccurrence of this error on the #errors slack channel after we started sending the sources up to Bugsnag. Any chance I could get a screenshot of what those sources might be and maybe we can resolve this issue? Thanks!

@wylieconlon wylieconlon self-assigned this Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants