> This is the second similar incident this year. We want to apologize for the inconvenience these events have had on our developers and their users.
It’s an odd addendum to put in and appears ominous to me.
There are many similar successful concepts that cap the maintenance window that services must tolerate, while at the same time giving developers enough forewarning to understand what is expected of them.
The crash was just that a dictionary decoded from json sent by the server contained null in a place where the code expected a non-null value. The actual payload difference would not be very interesting.
My understanding is that to use Facebook as an auth mechanism, you must use their SDK (and personal data vacuuming along with it), so dropping Facebook auth would allow apps to drop the SDK, which would be a win for both privacy advocates and users who enjoy their apps working even when Facebook breaks something.
Does anyone know more about this?
As far as I remember Facebook does support being and openid connect authentication provider so it should be theoretically possible without their SDK. But it might be that they put some practical restrictions in place to force usage of their API??
Moreover, the actionable advice to upgrade the SDK is a complete non-technical non-sequter seemingly put as a distraction:
- They admit it was a server side change that caused the crashes. SDK version doesn't change that.
- No breakdown of which versions were affected (or was it everything?).
- Is a newer release safer? Were changes made that we would get by upgrading?
Did anyone by chance MITM the server payload to understand the bad code/bug?