amccarri

  • Joined on
@amccarri
Restart XCode / F2 no longer works.
amccarri commented on issue realm/realm-cocoa#1900
@amccarri

My steps were similar, but I already had Carthage set up so Framework build dir was already in my framework search path. I also didn't add the stri…

amccarri commented on issue realm/realm-cocoa#1900
@amccarri

Found the problem. I am using Carthage and I had to add the RealmSwift.framework to carthage copy-frameworks build phase, but NOT add it to the lin…

@amccarri
Using Carthage -- Realm.framework depends on RealmSwift.framework??
@amccarri
Using Carthage -- Realm.framework depends on RealmSwift.framework??
@amccarri

So yeah, it is definitely something CocoaPods was doing. I switched my project over to use Carthage and it works much better.

@amccarri

Yeah what's weird is that flattenMap works with most other things. The first two calls to flattenMap in the chain work fine. Only when I return a R…

@amccarri

I'm seeing this and I do not have it linked twice unless CocoaPods is doing something weird? I am building a framework though, not an app.

@amccarri

I should also note, based on searching similar issues is that as near as I can tell, this is not a scenario where the RAC / pods is being linked tw…

@amccarri
returning RACSubject from flattenMap results in assertion failure saying RACDynamicSignal is not a stream.
@amccarri

Yeah I was thinking it was a code smell also, but I'm building this for a group that is very new to Reactive and this is something they were asking…

@amccarri

But I don't want to stop the propagation if they subscribed to the error block. Maybe a better way to phrase the question is, how do I determine if…

@amccarri

I think -catch: is inverse of what I want. Catch let's me intercept the error and propagate it if I choose. What I want is to do some default error…

@amccarri
What is best advice for default error handling?
amccarri commented on pull request ReactiveCocoa/ReactiveCocoa#1625
@amccarri

@kastiglione sounds like this just bit us this morning. We wait till < 10% of our users are left on the previous rev before dropping support for th…