iOS failed to launch dnsproxy network extension and no network anymore

Question

richard_wang OP

Created May ’22

Replies 3

Boosts 0

Participants 3

Hi there,

We have a batch of customer ipad running our software older version with dnsproxy. They have not been running for a while. Then it is found that these devices cannnot load dnsproxy network extension and no network access anymore.

Below is the ipad console.

iPad neagent(NetworkExtension)[220] <Error>: Failed to start extension com.***.ios-dns.ext: Error Domain=PlugInKit Code=4 "RBSLaunchRequest error trying to launch plugin com.***.ios-dns.ext(***): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x14de85170 {Error Domain=NSPOSIXErrorDomain Code=85 "Bad executable (or shared library)" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 85}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to launch plugin com.***.ios-dns.ext(***): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x14de85170 {Error Domain=NSPOSIXErrorDomain Code=85 "Bad executable (or shared library)" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 85}}}}

I guess it is because the dnsproxy provisioning profile there expires already?

In this case is there any way to retain the network access remotely? There are hundreds of them. Cannot imagine need to remove the app one by one manually.

Furthermore, is there any way to avoid such a situation: devices wakeup after not in use for some time, provisioning profile expires, not able to load dnsproxy network extension and no network anymore.

Thanks in advance for any suggestion,

Richard

Boost

Answer 1

Systems Engineer OP

Apple

May ’22

We have a batch of customer ipad running our software older version with dnsproxy. They have not been running for a while. Then it is found that these devices cannnot load dnsproxy network extension and no network access anymore. I guess it is because the dnsproxy provisioning profile there expires already?

What do you mean specifically by "older version" and "they have not been running for awhile?" For example, do you mean that you are running an older version of the operating system? Do you mean that your code signature is significantly out of date?

As the error indicates, Running Board is denying your launch because of an issue with your executable, we just need more information on specifically why your executable is deemed bad.

0

Answer 2

richard_wang OP

May ’22

Those device are running our app released a couple of years ago. If I try fresh install this old version app on a device, it will just fail with the prompt saying this app cannot be installed because its integrity could not be verified. So it should be the provisioning profile built into that app binary expire already.

Thanks Richard

0

Answer 3

DTS Engineer OP

Apple

May ’22

So it should be the provisioning profile built into that app binary expire already.

Perhaps. Did you install this app from the App Store? If so, it shouldn’t expire. OTOH, if this is In-House (Enterprise) or Ad Hoc signed, both certificate and profile expiration is possible. You can test this theory by pulling apart the profile to look at its expiry date and the expiry date of the certificates it authorises. See TN3125 Inside Code Signing: Provisioning Profiles.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1