Callback on enter request for unauthorized users

[iospro]

It would be useful to add callback on enter request for unauthorized users.
For example, in iOS JitsiMeetViewDelegate we have callback

- (void)participantJoined:(NSDictionary *)data

When unauthorized user comes we have on-screen message with two buttons Allow/Disallow.
It would be nice to have some callback as

- (void)participantIsWaiting:(NSDictionary *)data

data contains basic information on a new user (some userGuid)

Also we need some method to Allow/Disallow to enter in parallel with current in-box mechanism

• (void)enterParticipant:(NSString *)userGuid allow:(BOOL)allow

This SDK extension allows to notify admin about new waiting participants while screencasting outside the custom Jitsi App.
In such case the App can make a local notification with interactive buttons on participantIsWaiting event to allow/disallow enter for new participant without need to enter the Jitsi App

This feature is needed in all platforms.

[saghul]

You mean lobby actions, right?

[iospro]

Yes, incoming lobby event and programmical reaction on this event via SDK API

[saghul]

Got it. I don't think we have short term plans to add this, but any PR is welcome.

[iospro]

Could you please describe how we can get to know which commits from master branch were included into some SDK release? We can't find release notes and commit relations in SDK repo

[saghul]

It's right here: https://github.com/jitsi/jitsi-meet-release-notes/blob/master/CHANGELOG-MOBILE-SDKS.md

That includes the release notes and links to the tag and list of commits on a given release.

It's also linked in the "releases" tab on the handbook: https://jitsi.github.io/handbook/docs/releases

[iospro]

Could you please make a suggestion about the date of the next release iOS/android sdk? We made some pull requests with very important for us localization improvements.

[saghul]

We are hoping for a release late this week or the next.

[iospro]

very hope this week

[stale]

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.