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

Can't find variable: RealmType #2

Closed
bleonard opened this issue Sep 3, 2015 · 4 comments
Closed

Can't find variable: RealmType #2

bleonard opened this issue Sep 3, 2015 · 4 comments

Comments

@bleonard
Copy link

bleonard commented Sep 3, 2015

Something is happening that prevents the injection of the Realm and RealmType globals in to the JS framework when you upgrade react to the current version.

You can see the issue in the example app if you change the package.json to:

  "dependencies": {
    "react-native": "0.10.0"
  }
@alazier
Copy link
Contributor

alazier commented Sep 3, 2015

This should now be fixed with commit 1148ac5

@alazier alazier closed this as completed Sep 3, 2015
@bleonard
Copy link
Author

bleonard commented Sep 3, 2015

this is still occurring if debugging in chrome.
(cmd+D in the simulator and "Debug in Chrome")

@alazier
Copy link
Contributor

alazier commented Sep 3, 2015

Debugging in chrome does not work as it is built on v8 rather than javascriptCore. We could add some temporary hacks so that the Realm apis are no-ops when in debugging mode, but getting the apis functional in this mode will be a major endeavor.

@bleonard
Copy link
Author

bleonard commented Sep 3, 2015

hmmm, that's going to be trouble. that's a key tool in the react native toolbelt. we'd end up not be able to debug at all really because something will always depend on the database somewhere in the flow.

there's definitely nothing else in the react native world that i've seen that injects things into the js context. I assume you are doing that and not as a npm_module / bridge to work with cordova and be synchronous.

probably be something you'd have to figure out to be successful in this space. make it more an npm module and connect without that injection.

simonask added a commit that referenced this issue Jun 14, 2016
Enable Sync support in Node.js binding
mbalex99 added a commit that referenced this issue Jun 15, 2017
# This is the 1st commit message:

adding ts files

# This is the commit message #2:

updating to ts 2.3.2 and fixing inheritance for ObjectSchema
kneth pushed a commit that referenced this issue Jun 1, 2018
Moved sync-request into devDependencies
kraenhansen added a commit that referenced this issue Jun 16, 2022
kraenhansen added a commit that referenced this issue Jul 16, 2022
kraenhansen added a commit that referenced this issue Oct 24, 2022
kraenhansen added a commit that referenced this issue Oct 26, 2022
takameyer pushed a commit that referenced this issue Dec 28, 2022
kraenhansen added a commit that referenced this issue Jan 11, 2023
* Assert the NDK relative to the Android SDK

* Updating docs and NDK version used on CI
kraenhansen added a commit that referenced this issue Mar 1, 2023
kraenhansen added a commit that referenced this issue Mar 1, 2023
* Assert the NDK relative to the Android SDK

* Updating docs and NDK version used on CI
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants