PDF Reader 'GoodReader' Removes iCloud Drive Functions to Comply with 'Mandatory' Apple Policy [Updated]

[grahamperrin]

directory/folder hierarchy restrictions/guidelines

… I remember app containers were said to be restricted to one level only back in October …

Is there a publicly available point of reference for that? In the developer.apple.com domain, maybe?

Whilst seeking that information, a few other things caught my eye.

https://developer.apple.com/library....html#//apple_ref/doc/uid/TP40012094-CH6-SW14

https://developer.apple.com/library...d.html#//apple_ref/doc/uid/TP40012094-CH2-SW9

https://developer.apple.com/library...p.html#//apple_ref/doc/uid/TP40014969-CH3-SW5 – I doubt that anyone will choose to use a watch to view PDF content, I'm thinking more broadly about any environment in which it may be undesirable – or necessary – to limit or prevent a user-created directory hierarchy.

 

[Trahearne]

Is there a publicly available point of reference for that? In the developer.apple.com domain, maybe?

Whilst seeking that information, a few other things caught my eye.

https://developer.apple.com/library....html#//apple_ref/doc/uid/TP40012094-CH6-SW14

https://developer.apple.com/library...d.html#//apple_ref/doc/uid/TP40012094-CH2-SW9

https://developer.apple.com/library...p.html#//apple_ref/doc/uid/TP40014969-CH3-SW5 – I doubt that anyone will choose to use a watch to view PDF content, I'm thinking more broadly about any environment in which it may be undesirable – or necessary – to limit or prevent a user-created directory hierarchy.

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

According to the thread, app containers are currently limited to one level of subdirectories, while user-created folders outside the app containers are unlimited. This behaviour can be validated in Finder on the Mac and also Byword for iOS: neither one lets you create more than one level of subdirectory in the iCloud app container. As a side note, one may workaround this by pre-builting your folder structure and drag them into the app container.

 

[grahamperrin]

Workarounds, loss of coordination

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

According to the thread, app containers are currently limited to one level of subdirectories, while user-created folders outside the app containers are unlimited. This behaviour can be validated in Finder on the Mac and also Byword for iOS: neither one lets you create more than one level of subdirectory in the iCloud app container.

Thanks, I see, for example, advice from léonie:

"… ignore the predefined folders for Pages, Numbers, Keynote, Preview and store your documents in a custom folder hierarchy …"​

Yosemite-friendly advice such as that is well intended. However, using Mavericks to create a subdirectory in the iCloud directory for Pages goes hand in hand with the loss of coordinated content for Pages 5.2.2 (and Numbers, and so on) …

… one may workaround this by pre-builting your folder structure and drag them into the app container.

… that's a limited workaround, because Pages on Mavericks has no direct access. Every launch of the app begins with an apology for the incompatibility:

Coordinated content:

Loss of coordination:

– Pages 5.2.2 can not see the item that I dragged into the subfolder, neither can it see anything beyond its uncoordinated container.

That iCloud topic in Apple Support Communities mentions neither Mavericks nor upgrading. The advice there might be unexpectedly troublesome to a Mavericks reader who is not technically adept enough to get the big picture.

 

[Trahearne]

Thanks, I see, for example, advice from léonie:

"… ignore the predefined folders for Pages, Numbers, Keynote, Preview and store your documents in a custom folder hierarchy …"​

Yosemite-friendly advice such as that is well intended. However, using Mavericks to create a subdirectory in the iCloud directory for Pages goes hand in hand with the loss of coordinated content for Pages 5.2.2 (and Numbers, and so on) …



… that's a limited workaround, because Pages on Mavericks has no direct access. Every launch of the app begins with an apology for the incompatibility:

Image

Coordinated content:

Image

Loss of coordination:

Image

– Pages 5.2.2 can not see the item that I dragged into the subfolder, neither can it see anything beyond its uncoordinated container.

That iCloud topic in Apple Support Communities mentions neither Mavericks nor upgrading. The advice there might be unexpectedly troublesome to a Mavericks reader who is not technically adept enough to get the big picture.

I'm not so sure about how iWork on Mavericks will behave with iCloud Drive, and the workaround hasn't been tested on iWork yet but works with GoodReader, Documents 5 and Byword. You may want to try to drag a file onto a file to create a folder in the Documents in the Cloud picker.

 

[grahamperrin]

Loss of coordination versus the value of organisation

… You may want to try to drag a file onto a file to create a folder in the Documents in the Cloud picker.

A nice idea but since coordination has been lost, there's no longer a reason to attempt organisation in the context of iCloud.

 

[samcraig]

All I have to add is that goodreader was the app (beyond media consumption) that originally made me more productive on my first iPad. I am glad they have continued to find success, and I do hope they are able to reinstate functionality.

 

[APlotdevice]

Hmm, I can see the latest update, but it won't let me install it.

 

[johnnyturbouk]

Unbelievable, I think Apple goes out their way to annoy consumers and developers.

They will add it in three years, then boast about the amazing and magical ability to add new folders to icloud! Well done apple!!

 

[grahamperrin]

They will add it in three years …

I doubt it. I expect iCloud Drive to remain limited in some environments.