Posts

Post not yet marked as solved
7 Replies
I have the same problem , compounded by the fact that my MacbookPro bricked when I tried to update it it Big Sur as suggested. Anyone got a lead on the old ispw "UniversalMac11.020A5374i_Restore.ipsw" ?
Post not yet marked as solved
12 Replies
Kind of unbelieveable, but it DID work! old files in there from 2008 or so! OTOH, a useful error message would have helped!
Post not yet marked as solved
94 Replies
I too am hit by this issue.I have my own custom UTI for my own files which I serve from a web page.in iOS 12, Safari puts up "Open in.." when tapping it. Choosing Open in copies the file into my apps Documents dir in a special Inbox subdriectory, where I can read it via the URL. If I use the UIDocumentPickerViewController way , it says "Copy to [my app]", which again puts it in the Inbox.in iOS 13, it demands to be downloaded instead. Trying to read the downloaded file results in it not being owned by my app and illegible. In fact, I can't figure out what anyone can do with the download's file:// URL that is given to the app in that situation. If I go to the Download part of Files and move (copy really) it into my app's Document dir, it's found.I've tried a great number of the techniques mentioned, but the truth is: works in iOS 12 perfectly, decides it wants to use the new file system in iOS 13, but still doesn't give access.
Post not yet marked as solved
18 Replies
My main problem with this is that the WK calls they replaced UIWebView with don't work well on iOS 9. I try to have my software work on older devices like iPad 3 that are stuck on iOS9.3. If they are just checking for calls to UIWebkit, then I can't do a gestalt check onthe OS to swap between ways of presenting web content. (Actually, I can if I use low-level objC calls that Apple reviewers wouldn't see if they don't run under iOS 9).
Post not yet marked as solved
33 Replies
I hope iOS13.1 really fixes this via subclassing editingInteractionConfiguration. Why this should be on be default for anything but UITextFields and Areas is a mystery to me. Until then, I've found that putting down fingers one at a time without moving them , with about 1/2 second between them ("one-uh-two-uh-three-uh") will send out the three fingered touch message as it's done since 2006. I also use 4 finger taps , and that's a similar situation.