* Update OS
* Use the latest sync
* Update objectstore
* Use realm-sync 7.2
* Add files to project
* Use OS submodule with fix
* Fix object store includes in xcode project
* add missing object store file to binding.gyp
* Update OS with fix for the GlobalNotifier
* Add OS files to Android jni
* Use master@ObjectStore
* Update to sync v1.0.0-BETA-6.3.
This requires updating to current object store master to accommodate the
changes to sync error reporting.
* Add some include folder search paths
* Add thread_safe_reference to the RealmJS target
There seems to a bug inside the `strip` command (or its `ld64` library) that is being triggered by some users who get this message: `Assertion failed: (0 && "need to handle arm64 -r reloc")`
It is reported that disabling this setting side-steps the issue, and we don't need any stripping done on the static library itself.
Fixes#503
By default, React Native projects target a minimum of iOS 7, but our projects were set to iOS 8 because previously we used a dynamic framework.
When building for an iOS 7 minimum target version, the linker would complain about thread local variables not working on iOS 7. So it was necessary to add even more checks (iOS >= 8 or OS X >= 10.7) before using native thread local variables rather than our shim.
This also changes our projects to target iOS 7 so we can catch these issues quicker in the future.
Moved it up one level since it references the whole source tree inside the src/ directory. Added the functionality to run Node tests from Xcode on the existing RealmNode target.
All realm operations for the RPC are now done in their own thread so it can be allowed to block on waiting for callback results. The recursive and multi-threaded nature of this makes it pretty tricky, but it works!
* master:
add keypath tests
pr feedback, changelog
typo
bug fix
tests
support keypath comparisons for types that support it
support for null queries
don't require optional or link properties when creating objects
[0.11.1] Bump version
Update CHANGELOG with 0.11.1 fixes
Update changelog script
Remove changes_available implementation that asserts
Get correct path to adb from Android Studio
add some simple tests for Realm.write
Update apps to use React Native 0.22
If adb really isn't found (unsure what conditions would cause that to happen), then `false` will be called which will result in that warning message being displayed instead.
Fixes#351
We needed to do this due to the way React Native modules work. Our hacky solution for using a framework ended up falling apart due to it relying on symbols not getting stripped from the main application.
This static library is in its own Xcode project because rnpm links in *all* static libraries from a given Xcode project.
It still only tries localhost for the simulator, but for devices, we now get a list of possible IP addresses to attempt to connect to before throw a more helpful exception.
Resolves#284 and fixes#276
* master: (207 commits)
Convert to using new React Native MainActivity template
Create RealmReactPackage for our Android plugin
Fix doc for Android
NPM ignore react-native/android folder
Skip building Android module under Xcode
Skip building Android module for iOS tests
gitignore Android downloads folder
Update README with instructions to run on Android
Use un-patched RN for Android by installing hook into JSC
cleanup build system
Use Realm in node_modules for ReactTests on Android
Change Demo => ReactTests
adding a 'publishAndroid' task to generate the AAR with prebuilt .so files
Adjust POM_NAME
Use consistent package naming
Remove old Demo files
Add copyright to JNI file
Cleanup platform.hpp
Make our Android module buildable as a dependency
Add `npm test` command
...
This works by installing some assembly into JSGlobalContextCreateInGroup() that will immediately jump out into our own wrapper function so we always can inject the Realm constructor into the context.
We no longer need to have the rebuilt JSC binaries because instead we build a dummy libjsc.so and link against it while allow undefined symbols. At runtime, it will link in the real libjsc.so and resolve the symbols.