We have over 10,000 iOS/iPadOS devices and are seeing the same thing for about a year and it's getting worse. Are you noticing the issue more when distributing apps automatically vs. from self service?

The issue seems to only be affecting our auto install apps. I was able to reproduce all of the same issues on our test server running 10.23 while our prod is on 10.18. I ran wireshark and found a couple things and sent to our network team for further analysis. I also ran conosole on an iPad and grabbed some logs. Every time that I reproduce the issue, the first error I see is "unrecognized token from <private>". I'm not sure if that's of any significance, but I see it on both test and prod while reproducing the issue.

I tested a few manual installs from Self Service and saw the same issue, so I don't believe it's limited to our automatic installs.

I'm seeing the same issue. I have a call open with Jamf. It was working fine Thursday but the next day it stopped working. Licenses are just not being applied for some reason. They are aware it's a PI and are working on a fix for me at the moment. I've said I can't wait for a Jamf update and this needs doing as soon as possible as we've just rolled out 100s of iPads for students and teachers which they can't currently use fully. Manually refreshing licenses fixes it but this is very time consuming as you can only do one at a time: Global Management > Volume Purchasing > VPP Account > Content > IOS App > Refresh the app you want.

I'm just focusing on core ones at the moment. Although we're still setting iPads up so I have to keep going back and doing the same ones. Any new iPads that get setup will not get their licenses. This is not just auto install apps. It's any apps that have been assigned after the break happened.

We are having the same issue.

Possibly an Apple Issue then as this only started happening on Friday for us?

We're in the same boat only ours was working fine until this morning (Wed). In our case it doesn't matter if the app is a required install or availble in self-service it just seems like the licenses are broken. I've gone through about 30 of the (essential) apps in VPP and performed a manual refresh but as @RLR alluded, that could take days depending on your deployment size.

If anyone hears concrete positive news from Jamf please share.

Adding us to the "me too" list - we're frantically trying to setup 1500 more iPads and have ground to a halt here because of this issue.... I think it's happening on our Macs as well but haven't dug into that yet.

When I look in my JSS logs I'm seeing tonnes of error messages about managing licenses, something like the following, only repeated thousands of times:

