Home
%3CLINGO-SUB%20id%3D%22lingo-sub-672738%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-672738%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20this%20%22different%20channel%22%3F%20I%20would%20love%20to%20know%2C%20I%20have%20been%20pulling%20my%20hair%20out%20for%20a%20while%20as%20my%20company%20just%20has%20a%20flurry%20of%20new%20hires%20start.%20I%20found%20the%20workaround%20to%20deploy%20to%20devices%20on%20my%20own%20last%20week%2C%20but%20would%20love%20to%20know%20how%20to%20have%20a%20user%20accept%20the%20VPP%20invitation%20without%20the%20AppStore%20App.%20Thanks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678251%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678251%22%20slang%3D%22en-US%22%3E%3CP%3ENice%20of%20you%20to%20acknowledge%20the%20issue%20after%20I%20was%20fighting%20it%20for%20a%20long%20time%20now%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678554%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678554%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F35582%22%20target%3D%22_blank%22%3E%40Andrew%20Allston%3C%2FA%3E%20we%20are%20going%20to%20update%20the%20writeup.%20I%20was%20thinking%20we%20could%20get%20the%20terms%20across%20in%20a%20different%20mechanism%2C%20but%20in%20talking%20back%20with%20one%20of%20our%20Apple%20PM's%2C%20he%20said%20that%20can%20be%20tough%20so%20best%20approach%20would%20be%20to%20try%20the%20device-licensing%20as%20a%20workaround.%20Hope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719977%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719977%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20any%20updates%20as%20to%20when%20this%20will%20be%20resolved%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-778444%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778444%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20also%20have%20this%20problem.%20Any%20updates%20to%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-778445%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778445%22%20slang%3D%22en-US%22%3E%3CP%3ETickets%20still%20open%20with%20both%2C%20Microsoft%20and%20Apple.%20As%20of%20this%20morning%20both%20say%20no%20updates...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-784631%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-784631%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F173233%22%20target%3D%22_blank%22%3E%40Jacob%20Heinikel%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F273129%22%20target%3D%22_blank%22%3E%40Berendsen22061993%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F105949%22%20target%3D%22_blank%22%3E%40Vojin%20Lekovic%3C%2FA%3E!%3C%2FP%3E%0A%3CP%3EThank%20you%20all%20for%20your%20feedback!%20We've%20updated%20this%20blog%20with%20our%20most%20recent%20update.%20Also%20including%20our%20update%20below%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20been%20working%20closely%20with%20Apple%20to%20resolve%20this%20issue.%20We%20see%20in%20the%20iOS%2013%20Beta%205%20release%20notes%20what%20appears%20to%20be%20a%20fix!%3C%2FP%3E%0A%3CP%3EWe%E2%80%99ll%20continue%20our%20testing%2C%20too.%20You%20can%20read%20more%20about%20what%E2%80%99s%20included%20in%20Apple%20beta%20documentation%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdeveloper.apple.com%2Fdocumentation%2Fios_ipados_release_notes%2Fios_ipados_13_beta_5_release_notes%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.apple.com%2Fdocumentation%2Fios_ipados_release_notes%2Fios_ipados_13_beta_5_release_notes%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785167%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785167%22%20slang%3D%22en-US%22%3E%3CP%3EDear%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune%20Support%20Team%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reaction!%3C%2FP%3E%3CP%3EIf%20I%20understand%20correctly%20the%20fault%20lies%20in%20the%20Apple%20iOS%20update%3F%20If%20that%20is%20the%20case%20we'll%20wait%20for%20the%20iOS%2013%20to%20become%20available.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3ESjoerd%20Berendsen%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857320%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857320%22%20slang%3D%22en-US%22%3E%3CP%3EApple%20says%20that%20this%20is%20Intune%20issue.%20No%20beta%20of%20iOS%2013%20that%20I%20have%20loaded%2C%20and%20I've%20done%20them%20all%2C%20has%20addressed%20this%20issue.%20I%20do%20NOT%20want%20to%20use%20%22device%22%20licensing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdiscussions.apple.com%2Fthread%2F250394562%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdiscussions.apple.com%2Fthread%2F250394562%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20we%20have%20some%20clarification%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaciej%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-668980%22%20slang%3D%22en-US%22%3EResolved%20-%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-668980%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CEM%3EUpdated%2011%2F6%2F19%3A%20We%20have%20confirmation%20from%20Apple%20and%20from%20customers%20that%20this%20is%20now%20resolved.%26nbsp%3B%3C%2FEM%3E%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CEM%3EUpdated%2011%2F1%2F19%3A%20We%20are%20continuing%20to%20work%20closely%20with%20Apple%20to%20resolve%20the%20issue.%20If%20you%20have%20an%20open%20ticket%20with%20Apple%2C%20please%20direct%20message%20us%20so%20that%20we%20can%20provide%20you%20the%20bug%20number%20to%20reference%20for%20this%20issue.%3C%2FEM%3E%3CSTRONG%3E%3CBR%20%2F%3E%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EThere%E2%80%99s%20a%20known%20issue%20we%E2%80%99ve%20heard%20from%20a%20few%20customers%20and%20also%20seen%20documented%20by%20other%20MDM%20providers.%20Apple%20has%20also%20been%20notified%2C%20but%20no%20word%20on%20their%20resolution.%20In%20iOS%2012.2%20and%20higher%2C%20for%20MDM-managed%20devices%20using%20user-licensed%20VPP%20apps%2C%20end%20users%20will%20not%20be%20able%20to%20accept%20or%20cancel%20Terms%20and%20Conditions%20when%20accessing%20a%20VPP%20app%20for%20the%20first%20time.%20As%20such%2C%20app%20installations%20that%20require%20terms%20and%20conditions%20may%20fail%2C%20as%20they%20don%E2%80%99t%20appropriately%20get%20an%20accept%20or%20cancel%20response%20from%20the%20user%20on%20the%20device.%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EAs%20a%20workaround%2C%20you%20can%20use%20device%20licensing%20when%20deploying%20VPP%20apps%20instead%20of%20a%20user%20license.%20Device%20licenses%20do%20not%20require%20terms%20and%20conditions.%20Alternatively%2C%20you%20can%20provide%20terms%20and%20conditions%20through%20a%20different%20channel%20than%20delivered%20with%20the%20app.%20You%20can%20switch%20from%20user-based%20apps%20to%20device-based%20apps%20through%20the%20guidance%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fintune%2Fvpp-apps-ios%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fintune%2Fvpp-apps-ios%3C%2FA%3E.%20%26nbsp%3B%3CBR%20%2F%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EBlog%20post%20updates%3A%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E7%2F31%2F19%3A%26nbsp%3BWe%20have%20been%20working%20closely%20with%20Apple%20to%20resolve%20this%20issue.%20We%20see%20in%20the%20iOS%2013%20Beta%205%20release%20notes%20what%20appears%20to%20be%20a%20fix!%20We%E2%80%99ll%20continue%20our%20testing%2C%20too.%20You%20can%20read%20more%20about%20what%E2%80%99s%20included%20in%20Apple%20beta%20documentation%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdeveloper.apple.com%2Fdocumentation%2Fios_ipados_release_notes%2Fios_ipados_13_beta_5_release_notes%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.apple.com%2Fdocumentation%2Fios_ipados_release_notes%2Fios_ipados_13_beta_5_release_notes%3C%2FA%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E9%2F27%2F19%3A%20We%20tested%20on%2013.1%20and%20unfortunately%2C%20we're%20still%20seeing%20the%20error.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-668980%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20customer%20feedback%20this%20is%20now%20resolved.%20Read%20this%20support%20tip%20for%20a%20known%20issue%20with%20T%26amp%3BC%20and%20iOS%2012.2%20and%20higher.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-992869%22%20slang%3D%22en-US%22%3ERe%3A%20Resolved%20-%20Known%20Issue%3A%20iOS%2012.2%2B%20Terms%20and%20Conditions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-992869%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20IS%20now%20resolved%2C%20but%20what%20better%20clarification%20would%20be%20is%20that%20its%20resolved%20in%20iOS%2013.2%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Updated 11/6/19: We have confirmation from Apple and from customers that this is now resolved. 
 
