iOS 11.3, iWork 4.0 Apps, and iCloud Drive

[JoshRouthier]

Wondering if anyones seen similar behavior from their supervised iOS devices running iOS 11.3 and iWork 4.0 apps. Device is signed into iCloud, has the iCloud Drive and iWork iCloud Drive options turned on, but in the Settings of each app, I cannot choose iCloud Drive as a Default Storage option. I was first alerted to this yesterday when I opened up Pages and received a message stating my Default Storage option was no longer available and to choose another.

I checked my Restrictions Config Profile, but it allows iCloud Drive. Even if I remove the device from the scope of my Restrictions profile, I'm still not able to see iCloud Drive as a Default Storage option.

The only time iCloud Drive comes back as a Default Storage option is if I unmanage the device. So it does appear to be something that my JSS is restricting, just not sure what/how/why. JSS is 10.2.2 hosted.

[JoshRouthier]

Heard back from Jamf Support about this today. They are able to replicate the problem, and are looking into a fix. In short it looks like this happens when a device running iOS 11.3 has Pages, Numbers, or Keynote managed by Jamf. Anyone else seeing this behavior?

[MFRA]

Hi. I've got exactly le same problem.
I found that by deleting the enrollment profile, iCloud comes back...
This problem appears with iOS 11.3 and 11.3.1.

Thanks to help.

[MFRA]

Same problem for me since ios 11.3
By removing the enrôlement profil, iCLOUD is back...
I Think, this is a jamf bug.

[cdenesha]

Is there a Product Issue number?

[MFRA]

Jamf Pro VERSION
10.3.1-t1522933524

[cdenesha]

I'm sorry - is it fixed in this version or still a problem? If still a problem, can I have the PI-NNNNN number for monitoring Release Notes for the fix?

ty!

[JoshRouthier]

Pinged my support rep on this case for the PI number. Will post it as soon as I have it!

[JoshRouthier]

Got word back from my support rep. They informed me that Jamf doesn't currently have a Product Issue filed for this, but do have an open case with Apple. The support rep stated "We're certainly not pointing fingers but on our side we have nothing we can do other than unmanage the apps to have the iCloud option."

Certainly not the most encouraging update on this. If you are experiencing this issue, I have been told that it would be good to contact Apple to mention you are having this problem, as there doesn't appear to be anything you can do to fix it, OTHER than unmanaging the apps.

[cdenesha]

I've submitted a ticket to Apple Enterprise, we'll see what they know.

chris

[JoshRouthier]

Heard back from my Jamf support rep, and they told me that they've created a 3rd-Party Product Issue, PI-005802. The rep said to reference this when calling Apple regarding this problem.

[thejenbot]

A jamf support specialist I'm working with just informed me that apps set to Install automatically and/or have the box checked to make app managed if currently installed as unmanaged results in loop when iOS 11.3 device responds back with incorrect identifier. We have opened up an Apple Radar ticket on this issue, 100505138618, and I would recommend that you reach out to Apple referencing this number to bring more attention to the issue. We are currently working alongside Apple to get this issue resolved. In the mean time our workaround is to uncheck the setting "Make app managed if currently installed as unmanaged" in the app configurations. He was able to provide me with a list of all apps with that setting enabled; additionally, since we are cloud hosted, he let me know that the online services team can turn this setting off in mass for us rather than us having to do it manually (which is nice because we have a huge list...).

[cdenesha]

Hello,

Apple Enterprise can duplicate the behavior and have sent it over to Engineering. Workaround: press Browse on the bottom right to bring up the Files sidebar, select iCloud Drive, choose the Pages folder, and you can now work with existing iCloud Drive documents and create new ones with the plus sign.

chris

[JoshRouthier]

Thanks for the update. I hadn't heard back from Apple yet after my initial reach out to them.

[MFRA]

This is the solution (that I don’t like)

[JoshRouthier]

Just got off the horn with Apple Enterprise Support. Tech told me that Engineering has been able to reproduce the issue, and has issued it as an official bug. No ETA for resolution, but Tech did say to keep an eye out on future updates. Best I got for now

[JoshRouthier]

Not sure if anyone else has heard from their Apple reps about this, but the last I heard from mine was that Engineering was able to reproduce the issue, and it would likely be a fix in an "upcoming" iOS update. Needless to say with yesterdays drop of iOS 11.4, this issue has NOT been fixed. Hoping we get a minor 11.4.x patch that addresses this.

[JoshRouthier]

Just wanted to chime in that if you are part of Apple Developer program, you may want to take a look at the latest iOS 11 betas!

[MFRA]

Do you mean that the proble; is solved in the last beta version ?

[JoshRouthier · Accepted solution]

iOS 11.4.1 solves this issue. I would recommend updating your devices to iOS 11.4.1 and make sure it is working for you as well.