.pages extension shows blank on submitted work

[HENRYFOURNIER]

students using Macs are submitting assignments using Pages.  Their assignments appeared completed before.

Recently submitted assignments with the .pages extension are appearing blank now.

[chriscas · Accepted solution]

Hi @HENRYFOURNIER,

This is apparently a known issue at the moment.  The  [OPEN] Apple iWork files are not rendering in Spee... - Instructure Community - 627577  page gives a little more detail, but there doesn't appear to be a workaround for this right now.  Even though it's a known issue, I'd still suggest reporting it to Canvas support to help them judge the impact and so that you'll be notified when the fix is in place.

I hope this info helps!

-Chris

[dbrace]

Hi @HENRYFOURNIER,

This is something that I experienced at my institution (I am also primarily a Mac user and do not use Pages, Numbers, or Keynote but I do have them installed) and there are technically two work arounds:

1. have the student export the Pages files as a Microsoft Word document or Adobe PDF file and then allow them to submit again
   1. Export to Word, PDF, or another file format in Pages on Mac
   2. Export to Word, PDF, or another file format in Pages on iPad
   3. Export to Word, PDF, or another file format in Pages on iPhone
2. if your faculty have access to a Mac, iPad, or iPhone, they can (if your institution allows it)
   1. download the student's Pages file from SpeedGrader (using the "down arrow" that appears on the right-side of SpeedGrader, to the right of the file that was submitted)
   2. open the file in Pages
   3. export to a Word document or PDF file (using the options above)
   4. submit the exported version of the assignment on behalf of the student

The single instructor that brought it to my attention used option #2 because they did not want to penalize the student because they did not technically do anything wrong.

-Doug

[dbrace]

Just an update about this issue that I received on Friday, December 13, 2024 at 3:35 PM ET.

___

Our engineers have created a fix that is undergoing QA testing. The next step, once it has passed QA, is for this fix to be deployed to the live production environment to address the problem. We will provide another update once that has happened.