RxSwift | Space to study RxSwift | Reactive Programming library

Your setupSnapshot() function is being called before the values have been accepted into followers. I haven't used a NSDiffableDataSourceSnapshot yet, but you likely need to do something like this instead:

Every time you emit a new value out of the filters Observable, the collection view will reload. Part of what this means is that it goes back to the beginning. So the way to fix this is to make it so that you don't emit a new value from filters when the user selects an item.

There are a number of ways to do this.

• The simplest would be to remove the isSelected parameter from the FilterCellModel type. Instead track what items are selected through some other means.
• Another option would be to use a custom DataSource that only reloads the items who's state has changed. Check out the RxDataSources library for ideas.

You can try this pod RxTimer

Answering

is it possible to do this with RxSwift

that's not possible, as every time we trigger the function it gets dispatched and we can't access the callbacks from other threads.

You're creating a race condition, a workaround is to populate the data once in a singleton, and rather than calling the function multiple times use that singleton.

some other approach might also work singleton is just an example.

Race condition: A race condition is what happens when the expected completion order of a sequence of operations becomes unpredictable, causing our program logic to end up in an undefined state

The core of RxSwift is the Event enum with associated values. This enum cannot be ported into Objective-C.

The answer to your question is... You can't use RxSwift in Objective-C code.

An alternative would be use ReactiveObjC in your Objective-C code and map from RxSwift Observables to ReactiveObjC Signals.

This is actually because of the Apple tools that can't search for the correct Frameworks Search Path. The fix is in this link: https://github.com/ReactiveX/RxSwift/issues/2292#issuecomment-804045119

As long as you don't insist too strongly on the "array" part, combineLatest or zip is correct for the Combine framework too. The difference between them is whether you want the overall value emitted each time to contain the oldest (zip) or the newest (combineLatest) contribution from each publisher.

Your example doesn't actually give enough information to tell which of those you want. To know which you want, you'd need to say what should happen when you say e.g.:

In the section titled Compatibility Version Numbers at Runtime within https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/VersionInformation.html the context & meaning is fairly clear that the Xcode linker links against only one version (and that it must be the older version if the framework is dynamically linked). I.e., all of the determiners are singular: no linking 2 or more versions into the same app. So it seems that you have exactly 2 choices:

• upgrade Framework A to utilize RxSwift 2.0
• forego using RxSwift 1.0 in your app so as to use RxSwift 1.0 in your app (throughout your app, both Framework A and your app-domain)

The desired choice of linking in both an RxSwift 1.0 identifier and an RxSwift 2.0 identifier for the same identifier is not possible with the Xcode linker, the desired choice (linking in 2 different versions of RxSwift into the same app executable) is actually a nonexistent choice—hence not an option after all.

You have registered the cell class against your reuse identifier. This just instantiates your cell instances without any reference to your XIB file, and so the outlets are not connected.

You need to register the XIB file against the reuse identifier.