- 3comments
- 15comments
- 16comments
- 7comments
- 280comments
- 461comments
- 83comments
- 22comments
- 10comments
- 4comments
- —discuss
- 19comments
- 184comments
- 37comments
- 31comments
- 521comments
- 83comments
- 47comments
- 216comments
- 340comments
- 211comments
- 3comments
- 110comments
- 44comments
- 197comments
- 92comments
- 9comments
- 9comments
- 267comments
- 22comments
Resolved - https://github.com/firebase/firebase-ios-sdk/issues/16728#is...
Resolved, but can still affect customers for up to 4 hours...
So many problems here, and no signs of an updated SDK that behaves properly on malformed input.
This is not the first time this has happened.
I was wondering why random apps kept crashing today. Good to know.
But this is completely not acceptable from the Google
Ugh.
That's the dark side of these types of dependencies.
But they provide a great deal of utility, so I can understand the attraction.
I'm hearing an awful lot of "How could they do this to us?" and not a lot of "Wow, maybe we should have read some of this 3rd party code we bundled into 'ALLLL' of our apps"
Just an ignorant and naive outsider's take, but to me it paints a pretty damning picture of the state of mobile development.
Mobile and frontend development, both, now-a-days contain way way way more dependencies than they should.
I remember first learning about Firebase when working on Android push notifications, a loooooong time ago (~2011 i think). Over time it grew into this full-featured app development platform, after an aquisition (don’t remember the name).
These days however it feels a bit neglected, and somehow poorly bolted on to GCP. I still have a few production apps running on it and news like this reinforces my belief that it’s in decline.
What are folks using these days that (ideally) is open source and self-hostable? I don’t want to lock in with another platform. Some of these apps use the offline sync feature of Firestore (apps used in basements and other low-connectivity areas).