App is not upgrading with Network Extension in iOS 13 in Test flight

Question

Created Jul ’20

Replies 5

Boosts 0

Participants 4

Hi
We are building a VPN app (PacketTunnelProvider) and allowing users to install the app through test flight and app upgrade works seamlessly without VPN, but immediately after enabling the VPN, we are not able to get app upgraded with the progress bar in test flight stuck at 90 percent and now app is not usable after that but VPN is still working.
We are not noticing the issue on ios 12.4.1 version but facing the issue on iOS 13 versions.
On looking through console app during upgradation process we are noticing a below recurring log message.

Code Block Error acquiring hold on plugins for <bundle_identifier>: Error Domain=PlugInKit Code=14 "plugins are busy" UserInfo={busyPlugInUUIDs=({
        XPCExtensionBundleIdentifier = "<bundle_identifier>.tunnel";
    }
), NSLocalizedDescription=plugins are busy}

Could someone please help us in resolving the issue.

Answered by DTS Engineer in 887707022

Bugs like this crop up pretty frequently. There’s nothing your app can do to resolve them. The system is responsible for your updating your app; you’re not involved in that process at all.

Given that, the only path forward is to file a bug explaining the exact circumstances under which you’re seeing the problem. Make sure to attach a sysdiagnose log taken immediately after the update fails. If possible, enable additional on the device before you start the test. Specifically, follow the App Store and VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page.

Please post your bug number, just for the record.

Back in 2020 grtteja wrote:

Are these bug reports publicly available

No.

Bug reports that you file are only visible to you, other members of your team [1], and relevant folks at Apple. For general info on this whole process, see Bug Reporting: How and Why?

A bug number is not in and of itself private info, which is why Apple shares them all the time — for example, in our release notes — and why I encourage developers to post them here on the forums.

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

[1] If you opt in to that. Search Bug Reporting: How and Why? for team to learn more about that.

Boost

Answer 1

Systems Engineer OP

Apple

Jul ’20

This looks like there is a potential issue when updating the existing host app and the Network Extension in not being updated because it is currently in-use. Notice the "plugins are busy," and "Error acquiring hold on plugins" messages. This should be captured in a bug report. Please open a bug report and provide any further logs, screen shots, or videos that you may have reproducing the issue. One you have done so please respond back with the Feedback ID and I can copy myself on it for further updates.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

0

Answer 2

grtteja OP

Jul ’20

Thanks Matt for acknowledging the issue. I have few questions on raising bug report.
Are these bug reports publicly available because we don't want to disclose our app specific screenshots, logs etc.
Would it be okay to share apple id of the app which you can use to track ?

0

Answer 3

Systems Engineer OP

Apple

Jul ’20

Once you have the bug report opened, go ahead and send the Feedback ID to me in my email address attached to my signature. Make sure to reference this post in your email.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

0

Answer 4

dah_ OP

2d

Hi,

we are seeing this exact same issue with iOS 26.4.2 + the current iOS 26.5 beta version. We can not update our App anymore having the VPN tunnel running! Removing the VPN Profile instantly resolves the issue.(which isn't a solution)

installcoordinationd:

Failed to acquire termination assertion

RBSRequestErrorDomain Code=5 "Error acquiring hold on plugins"

PlugInKit Code=14 "plugins are busy"

busyPlugInUUIDs = ******.NetworkExtension

Same build is perfectly updating on e.g iOS 17.* or IOS 18.* devices.

0

Answer 5

DTS Engineer OP

Apple

1h

Recommended

Bugs like this crop up pretty frequently. There’s nothing your app can do to resolve them. The system is responsible for your updating your app; you’re not involved in that process at all.

Given that, the only path forward is to file a bug explaining the exact circumstances under which you’re seeing the problem. Make sure to attach a sysdiagnose log taken immediately after the update fails. If possible, enable additional on the device before you start the test. Specifically, follow the App Store and VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page.

Please post your bug number, just for the record.

Back in 2020 grtteja wrote:

Are these bug reports publicly available

No.

Bug reports that you file are only visible to you, other members of your team [1], and relevant folks at Apple. For general info on this whole process, see Bug Reporting: How and Why?

A bug number is not in and of itself private info, which is why Apple shares them all the time — for example, in our release notes — and why I encourage developers to post them here on the forums.

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

[1] If you opt in to that. Search Bug Reporting: How and Why? for team to learn more about that.

0