FYI, I tested this on an iPad with iOS 11 beta 2 and opening an existing
UIDocument works on the actual device - just not on the simulator. I updated my
bug report with this information.
Dave Reed
> On Jun 21, 2017, at 5:08 PM, Jonathan Hull wrote:
>
> That part is really confusing me as we
I submitted a bug report: rdar://32912183
Based on the WWDC video, it appears Apple is recommending you put an empty
document as a resource in your app and then choose the option to copy it.
The other option would be to make a new document in a temporary directory your
app can write to and the
That part is really confusing me as well (I am also using a package document).
I started by using the documents directory, but I keep getting an error that
the browser doesn’t have access. Then I switched to the temp directory, and
now it works part of the time, and the other times I still get
> On Jun 20, 2017, at 5:29 PM, Kyle Sluder wrote:
>
> On Tue, Jun 20, 2017, at 03:40 PM, davel...@mac.com wrote:
>> I'm trying out the new UIDocumentBrowserViewController in iOS 11 (using
>> the iPad simulator). I can get it to create a new document (which is a
>> file package) for my app, but t
On Tue, Jun 20, 2017, at 03:40 PM, davel...@mac.com wrote:
> I'm trying out the new UIDocumentBrowserViewController in iOS 11 (using
> the iPad simulator). I can get it to create a new document (which is a
> file package) for my app, but tapping on the document in the
> UIDocumentBrowserViewControl
I'm trying out the new UIDocumentBrowserViewController in iOS 11 (using the
iPad simulator). I can get it to create a new document (which is a file
package) for my app, but tapping on the document in the
UIDocumentBrowserViewController does not cause the delegate method
documentBrowser(_ contro
