Description
We were investigating why Zoom LTI 1.3 meeting reports were coming up blank. We have a ticket opened now, but just wanted to see if others had the same issue.
For meetings that are recurring, the API has to use a UUID.
According to spec: https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/reportMeetingDetails
If you provide a meeting UUID that begins with a
/
character or contains the//
characters, you must double encode the meeting UUID before making an API request.
However, we’re noticing that for
TEST.ZOOM.JHTEST - Recurring Testing
Meeting ID: 920 0727 4568
it should be sending https://zoom.us/v2/report/meetings/bi%2FwHAuARKqvBYhZIshGrw%3D%3D
but it’s sending (according to the call log)
https://zoom.us/v2/report/meetings/bi%25252FwHAuARKqvBYhZIshGrw%25253D%25253D
and failing with a “code”: 3001,
“message”: “Meeting does not exist: bi%2FwHAuARKqvBYhZIshGrw%3D%3D.”
So it may inappropriately double encoding meeting_id = bi%2FwHAuARKqvBYhZIshGrw%3D%3D
How To Reproduce
- create a recurring meeting via LTI Pro
- launch and end the meeting
- wait for the report link to appear
- click on the report link
Results:
no meeting report
if you check the zoom call logs, you will see an 404 error, and the details would say
"response": {
"code": 3001,
"message": "Meeting does not exist: bi%2FwHAuARKqvBYhZIshGrw%3D%3D."
},