Hi, I have the exact same error and I didn't quite understand what the workaround is. @Selda you're talking about registering a client server as TLS 1.2, what client server are you talking about ? If that may help, our application worked fine using our previous certificate (and it still works if we regenerate it with the previous cert), then we tried to generate a new in-house certificate and now it doesn't start anymore, throwing the same error : Bootstrapping failed for <FBApplicationProcess: 0x108bc7260; application<com.efrontech.aero.valrhona.prd>:<invalid>> with error: <NSError: 0x2817a6700; domain: RBSRequestErrorDomain; code: 5; reason: "Launch failed."> { underlyingError = <NSError: 0x2817a6460; domain: NSPOSIXErrorDomain; code: 85>; } We also see this error Process start failed with Error Domain=NSPOSIXErrorDomain Code=85 "Bad executable (or shared library)" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 85} Thanks for your help UPDATE: The app works fine when we use a development certificate associated with our ipad UDID. It really looks like there's something wrong with the in-house certificate.