That's exactly what I was looking for, thanks!
Post not yet marked as solved
Thanks for posting this. Adding "UTTypeConformsTo" is what I needed for my app to show up in sharing action sheets in iOS 13.When Safari downloads one of my custom files in iOS 13, it no longer prompts if I want to open that file in my app like it used to. I hope that ability comes back since I'm not sure users will know to look at the downloaded file and then do a share action.
Thank you for confirming.
The reason I use Data and not an array is because the actual application where this crash started occurring in Swift 4.1 uses Data for reasons outside the scope of this post. I posted a distilled version of the code here just to illustrate the issue I'm experiencing. Thanks again for your help and insights.
Thanks, that makes sense. But I think the code was working in Swift 4.0 for some reason. Perhaps it shouldn't have been, and now 4.1 fixes this. In my actual implemtation, I pass the range to a function that accepts a Data argument like so:func f(_ data: Data) {
print(data.startIndex)
}
let d0 = Data(bytes: [10, 11, 12, 13, 14, 15])
let d1 = d0[4...5]
f(d1)
f(Data(d1))Inside function "f" I access the data, and this is where the index behavior has changed, if I'm not mistaken. The playground output from the above is now:4
0
Post not yet marked as solved
Looks like this is fixed in iOS 11.2.
Post not yet marked as solved
Same here. I can't find a way to perform a multiple select in the UI.
Thank you for the link. I can see how not allowing the creation of subdirectories could be an intentional change with this in mind. Thanks again, I appreciate the help.
Thank you for taking the time to reproduce this. I've filed a bug as requested (34885748). If you have any ideas about a workaround or a preferred location to store data on the file system, please let me know.
Yes I tried passing false for withIntermediateDirectories, and it made no difference. Creating a directory under "Library" is pretty boilerplate code that I've used in projects for years, following the guidelines communicated in the last paragraph here:https://developer.apple.com/library/content/qa/qa1699These are the results from different environments:1. All simulators in all environments succeed, regardless of target platform or OS version.2. Running on an iOS 11 iPad with the deployment target set to iOS 11 - success.3. Running on an iOS 11 iPad with the deployment target set to iOS 9.3 - success.4. Running on an iOS 9.3 iPod touch with the deployment target set to iOS 9.3 - success.5. Running on a tvOS 11 device with the deployment target set to tvOS 11 - FAILS.6. Running on a tvOS 11 device with the deployment target set to tvOS 10.2 - FAILS.I'm unable to try Xcode 8 with a tvOS 11 device since Xcode 8 doesn't support it, but I had been using Xcode 8 with tvOS 10 and everything worked fine. Things broke when I upgraded to Xcode 9. What I don't know is if the combination of Xcode 9 and tvOS 10.2 would succeed or not.This is a blocking issue since my app can't write anything to the file system, which it is heavily dependent on. I've never run into anything like this before.
