Ricardo Rodrigues

Update your Keybase client to the latest version: https://keybase.io/docs/the_app/install_macos

Added a check to ensure meetings exists in `recordings_data` before trying to access it. Please fetch the latest version of zoom-recording-downloader/zoom-recording-downloader.py and give it a try.

@ylanmuller Could you try a quick test of the API response for that specific problematic user? You can use this `curl` command (replace the placeholders): `curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN"...

Here's a custom version of the script. I've added logging to capture the full API response for debugging (in the 'logs' subdirectory). Please review the API responses in the error...

@ylanmuller The script was recently modified to handle OAuth token refresh if authentication expires.

Was your S2S OAuth app set up with the correct scopes? `account:master, account:read:admin, account:write:admin, information_barriers:read:admin, information_barriers:read:master, information_barriers:write:admin, information_barriers:write:master, meeting:master, meeting:read:admin, meeting:read:admin:sip_dialing, meeting:write:admin, meeting_token:read:admin:live_streaming, meeting_token:read:admin:local_archiving, meeting_token:read:admin:local_recording, recording:master, recording:read:admin, recording:write:admin, user:master, user:read:admin,...

Does the first user in your Zoom account have a _blank_ first name?

I went through the error log you sent. The script fails because of a colon character “:” in one of the meeting names. Windows doesn’t allow that character when creating...

Try installing it manually using one of the recommended methods listed here: https://pypi.org/project/tqdm/#installationOn Jan 16, 2023, at 7:40 PM, izzyyf ***@***.***> wrote: I'm fairly new to coding... So I'm editing...

Do you have any Zoom user accounts with blank last name fields? Anyway, try the updated 3.1 version and see if that works.