It'll sting internally, for sure. For how long? Not sure but I'd say it'll halt release processes for maybe a week or two.
Any large organization resorts to using enterprise certs for beta and QA distributions of an app as the device limits are unrealistically low for them. These things tend to have cycles where a features have to get in by a certain date and then builds are sent off for beta and QA testing. There's no question this issue throws a wrench in this process.
A solution to this problem is signing it with another enterprise cert. I don't know if all of Facebook's enterprise signing certs were revoked or just the one used for this app and even if FB tried applying for a new one (maybe through a subsidiary?) that takes time.
Any large organization resorts to using enterprise certs for beta and QA distributions of an app as the device limits are unrealistically low for them. These things tend to have cycles where a features have to get in by a certain date and then builds are sent off for beta and QA testing. There's no question this issue throws a wrench in this process.
A solution to this problem is signing it with another enterprise cert. I don't know if all of Facebook's enterprise signing certs were revoked or just the one used for this app and even if FB tried applying for a new one (maybe through a subsidiary?) that takes time.