-
All replies
-
Helpful answers
-
Oct 1, 2015 5:00 AM in response to JohnWGIVby Pterio,I Got this feature back when i am update to ios 9.0.2
-
Jan 8, 2016 9:36 AM in response to JohnWGIVby Luigi91,(This is a post I wrote on reddit but I’m cross-posting it here in many threads because it looks like many people are facing this problem)
Hello everyone! I found a solution! It requires a bit of time but it solved the bug (which is the impossibility to download any kind of file from Safari because the “Open in” label in ANY kind of document of file is simply not showing up).
This is what I did. Not sure every single passage is necessary but now it’s working flawlessly.
- Connect the iPhone to the computer, put it in flight mode (to avoid receiving iMessages and notifications after the backup that would go lost) and do a full and encrypted backup (this way it preserves health data and keychain elements)
- Restore the iPhone. It will download the latest iOS version and erase all the content
- Once the iPhone is restored instead of restoring your data, choose the setup as new option from the iPhone screen (not from iTunes, but from the phone). To go more quickly I connected to Wi-Fi but skipped everything (including signing in to iCloud, and TouchID and passcode, there’s an option to do that) - so it prevents linking to iMessage as well (we don’t want that for now)
- Now that you got a fresh copy of iOS open Safari and check that it’s working properly - I googled “pdf example” and opened the first two results - now it was handling the “Open in iBooks” correctly.
- Connect the iPhone to your computer again if you disconnected it and it will ask you if you want to set it up as new or restore from a backup. Choose the backup you did in #1 (it should be already selected)
- Wait for restore to be completed. You’ll have to put your Apple password several times because… I don’t know why, but iOS keeps asking it several times
- While you wait for every app to be loaded you can already try to open Safari and look for a PDF or regular document, now everything should work just fine!
Hope it helps.
-
Jan 8, 2016 10:00 AM in response to Luigi91by Kilgore-Trout,Or, as already stated in this thread, simply update to iOS 9.2, which fixed the issue.
-
Jan 8, 2016 10:03 AM in response to Kilgore-Troutby Luigi91,Except that it didn't, since I had this problem on 9.2 and even updates to the 9.2.1 beta.
-
Jan 8, 2016 11:04 AM in response to Luigi91by Kilgore-Trout,Issues related to beta versions of iOS should not be presented here. And it should be obvious that the 9.2 update took care of the folks on the thread (and pretty much everyone else) three months ago. Doing a full restore simply isn't necessary to fix this. What you were experiencing was something else (and quite possibly related to the beta software).
-
Jan 8, 2016 11:20 AM in response to Kilgore-Troutby Luigi91,What's your problem with me giving a solution to a problem? I WAS ON 9.2 AND I HAD THIS ISSUE (yes, I'm shouting), I updated to the 9.2.1 beta just to find out if the problem was solved, but it wasn't. Maybe 9.2 solved the problem for these people, but it didn't for me, so if anyone reads can try what solved the problem FOR ME. Ok?