Undefined error when evaluating 'this.modelClass.associations'
See original GitHub issueHi
We have an app in production which uses the watermelonDb version 0.14.0. Recently we have been getting this error in our Sentry crash reporting:
TypeError: undefined is not an object (evaluating 'this.modelClass.associations')
This generally happens when making queries to the database.
We haven’t been able to replicate the issue locally but according to the crash reports it seems to be only affecting Android devices.
If anyone can offer any insight into this issue that would be great. Thanks
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Rails Rich Associations - undefined method error
Using this schema, I would assume the "Assignment" model is sort of the join table, which holds the information for which users belong...
Read more >Changelog - WatermelonDB documentation - GitHub Pages
This change was necessary to fix a long-standing Sync bug. ... [DX] Queries with bad associations now show more helpful error message; [Query]...
Read more >Systems Analysis and Design Ch. 4-7 Flashcards | Quizlet
b. binary d. undefined. unary. The domain model class diagram is used to ______ . a. show the software classes in the problem...
Read more >GAMS — A User's Guide
6.3.4 Extended Range Arithmetic and Error Handling. GAMS uses an extended range arithmetic to handle missing data, the results of undefined operations, ...
Read more >Customizing and Extending IBM Content Navigator
However, it is the user's responsibility to evaluate and ... IBM Corporation, International Technical Support Organization ... attributeName!=undefined).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Since upgrading our app to React Native version 0.60.5 and watermelon db to version 0.15.0 we have not experienced this issue.
Same here, stopped seeing this error after upgrading to RN v0.62.2. But now we are seeing React Native’s “Should not already be working.” at almost the same frequency. So it looks like the error just mutated. Just asking here if anyone of you are also seeing it in your error logs? https://github.com/facebook/react-native/issues/28948