-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault on onInMeeting_() call #8
Comments
@FStupar you are on 5.17.11? |
@tanchunsiong yes, latest linux build, 5.17.11 |
@FStupar I've just tested it and it works fine. You are using the dockerfile right? |
@tanchunsiong The bot manages to connect to the meeting just fine, the segmentation fault happens right after that, when calling the onInMeeting_ from the MeetingServiceEventListener to be precise, segmentation fault occurs right when the onInMeeting_ is called. EDIT:: |
@FStupar has the code been changed? onInMeeting_ invokes back a method in the main thread. If you are missing the method, or if it is nullptr, you might get the seg fault. |
@tanchunsiong I had the same problem, and by some additional debugging, I have figured out the segmentation fault happens on the line 137:
Even when I comment the line, and assume the recording rights are there, I got the segmentation fault on the line 140:
Do you have any idea why those SDK methods cannot be invoked? |
@tanchunsiong Ok, with the latest version of SDK (just released), the seg fault is not there anymore, but I am having the SDKError 12 ("Cannot start raw recording: no permissions yet, need host, co-host, or recording privilege") even though I have allowed all participants to start recording local files (see image attached). Do I now need to generate "recording_token" for that? |
@uro-sh that error is a bit odd, possibly that m_pMeetingService->GetMeetingRecordingController() is throwing nullptr For the no permission issue, the host can be prompted to provide permission (recommended way). This is the specific token which is necessary |
@tanchunsiong It is not throwing nullptr, I have checked it. Also, I am able to quickly after the bot joins the meeting click on Participants -> Select the bot -> Click More... -> Select "Allow local recording", and the recording process started and was successful (the PCM file was generated, since only audio part is recorded). But without allowing that option manually the bot cannot start recording. Is there a code example for prompting for the permission (the recommended way)? |
@uro-sh , this is code for Windows, but it should be almost identical to Linux IMeetingRecordingController* m_pRecordController = meetingService->GetMeetingRecordingController(); |
@tanchunsiong Thank you, that worked for me! |
Used Ubuntu Dockerfile,
Built with newest SDK, added necessary tokens and information.
The bot joins the meeting, but as soon as it's admitted it throws a segmentation fault.
Managed to narrow it down to the onInMeeting_() call that happens in
MeetingServiceEventListener::onMeetingStatusChanged once the status is MEETING_STATUS_INMEETING
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: