James Stone

We would like to implement full support for "IN" at some point, but because of the workaround mentioned here with chaining equality with "OR" it hasn't been a high priority....

@abhishekmatta999 yes, the workaround works on any type of value. If you are having issues with your query, let us know more details so we can try to help you.

@abhishekmatta999 the best practice is to pass your variables in by argument substitution, then you don't have to worry about the format. With the object id's stored in variables `oid1`...

There's a good chance this is the same issue as described in https://github.com/realm/realm-core/pull/4175 The reason being the combination of the notifier being run and `ConstLstIf::get()` being triggered. The know (and...

Are the apps that are crashing using Realm sync? I'm just realizing that the indices reported to the replication for notifications are the full set including unresolved links, and this...

@nirinchev we have `Obj::get_path()` and `Obj::get_fat_path()` which return the entire path to an embedded object, the top object will be the first element in the returned list. Does this satisfy...

Possibly related [failure](https://ci.realm.io/blue/rest/organizations/jenkins/pipelines/realm/pipelines/realm-core/branches/PR-5663/runs/6/nodes/93/steps/867/log/?start=0): ``` Thread[2]: /Users/realm/workspace/realm_realm-core_PR-5663/test/test_sync.cpp:1138: Begin Sync_FastRebind /Users/realm/workspace/realm_realm-core_PR-5663/src/realm/array.hpp:754: [realm-core-12.3.0] Assertion failed: has_refs() 0 realm-sync-tests 0x0000000107f5b1bc _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28 1 realm-sync-tests 0x0000000107f5b0c1 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 385 2 realm-sync-tests 0x0000000107e050b1 _ZNK5realm5Group8set_sizeEv +...

Another failure: ``` 2: Thread[3]: /Users/realm/workspace/realm_realm-core_PR-5918/test/test_sync.cpp:1502: Begin Sync_FailingReadsOnClientSide 2: /Users/realm/workspace/realm_realm-core_PR-5918/src/realm/sync/noinst/server/server_history.cpp:1718: [realm-core-12.8.0] Assertion failed: m_acc->cf_locked_server_versions.size() == m_num_client_files 2: 0 realm-sync-tests 0x000000010187cd0c _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28 2: 1 realm-sync-tests 0x000000010187cc11 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 385...

Thanks for reporting this @tacohoekwater. The stack trace shows an assertion in `realm::_impl::RealmCoordinator::promote_to_write(realm::Realm&)` which is likely ` REALM_ASSERT(!realm.is_in_transaction());`. This seems to indicate that there is already an ongoing write transaction....

The relevant stack from the attached file is: ``` 4 libsystem_c.dylib 0x12220e6b7 abort + 130 5 realm-wrappers 0x1117642e9 please_report_this_issue_in_github_realm_realm_core + 9 6 realm-wrappers 0x111764650 realm::util::terminate_internal(std::__1::basic_stringstream&) + 256 7 realm-wrappers 0x111764471...