What am I missing? The meeting is also on. Do I need to run a flask web server on localhost port 4000?
zoomsdk-build | [100%] Built target zoomsdk
zoomsdk-build | configure
zoomsdk-build | initialize
zoomsdk-build | authorize
zoomsdk-build | join a meeting
zoomsdk-build | connecting to the meeting
zoomsdk-build | disconnecting from the meeting
zoomsdk-build | failed to connect to the meeting
zoomsdk-build | meeting ended
I figured out the issue. The code works when the headless bot and the meeting organizer use the same account, the bot fails to log in to a meeting created by a different user though. Why?
I figured out the issue. The code works when the headless bot and the meeting organizer use the same account, the bot fails to log in to a meeting created by a different user though. Why?
If your Meeting SDK app isn’t published, the bot won’t be able to join any external meetings e.g. meetings that belong to someone outside of the Zoom account your Meeting SDK credentials belong to.
It sounds like the user you initially tried to use was from a different Zoom account, which is why your code failed in the first attempt.
If you continue running your meeting bots and want to take this off your plate in the future, you could consider using Recall.ai for your meeting bots instead. It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video from meetings without you needing to spend months to build, scale and maintain these bots.
Thank you @amanda-recallai for the reply! this makes sense. I can appreciate the effort it would take to maintain a bot. I checked the recall.ai web site . It looks like a commercial product. Is there a version that’s open/free to developers?
Hey @benren! Recall is open to developers - if you go through the demo flow on the website it should take you to an onboarding where you’ll get access to the product!
configure
connecting to the meeting
failed to connect to the meeting