2

I'm running Mojave as an update from Sierra— things were easier so far until last week when TextEdit started to do a number on me by not autosaving when it normally should, and worse still, not manually saving whatever changes I'd made. As Apple put it:

The document "so-and-so.txt/.rtf(d)* could not be autosaved. Your changes will not be saved until the problem is resolved.

Uh, excuse me?? What problem do you mean? I just downloaded a few fonts prior to all this, so it couldn't have been anything I did. And I can't just duplicate this, because that won't save well either.

Is this some sorta glitch that popped back up? (I read it occurred quite often with MacOSX Mountain Lion)

  • 1
    Welcome to AskDifferent! Does it happen to all TextEdit files or only to a specific one? Can you still use "Save as" to save the file somewhere else (open the "File" menu, then press "Alt/Option" to reveal this")? – nohillside Oct 22 '18 at 5:52
  • Nope, I still get the same error. And it's been happening to all files I've got. – Ian Sherman Oct 22 '18 at 6:13
  • The error talks about auto-save, I was wondering whether you are at least able to save the document somewhere else. – nohillside Oct 22 '18 at 6:18
  • Do the answers in apple.stackexchange.com/questions/50760/… help? Does it also happen with new files? Does it happen both with files stored locally and with files stored in iCloud? – nohillside Oct 22 '18 at 6:19
  • Even if I make a new file, it can't autosave those either. – Ian Sherman Oct 22 '18 at 6:39

You must log in to answer this question.

Browse other questions tagged .