Updated 11/1/19: We are continuing to work closely with Apple to resolve the issue. If you have an open ticket with Apple, please direct message us so that we can provide you the bug number to reference for this issue.
 
There’s a known issue we’ve heard from a few customers and also seen documented by other MDM providers. Apple has also been notified, but no word on their resolution. In iOS 12.2 and higher, for MDM-managed devices using user-licensed VPP apps, end users will not be able to accept or cancel Terms and Conditions when accessing a VPP app for the first time. As such, app installations that require terms and conditions may fail, as they don’t appropriately get an accept or cancel response from the user on the device.
 
As a workaround, you can use device licensing when deploying VPP apps instead of a user license. Device licenses do not require terms and conditions. Alternatively, you can provide terms and conditions through a different channel than delivered with the app. You can switch from user-based apps to device-based apps through the guidance here: https://docs.microsoft.com/intune/vpp-apps-ios.  
 
Blog post updates:
10 Comments
Occasional Contributor

What is this "different channel"? I would love to know, I have been pulling my hair out for a while as my company just has a flurry of new hires start. I found the workaround to deploy to devices on my own last week, but would love to know how to have a user accept the VPP invitation without the AppStore App. Thanks in advance.

Senior Member

Nice of you to acknowledge the issue after I was fighting it for a long time now :)

@Andrew Allston we are going to update the writeup. I was thinking we could get the terms across in a different mechanism, but in talking back with one of our Apple PM's, he said that can be tough so best approach would be to try the device-licensing as a workaround. Hope this helps.

New Contributor

Are there any updates as to when this will be resolved?

New Contributor

We also have this problem. Any updates to it?

Senior Member

Tickets still open with both, Microsoft and Apple. As of this morning both say no updates...

Hello @Jacob Heinikel@Berendsen22061993, @Vojin Lekovic!

Thank you all for your feedback! We've updated this blog with our most recent update. Also including our update below:

 

We have been working closely with Apple to resolve this issue. We see in the iOS 13 Beta 5 release notes what appears to be a fix!

We’ll continue our testing, too. You can read more about what’s included in Apple beta documentation here: https://developer.apple.com/documentation/ios_ipados_release_notes/ios_ipados_13_beta_5_release_note...

New Contributor

Dear @Intune Support Team ,

 

Thanks for the reaction!

If I understand correctly the fault lies in the Apple iOS update? If that is the case we'll wait for the iOS 13 to become available. 

 

Greetings,

Sjoerd Berendsen

 

Senior Member

Apple says that this is Intune issue. No beta of iOS 13 that I have loaded, and I've done them all, has addressed this issue. I do NOT want to use "device" licensing.

 

https://discussions.apple.com/thread/250394562

 

Please can we have some clarification?

 

Maciej

Senior Member

The issue IS now resolved, but what better clarification would be is that its resolved in iOS 13.2 release.