Pages problem since iOS 17
Ever since installing iOS 17 (on my iPad) I’ve been unable to Rename a document.
Any ideas?
iPad Pro (2nd generation)
Ever since installing iOS 17 (on my iPad) I’ve been unable to Rename a document.
Any ideas?
iPad Pro (2nd generation)
Reply to : heolesgyn Pages App iOS 17
Hi heolesgyn ,
You are not alone my friend , I have read an unprecedented amount of disastrous news for iOS 17 . Folks can't copy & past , some can't export , edit , use headers & footers etc. and some have documents that have gone missing all together .
My suggestions : wait for an update to fix it or go back to iOS 16 , and don't be in a hurry to install the next version . I purposely waited after reading all of the complaints about it .
⏳
Hello heolesgyn,
Thank you for reaching out to Apple Support Communities, and we'll be happy to help in any way we can. We understand you're having issues with renaming documents. Try the steps here to see if they reoslve the issue: Save and name a document in Pages on iPad
We hope this helps.
Cheers!
SteelCityAnne wrote:
Hi heolesgyn ,
You are not alone my friend , I have read an unprecedented amount of disastrous news for iOS 17 . Folks can't copy & past , some can't export , edit , use headers & footers etc. and some have documents that have gone missing all together .
That assumption is rather like going into an emegency room, seeing all the sick people and deciding that everyone in the city is sick. No, there is really not an "unprecedented amount of disastrous news for iOS 17". What we're seeing is about average for a major update. Most people are not having problems or are having minor problems.
wait for an update to fix it or go back to iOS 16 , and don't be in a hurry to install the next version . I purposely waited after reading all of the complaints about it .
When an update is released, it may well fix problems. **, there will be people with complaints about it. As for going back to iOS 16, that's not possible. Downgrading has never been supported.
If you're having problems with iOS 17, submit feedback to Apple:
That will help them determine where to focus their energy.
Hello heolesgyn,
Thanks for checking. Please contact Apple Support to investigate this with you.
Cheers.
Thank you for your response.
I am aware of how to Rename a document - and it worked flawlessly prior to installation of iOS 17.
However, since then it hasn’t worked and the system generates a message which states: “The requested operation couldn’t be completed because the feature is not supported. The requested operation is not supported”.
Please help!
Agreed. I have had no problems whatsoever with IOS17 on my iPhone or Mac Sonoma on my MacBook Air..... each time there is an update I hear about problems but I have never personally experienced any since my days upgrading after buying my first Macs in 1993 and first iPhones around 2010.
Reply IdrisSeabright
I didn't have a preconceived idea and I'm not assigning fault to the upgrade to get out of figuring out how to resolve the issue . I read about them everywhere I searched for
iOS 17. , including this community :
I'm able to share more examples if you'd like .
I'm going to install the update , if everything is messed up , I'll ask you how to fix it .
IdrisSeabright
I owe you an apology Idris , sorry I was sarcastic , the update worked out fine .
It's been only a day , but I'm not foreseeing any problems so far .
I actually gained space … from 3.2 GB to 3.1 GB of iCloud storage ! I also realized that all of the stuff that I removed to make space wasn't necessary to keep anyway .
💐
I've been active in this forum for over twenty years. So, when I say iOS 17 is not a catastrophe, it's because I've seen lots of operating systems get released. Posting screenshots of a dozen or so examples or issues doesn't make iOS 17 an enourmous problem. Remember, this is the emergency room. Yes, most of the people who post are are doing so because they have problems. All of the millions of people who don't have these problems are off doing something else and not posting here.
All that being said, if you are the person having the problem, it's not much comfort. I'm really glad to hear that you got things figured out.
Thanks for posting this statement - I have had absolutely no problems with IOS17 or any previous OS on my phone or on my laptop or my iPads..... occasionally I post asking how to do something in particular
notlimey wrote:
Thanks for posting this statement - I have had absolutely no problems with IOS17 or any previous OS on my phone or on my laptop or my iPads..... occasionally I post asking how to do something in particular
I've certainly had problems with every device I've ever bought from Apple. Most have been minor. Many have been the result of my not understanding how a feature worked. I've been fortunate that all of my hardware issues except for the cracked iPhone screen have been covered under warranty.
I, like many people, was quite put out when I discovered that iOS 17 removed the ability to use custom text tones. It was either a mistake or Apple reconsidered and it was restored under iPhone 17.1. I'm currently having some issues with unlocking my MBA running Sonoma with my Watch and with Touch ID.
I would never go so far as to say Apple makes flawless hardware or software. No company does.
People have problems. They have them with iOS 17, 16, 15, with Sonoma, and Ventura. If people report they are having problems here, I believe them. What frustrates me is when they also come with a preconceived idea about the cause of the problem. It makes troubleshooting incredibly challenging. I do understand that it's far easier to say that it's all the fault of the upgrade rather than to do the often annoying and tedious work of actually figuring out how to resolve the issue.
iOS 17 is not without it's issues. The most notable one for me is that Apple removed, either accidently or with intent, the ability to use custom text tones. Hopefully, that will change with a future update. And there were issues for some people with some of the iPhone 15 series getting hot. The iOS 17.0.3, however, seems to have largely resolved that.
Pages problem since iOS 17