You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
I think there is an issue when using service MXSession.clear on Android SDK.
This is the error stack error I have
E/MXSession: Use of a released session :
dalvik.system.VMStack.getThreadStackTrace(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1566)
org.matrix.androidsdk.MXSession.checkIfAlive(MXSession.java:313)
org.matrix.androidsdk.MXSession.getDataHandler(MXSession.java:380)
org.matrix.androidsdk.crypto.MXCrypto.close(MXCrypto.java:535)
org.matrix.androidsdk.MXSession.clearApplicationCaches(MXSession.java:605)
org.matrix.androidsdk.MXSession.clear(MXSession.java:639)
org.matrix.androidsdk.MXSession.clear(MXSession.java:615)
Indeed in MxSession.clear (line 627) we check internal attribute mIsAliveSession and set it to false
if (!mIsAliveSession) {
...
}mIsAliveSession = false;
And after, when we call MXCrypto.close -> MXSession.getDataHandler displays this error because mIsAliveSession = false;
Is it an expected behavior? Can we improve mIsAliveSession in this context?
The text was updated successfully, but these errors were encountered:
I think there is an issue when using service MXSession.clear on Android SDK.
This is the error stack error I have
E/MXSession: Use of a released session :
dalvik.system.VMStack.getThreadStackTrace(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1566)
org.matrix.androidsdk.MXSession.checkIfAlive(MXSession.java:313)
org.matrix.androidsdk.MXSession.getDataHandler(MXSession.java:380)
org.matrix.androidsdk.crypto.MXCrypto.close(MXCrypto.java:535)
org.matrix.androidsdk.MXSession.clearApplicationCaches(MXSession.java:605)
org.matrix.androidsdk.MXSession.clear(MXSession.java:639)
org.matrix.androidsdk.MXSession.clear(MXSession.java:615)
Indeed in MxSession.clear (line 627) we check internal attribute mIsAliveSession and set it to false
if (!mIsAliveSession) {
...
}mIsAliveSession = false;
And after, when we call MXCrypto.close -> MXSession.getDataHandler displays this error because mIsAliveSession = false;
Is it an expected behavior? Can we improve mIsAliveSession in this context?
The text was updated successfully, but these errors were encountered: