jitsi / jitsi-meet-sdk-samples

Jitsi Meet mobile SDK examples (Android, iOS and React Native)
Apache License 2.0
270 stars 235 forks source link

Unable to Initiate Jitsi Meet After Upgrading to Android 14 App Crashing #217

Open pramod279 opened 6 months ago

pramod279 commented 6 months ago

Unable to initiate Jitsi Meet - App Crashes Immediately after targeting Android 14.

Fatal Exception: java.lang.RuntimeException Unable to create service org.jitsi.meet.sdk.JitsiMeetOngoingConferenceService: java.lang.SecurityException: Starting FGS with type mediaProjection callerApp=ProcessRecord{82fabab 28805:com.darisni.nursery.debug/u0a287} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION] any of the permissions allOf=false [android.permission.CAPTURE_VIDEO_OUTPUT, android:project_media]

saghul commented 6 months ago

Are you using our app or the SDK?

pramod279 commented 6 months ago

Hi @saghul I am using the SDK.

saghul commented 6 months ago

Are you building your app with target SDK 34? Our SDK does not support that yet, you should target API 33 until an SDK which targets 34 is out.

pramod279 commented 6 months ago

Yes, I have upgraded my app to SDK 34 which is when this crash started occurring. Most of the other libraries I am using have upgraded to support SDK 34, which is why I am forced to use SDK 34.

May I know by when we could expect Jitsi SDK to support SDK 34 as it has been launched months back. Google recommends upgrading to SDK 34

saghul commented 6 months ago

Supporting 34 doesn't mean you have to do it too, you can target 33 and your app will still work.

We expect to have a version which targets 34 this month.

pramod279 commented 6 months ago

Thanks for that update.

mzgg commented 4 months ago

Does it support version 34 now? and which version

saghul commented 4 months ago

Not yet.

mzgg commented 4 months ago

when do you plan it to release ?

saghul commented 4 months ago

No ETA right now, we have run into some problems with new foreground service permissions and are working on fixing them.