user.constructor._getExistingUser is not a function in Chrome Debugger
See original GitHub issueWhile reinstalling an existing react native app, I have updated to the latest version of realm (2.2.2), along with upgrading all dependencies.
I get the user.constructor._getExistingUser is not a function
error. This looks like a new added function.
This error might be related with “subscribeToObjects is not a function”
https://github.com/realm/realm-js/issues/1608
It was not possible to use chrome debugger with partial realm but now debugger is not usable with realmjs at all.
Version of Realm and Tooling
- Realm JS SDK Version: 2.2.2
- React Native: 0.52.0
- Client OS & Version: Windows 10
- Which debugger for React Native: ? Chrome
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
javascript constructor with google chrome bugged? [duplicate]
It's a problem with the Chrome console, not your code. You cannot reliably "print" the state of an object. See this question. –...
Read more >JavaScript debugging reference - Chrome Developers
Discover new debugging workflows in this comprehensive reference of Chrome DevTools debugging features.
Read more >Using the Chrome Debugger Tools, Part 6: The Heap Profiler
The first column is labelled Constructor , indicating that the objects are grouped by their constructor function. As you can see in figure...
Read more >Chrome Developer Tools: 4 Features You Need to Know
Open up a webpage in Google Chrome; Use the keyboard shortcut Cmd + Alt + I / Ctrl + Shift + I (or...
Read more >Debugging in the browser - The Modern JavaScript Tutorial
We'll be using Chrome here, because it has enough features, ... differently if the next statement is a function call (not a built-in, ......
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 FreeTop 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
Top GitHub Comments
@ozmaat @eilongal @hussainb I believe we found the root cause (see #1634) and it is embarrassing and simple. We plan to do a release soon.
Confirm that 2.2.4 did not fix the issue.