-
Notifications
You must be signed in to change notification settings - Fork 240
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
The issue with targetSDK 14 #230
Comments
Are you reproducing this with the sample app? |
No |
Then unless you share some small sample code that reproduce the problem it's very hard for us to help you. |
Let me know what details I have to provide for helping me? |
Btw the app works fine with the version of the library: org.jitsi.react:jitsi-meet-sdk:5.1.0 |
We need a way to reproduce the problem. That SDK is years old, so it's no longer relevant here. |
Issue:
java.lang.IllegalAccessException
accessing visual serviceWindowManager
from a non-visualContext
Description:
When attempting to access the visual service
WindowManager
from a non-visualContext
, specifically in theCameraSession
andCamera2Session
classes, anIllegalAccessException
is thrown. This occurs within theorg.webrtc
package and seems to be related to device orientation retrieval.Error Trace:
Steps to Reproduce:
WindowManager
from a non-visualContext
.CameraSession
andCamera2Session
within theorg.webrtc
package.Expected Behavior:
The application should be able to access the
WindowManager
service without encountering anIllegalAccessException
when called from a non-visualContext
.Actual Behavior:
An
IllegalAccessException
is thrown, indicating an attempt to accessWindowManager
from a non-visualContext
.Environment:
com.my.app.Application@4187070
com.facebook.react.bridge
,org.webrtc
Possible Solutions:
Context
within the affected classes to determine why it's being used in a non-visual context.This issue needs to be addressed to ensure proper functionality and prevent runtime exceptions.
I passed activity context.
gradle:
implementation("org.jitsi.react:jitsi-meet-sdk:9.0.0") { transitive = true }
The text was updated successfully, but these errors were encountered: