* origin/master: (23 commits)
Fix api doc error
fix progress notifications registrations
Fix typo in Github issue template
Fix port conflict between RN >= 0.48 and RPC server (#1294)
Disable testAddListener when running in chrome
Ensure RN has an event loop running for async tests
Make permission tests better handle server delays
Fix race conditions in testAddListener
Separate build and test steps in xcode to reduce chance of hitting "Early unexpected exit"
Ignore errors when sourcing nvm.sh
Don't forward arguments to nvh.sh
Skip sourcing nvm.sh if it's already available
Fix some shellcheck warnings
Ensure node 6.5.0 is installed on CI
Build realm from source for each test-runner test
Improve error reporting for incorrect argument counts for Realm methods
Use the same error messages in the RPC code as the regular code
Silence an unused variable warning when building with sync disabled
Check the exception message in all Realm tests which assert an exception is thrown
Don't discard the actual error message in validated_get_X
...
When building Android on Ubuntu 16.04 LTS, this fixes an error for a missing header file:
In file included from ./src/android/io_realm_react_RealmReactModule.cpp:19:0:
/usr/lib/jvm/java-8-oracle/include/jni.h:45:20: fatal error: jni_md.h: No such file or directory
^
compilation terminated.
make: *** [/home/ashwinp/projects/realm-js/react-native/android/build/tmp/buildReactNdkLib/local/armeabi-v7a/objs-debug/realmreact/src/android/io_realm_react_RealmReactModule.o] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/ashwinp/projects/realm-js/react-native/android/src/main/jni'
:buildReactNdkLib FAILED
FAILURE: Build failed with an exception.
* Add and adopt `Value::is_binary` / `Value::to_binary` / `Value::from_binary`.
These methods allow conversions between `BinaryData` and the equivalent
JavaScript types without using `NativeAccessor`. Instead,
`NativeAccessor` now itself delegates to these methods.
* Have `NativeAccessor::value_for_property` and `RealmObjectClass::set_property`
verify that values are valid for the property in question.
If not, we throw an exception that includes the name and type of the
property in question.
`NativeAccessor` is changed to always hold a reference to a `Realm` and
an `ObjectSchema` in order to make this validation possible.
* Fix the Windows build.
* Remove an unused, incorrect forward declaration of a template class
named `Realm` that caused ambiguity with object store's `Realm` class.
* Disambiguate between `realm::js::PropertyType` and
`realm::PropertyType`.
* Update CHANGELOG.md
* 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.
Thomas Goyne
Ashwin Phatak
Kenneth Geisshirt
agerson
Yavor Georgiev
Jagdeep Nagpal
Dmitry Patsura
blagoev
Mark Rowe
Yavor Georgiev
David Howell
David Howell
Nabil Hachicha
Radu Tutueanu
Kristian Dupont
Ari Lazier
Scott Kyle