-
Notifications
You must be signed in to change notification settings - Fork 219
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
Application get crash in Android -14 #401
Comments
The bug has been fixed. You can upgrade the version to 4.4.1 and then try again. |
Can anyone please help update on above issue with latest Agora SDK version 4.4.1 |
I have tested it. there is no problem for onUserJoined callback with agora version 4.4.1, can you share your demo with me? By the way, you can also run our demo first to see if the callback is normal |
@weileifrank Just checked in your demo as well when any user left the channel (Suppose UID - 452061665) onUserOffline callback executed. In next second for UID-452061665 onUserJoined callback executed. Please check the logs of your demo App. |
@weileifrank Can you please check on priority as our client is facing issue #401 (comment). |
Hi @weileifrank I have checked with your webdemo and app but still having same issue. Please check the video https://drive.google.com/file/d/10tRGVG0b7JL5-TgGIr2S9mn-hxC9akhM/view?usp=sharing |
@rahul6924 |
@weileifrank I will check in two different phone but over use case is mobile and web video streaming. Can you please check the similar case at your end |
@weileifrank I have tried with two mobile but the behaviour is still same also i didn't get any logs in storage. There is no application folder with package name inside storage directory Do i need to add the below code in sample application.
val config = RtcEngineConfig() |
In our application we have targeted the SDK 34 and we are using screen sharing SDK.
We have already using a foreground service in app manifest as per the doc
https://docs.agora.io/en/video-calling/core-functionality/screen-sharing?platform=web
Do we need to do anything at our end to fix this crash.
The text was updated successfully, but these errors were encountered: