Marcel Bradea

Did you ever end up creating a Binary provider to support Sqlite? We do all our new feature development on Sqlite until the model stabilizes (faster iteration as there is...

Hey @jojoman2 looks like Andrew just gave me push permissions to maintain the repo. Will jump on later this week and push out a new version for it. We will...

Hi Vitor, do you mean 2.0 of the Messenger API? We have some in-progress features from the 2.X branches that we intend to push up soon. The lib doesn’t map...

Ahh, let me get back to you this weekend. This may be one of the changes that isn’t pushed up. If this is the case I’ll prioritize getting them up...

We're experiencing the same issue. Not sure if it's related, but we use dynamic plist files per environment, so we have `GoogleService-Info-DEV`/`GoogleService-Info-STAGING'/`GoogleService-Info-PRODUCTION' etc. We've tried setting both `FirebaseAutomaticScreenReportingEnabled` and `FIREBASE_AUTOMATIC_SCREEN_REPORTING_ENABLED`...

Any updates on this? We're currently using lambda helpers to replace this: ```C# switch( authIdentity ){ case AuthIdentity.PhoneNumberIdentity phoneNumberIdentity: installation.SetPreAuthContextPhoneNumber( phoneNumberIdentity.PhoneNumber ); break; case AuthIdentity.MessengerIdentity messengerIdentity: installation.SetPreAuthContextMessengerPageScopedID( messengerIdentity.PageScopedID ); break;...

DEFINITELY demanded. It's great that you guys took the single-relationship option but we just swept our codebase and in fact all our sorting use-cases are "to-many" scenarios (and thus have...

@bdash Makes sense in terms of the complexity needed. The manual version for such a computed property, for example: var userCuriosity:EventCuriosity? { return from( curiosities ).singleOrNil{ $0.person.id == User.currentUserPersonID }...

What's the priority/milestone target for this? This is an EXTREMELY common case used throughout our codebase, blocking our migration. This is a core regression from both EF6 and EFC 2.2...

@smitpatel Oh GOD no. In-memory is NOT viable in API scenarios and was a severe mistake to enable in the get-go as it gave a very incomplete representation of framework...