Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS] App crashes after calling jitsiMeetView?.retrieveParticipantsInfo()

See original GitHub issue

Description:

I have upgraded to v3.1.0 in order to get the new SDK feature retrieveParticipantsInfo(), but the app crashes after being called.

Steps to reproduce:

Create and join a conference:

let jitsiMeetView = JitsiMeetView(frame: CGRect(x: 0, y: 0, width: 300, height: 200))
jitsiMeetView.delegate = self
let ui = JitsiMeetUserInfo(displayName: "my name", andEmail:"my@email.com", andAvatar: nil)
let options = JitsiMeetConferenceOptions.fromBuilder({ builder in
    builder.serverURL = URL(string: "https://meet.jit.si")
    builder.room = "my_personal_room_3"
    builder.subject = "Room"
    builder.token = nil
    builder.audioMuted = false
    builder.videoMuted = false
    builder.setFeatureFlag("chat.enabled", withBoolean: true)
    builder.setFeatureFlag("invite.enabled", withBoolean: true)
    builder.setFeatureFlag("JMCallKitProxy.enabled", withBoolean: false)
    builder.userInfo = ui
})
jitsiMeetView.join(options)

Wait for the meeting for setting up…
Try to get the participants array

jitsiMeetView?.retrieveParticipantsInfo({ (d:[Any]?) in
            print("Retrieved!")
})

Expected behavior:

It should output the message “Retrieved!” in the debug log

Actual behavior:

App crashes with no message (AppDelegate) Captura de pantalla 2021-02-07 a las 14 02 09

Client information:

Jitsi Meet version: iOS SDK 3.1.0
Crashes on iOS simulator and on iPhone X device. iOS versions 13.2 and 14.3

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

tmoldovan8x8commented, Feb 9, 2021

Thanks @jsearle for signalling this. There was a problem with the way the completion blocks are handled on Swift. Merged the fix and we’ll release a new SDK asap.

0reactions

stale[bot]commented, Jan 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.