I Can't launch iOS apps with In-House certificate and provisioning profile

Question

Created Oct ’20

Replies 5

Boosts 0

Views 5.4k

Participants 5

I'm having a problem launching an iOS app that is built using the In-House build type. We have Apple Enterprise Developer Program Certificate and generate an In-House Provisioning Profile and can generate IPA files. I also trust the profile on my phone as an enterprise app but the app always crash/exit upon launching it. I check the logs on Xcode to look for a problem and the message log says "
Bootstrapping failed
for <FBApplicationProcess: 0x14289dff0; application<ourdomain>:<invalid>> with error: <NSError: 0x28252fa20; domain: RBSRequestErrorDomain; code: 5; reason: "Launch failed."> {
underlyingError = <NSError: 0x28252d080; domain: NSPOSIXErrorDomain; code: 85>;
}
"

Answered by Selda in 643037022

Hi,
We were having the same problem. We solved our problem.
The client server registered as TLS 1.2 and the application worked without any problems. You can try to change enable TLS 1.2 support on registry.
We tried very hard to solve the problem. I hope this may help you too.

Selda

Boost

Answer 1

Selda OP

Oct ’20

Accepted Answer

Hi,
We were having the same problem. We solved our problem.
The client server registered as TLS 1.2 and the application worked without any problems. You can try to change enable TLS 1.2 support on registry.
We tried very hard to solve the problem. I hope this may help you too.

Selda

1

Answer 2

mmc7779 OP

Oct ’20

Hi Selda,

Thank you for your reply,
Where can I change this TLS? But the way we're using outsystems for the development.

Thank you again.

0

Answer 3

mmc7779 OP

Oct ’20

Hi Selda,

Your suggestion works with us as well, Thank you very much.

0

Answer 4

eFront92 OP

Nov ’20

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.

0

Answer 5

Camron OP

Jan ’22

@Selda I go the same error when I try to test my singed with ad-hoc distribution profile. the app crashes on actual test devices right at the launch? Any idea? I use the same certificate/profile and build on the other machine and the app works fine on actual devices for testing, the issue only happening on my build machine. I tried removing caches from Xcode, restart the machine... no luck

0