2020-09-09 13:01:38,125 [error] [eralPool-15] [VppCommService           ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

2020-09-09 13:01:38,161 [error] [eralPool-16] [VppCommService           ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

2020-09-09 13:01:38,281 [error] [eralPool-19] [VppCommService           ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

2020-09-09 13:01:38,385 [error] [eralPool-16] [VppCommService           ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

2020-09-09 13:01:38,386 [error] [neralPool-8] [VppCommService           ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

2020-09-09 13:01:38,500 [error] [eralPool-13] [VppCommService           ] - Error managing licenses. ErrorNumber: 9603 , ErrorMessage:Internal error

@fsjjeff I had a similar issue, here is what support asked me about it:

Have you noticed any VPP issues? With this error, we would need to enable HTTP debug logging to get more information on the root cause. Do you know if a VPP token might be in use on another server by chance?

In our case one of our VPP accounts was being using in Apple Configurator 2, and we had to reclaim the token.

@ssrussell I've got all the VPP issues ... As in nothing is installing right now and I'm just getting all those error messages . I don't think we have any of our VPP accounts logged into any Apple Configurator instances, but trying to check as I type.

@fsjjeff If you click on each one of your VPP accounts in Settings in your jamfPro instance you should see a banner at the top of the VPP account page if the token is in use. Then you can click "Reclaim token".

@ssrussell Interesting, didn't even know that was a feature. Just checked and no banner to reclaim a token, but that doesn't surprise me too much as I was pretty certain we weren't signed in with anything else.

Apple has been having some issues the last couple of weeks I've seen. Apps/books not available in ASM, ASM errors, iPads
timing out to activate to name a few. That message means that Apple hasn't issued a license to that device for that app, and with them having issues as they have been I'm not surprised.

Based on the 9603 error in the log from @fsjjeff I found this from here: https://developer.apple.com/documentation/devicemanagement/app_and_book_management/interpreting_error_codes#3232844

Receiving a 9603 Internal Error response typically indicates the VPP server couldnʼt provide timely processing. Nothing is necessarily wrong with the request. When the MDM server receives this response, it should send the current request again. If it continues to receive 9603 errors after more than five attempts, it may mean that the VPP service is unexpectedly down and further retries should be scheduled for minutes later, instead of seconds.

I've been comparing jss logs from our prod and test server. Reproducing on the test server, I see
[error] [eralPool-10] [VppCommService ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

I see this on both prod and test and was able to grab a fresh log while reproducing the error. I sent the info to support and am waiting to hear back. The initial error is pending - application is not available to install, but eventually it will install.

@ssrussell That's definitely sounding like it's more of an Apple thing than a JAMF thing .

I ran into this issue today. In my case it was because I had the app scoped to a static group that had more members then we had licenses for in Apple School manager. It was a free app, so I added a bunch more licenses, then the app started installing.

Hope that helps somebody!?

We are starting to see this as well on newly registered iPads. Typically we would see the message for around 30 minutes as the licenses were getting assigned. Now with new ones we are seeing it for days without it progressing. We have plenty of licenses available.

I have the exact same issue with auto-install apps and apps from Self Service....in the managment pane they sit there and say:
Pending - Application is not available to install

I opened a ticket on this today. Our student testing window starts Monday and only 1/3rd or so of folks actually prepped for it.

I got confirmation from higher level support that it does appear to be an Apple issue. I've been told some changes have been pushed out which will hopefully fix it, but that app installs impacted by it may still need to be refreshed at least once more. The full relevant text is below.

We've been seeing this issue in a variety of environments, and we've opened communication with Apple regarding this behavior and it looks like multiple MDM's are affected. There have been some changes pushed, so we should see some improvement soon. However, we may need to refresh each app one last time.

The following is a brief overview of what's happening on the backend, feel free to skip over this if not curious!

This issue at its root has two causes that compound on each other:

1: When Jamf Pro attempts to assign a license to a device, Apple's VPP server does assign the license, but returns an error code (9603) to Jamf Pro.

2: Jamf Pro is unaware that a license was assigned, so it attempts to assign the license again. Apple returns another error code (9616), indicating that the license in question is already assigned. Jamf Pro interprets this as a failure and continues trying.

From here: We have preliminary reports that Apple has pushed a fix to prevent their servers from returning the initial error code (9603), so new license assignments should not run into this issue.

However, the fix that was implemented will not fix license assignments that are impacted by the second of the two issues, the 9616 error code.

To fully clear out this issue, any applications that are affected may need to be refreshed again in Jamf Pro > Settings > Volume Purchasing Accounts > Click on the token in question > Content > Refresh next to the app in question.

If you do run into this issue on any apps after refreshing their licenses, let me know. We're still in the process of verifying the fix from Apple across all environments, so we'll want to catch this as soon as possible if the issue pops up again.

Hope this works

Still not working for me today. Just setup a new iPad and still getting the same error message. Jamf support said they applied a fix last night for us but this hasn't changed anything either.

I been on our test server and after a reset, I still see the "Pending-Application is not available to install", however, it is pushing the apps in a timely fashion. I am noticing a new error in the jss logs while triggering an enrollment.

2020-09-11 08:52:34,570 [error] [duledPool-0] [iceEnrollmentSyncRunnable] -

com.jamfsoftware.jss.exceptions.communication.InvalidRequestDataException: java.net.SocketTimeoutException: Read timed out

Renewed the VPP token on prod and still seeing. constant error in the jss logs.
[VppCommService ] - Error managing licenses. ErrorNumber: 0 , ErrorMessage:null

Following thread.

We have been having issues since August with a handful of our devices. Over the weekend we updated our 2,000 iPads to the latest iOS. We noticed Google Classroom was having a lot of glitches, pushed an app update. Now, all of our iPads have Google Classroom greyed our "waiting". I also have a support ticket with JAMF.

+1 I have been fighting this for over a week as well, and it is an AWFUL issue when every student and teacher are working remotely and need their apps! Sounds like some of you have been getting better advice, I had to discover the refreshing content licenses myself and a Jamf agent was telling me its likely I just doubled-up scoping and applied multiple licenses to the same devices... right...
Have not gotten anywhere on the Apple-end of this problem either! Just gets pushed higher up each day.