[ARCHIVED] Comments not functional in Canvas for iPad

[AlexanderPope]

This semester I've had consistent problems with assignment comments in Canvas for iPad (teacher). I can usually post one comment, then lose the ability to post additional comments or interact with the sidebar in any meaningful way. This pertains to general comments on a student submission, but is particularly noticeable when trying to add comments to different sections of a rubric.

Re-loading the entire course is the only solution I've found, which is not a solution at all.

Has anyone else experienced this, or have any suggestions for how to correct this app behavior?

[KristinL]

Hi @AlexanderPope -

How are students getting work to you? Are you using the File Upload option for submissions while students use Canvas Student for annotations, or are you utilizing Annotations as the submission type?

The two routes seem similar, but they behave differently in the Canvas Teacher app and SpeedGrader. Let me know, and we can continue to troubleshoot.

[AlexanderPope]

They submit via text entry, file upload (.pdf, .doc, .docx), or url (to allow for Google Docs). No one has used the url yet this semester. It's mostly PDFs.

[KristinL]

Hi @AlexanderPope -

By chance, are Assignment Enhancements enabled at your school? I found that there's a Known Issue that sounds similar to what you describe.

[OPEN] iOS - Teacher | Feedback left via app is le... - Instructure Community  

[AlexanderPope]

Not that I know of

[KristinL]

I'm sorry to leave you waiting, but the Community Coaches are stumped. I think the best "next step" would be to collaborate with Canvas Support. They may have other cases (with solutions!) that they can share with you. They may also be able to forward your case to the Mobile Team for additional insight.

If you arrive at a solution, please come back and share an update. That way, if another Community member has a similar question, they have a starting point in the troubleshooting process.

[AlexanderPope]

Ok, thanks for taking a shot at it.

(This will also be my chance to share the error message I have gotten every time I reply to this thread)

[Stef_retired]

@AlexanderPope  I've seen that error message from time to time myself; it usually occurs when a user is not authenticated or has returned to a tab that was opened earlier but not refreshed to double-check that the user is still authenticated).