Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Emergency: keynote file damaged and can't open

Emergency:


I just finished a 60 slides keynote, then I tried to open it in my iPhone to practice.


However, when opening the file, the iOS version keynote crashed.


I was surprised. Then, I go back to macOS keynote, trying to open the file, but it can not either.


The macOS keynote says "the file is damaged and can't be opened."


The file is stored in iCloud, surprisingly, the historical versions also don't work.


User uploaded file


Possible reason:


Today, I just updated the IOS keynote to the latest version, the macOS one remains the older version. I suspect there is a bug in the new IOS version keynote that damages the file.


I updated my macOS keynote to the latest one, but it does not work.


Emergency:


I have to give the presentation tomorrow, and that is my PhD defense. I have no time, and not possible to make all the slides and animations again.


I tried to rename it to zip, extract, and compress again, it does not work.

null-OTHER, macOS High Sierra (10.13.6), Keynote

Posted on Oct 2, 2018 9:03 AM

Reply
10 replies

Oct 2, 2018 5:19 PM in response to CaptMrgnX

The iCloud.com keynote also crashes.



Screenshot:


User uploaded file


Detail error message:


Server reply error when fetching document: Unexpected server error when fetching document == Environment == URL: https://www.icloud.com/keynote/0vWPP5thP3bJmLZkA8B2ptgpA#2018.10_PHD_pre-defense _2 UA String: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Date: Wed, 03 Oct 2018 00:15:43 GMT Build environment: production Asset URL: https://p48-iwres.icloud.com:443/asset/ Res URL: https://p48-iwres.icloud.com:443/iwmb/ MBWS URL: https://p48-iwmb.icloud.com:443/iwmb/ SCMP URL: https://p48-iwmb2.icloud.com:443/scmp/ iCloud environment: PROD DS_ID: 1456157530 == Inspectee == == OT == == Mailbox == Mailbox Session: D8184033-F1F7-4030-9D98-0F81298C0D49 Incoming: Normal; Outgoing: Suspended Command Deque (rsvp | sendPending): [ | ] 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] Network-related configs: 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.connectionIdleTimeout = 20000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.connectionRetryInterval = 1000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.connectionRetryMaxBackoff = 4 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.reInitDelay = 1000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.reInitMaxBackoff = 3 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.reInitLimit = 4 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.persistentDisconnectionTimeout = 20000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.commandResponseTimeout = 300000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] - network.offlineWarningTimeout = 10000 20181003 09:14:49.794 [09:14:49.794+9 GSN.AbstractMailboxController.init] Mailbox initiated. 20181003 09:14:49.797 [09:14:49.797+9 GSN.FetchControllerPasswordConsumer.setPasswordReadyForTrial] setPasswordReady: false 20181003 09:14:49.797 [09:14:49.797+9 GSN.MailboxControllerPasswordConsumer.setPasswordReadyForTrial] setPasswordReady: false 20181003 09:14:49.797 [09:14:49.797+9 GSN.AbstractPasswordController._updateState] Entered state: GSN.VerifyPasswordForFetch:1994 20181003 09:14:49.797 [09:14:49.797+9 GSN.AbstractPasswordController._setPasswordReadyForTrial] setPasswordReady: true 20181003 09:14:49.797 [09:14:49.797+9 GSN.FetchControllerPasswordConsumer.setPasswordReadyForTrial] setPasswordReady: true == Network == == Playback == == Replay Script ==

Oct 2, 2018 11:53 AM in response to raphshu

I think the problem lies with the update to the latest version of Keynote, which on the desktop is 8.2. If you open 8.2 files in the El Cap version of Keynote (6.6.2) and resave them, they cannot then be reopened. I presume this is a bug but it might also be Apple's way of telling us that El Cap is no longer supported. It only started with the 8.2 version of Keynote -- the 8.1 version was OK.

BTW, the same happens with Pages, too.

Oct 6, 2018 8:01 AM in response to IanRid

I've got the same problem: open a file saved with 8.2 version using any other version (opens well), save, not possible to open anymore: '"....key" can't be open for some reason'. I don't know whether it's a bug or the Apple's way, but it makes it impossible to work, because on two out of three computers I've got keynote 6.6.2, and on one - the 8.2.


Have you found any solution? For now, I have to upload to icloud Keynote editor, modify something, download back, open (it opens), then modify and never (ever) close the file, unless the procedure should be repeated. Very disappointing.

Oct 7, 2018 3:29 PM in response to koniev

Yes, that sounds like the same problem I have encountered.

The solution I found was to create a new presentation in 6.6.2 and drag or copy the slides into it from the 8.2 version. Then save the 6.6.2 version.

You need to do something similar if you open a Pages 7.2 file in the older El Cap version of Pages.

This is a serious bug which seems to have arisen since the 'upgrade' to the latest versions of Pages (7.2) and Keynote (8.2). The 7.1 and 8.1 versions did not exhibit this behaviour, as far as I am aware.

Emergency: keynote file damaged and can't open

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.