Hacker News new | past | comments | ask | show | jobs | submit login

The fact that Facebook tried to hide their involvement by using intermediaries like “uTest” says something though, right?



Regardless of whether Facebook was also trying to deceive users specifically—which we'll never know—they likely wanted to deceive Apple. I'm not going to blame any developer for attempting to bypass Apple's stupid restrictions.

Using intermediaries also allowed Facebook to technically not violate Apple's enterprise certificate contract (because the intermediaries were in violation instead).


> Using intermediaries also allowed Facebook to technically not violate Apple's enterprise certificate contract (because the intermediaries were in violation instead).

I actually though they would have done that, but it used the regular "iPhone Distribution: Facebook, Inc. (In-House)" cert, they didn't even create a shell entity and get a new one. Reports say Apple has revoked this cert, breaking all internal (legitimate) apps and possibly creating quite a bit of chaos for internal ops.{1} Their separate Apple Developer Program organization account, used to deploy TestFlight public and private betas and App Store apps, as well as local deployment to a small number of devices without Apple involvement for development testing, is not affected.

The intermediaries may or may not face consequences if they have separate agreements with Apple, but they did not use any Apple products to do their part and have not violated anything with Apple.

{1} https://www.theverge.com/2019/1/30/18203551/apple-facebook-b...


Huh, I stand corrected. I'm pretty surprised Facebook used their own cert. The fact it has been revoked was 100% predictable.


When collecting data like this, best to leave it to the pros - whether they're internal, or you have to contract out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: