-
Notifications
You must be signed in to change notification settings - Fork 61
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
[question]: Getting Error On Logout Call #715
Comments
Thanks for sharing! What version of the OneSignal Unity SDK and Unity Editor are you using? Are you able to reproduce this error? And could you provide the steps to do so Can you provide your entire log with verbose logging turned on by calling |
So, Problem is that i am getting this really random. Unity 2022.3.22f, |
Where are you calling Are you calling |
When user logs in with his account i am calling |
Can a user be logged out without calling |
Got it. that was a case i was calling only once init and then only user login/logout. |
Closing due to inactivity. If you are still having issues, feel free to open a new issue |
How can we help?
Hey,
Got some problem Calling logout and reciving something like that
Must call 'initWithContext' before 'logout'
java.lang.Exception: Must call 'initWithContext' before 'logout'
at com.onesignal.internal.OneSignalImp.logout(OneSignalImp.kt:423)
at com.onesignal.OneSignal.logout(OneSignal.kt:193)
at com.unity3d.player.UnityPlayer.nativeRender(Native Method)
at com.unity3d.player.UnityPlayer.-$$Nest$mnativeRender(Unknown Source:0)
at com.unity3d.player.UnityPlayer$F$a.handleMessage(Unknown Source:122)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at com.unity3d.player.UnityPlayer$F.run(Unknown Source:24)
at UnityEngine.AndroidJNISafe.CheckException () [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.AndroidJavaObject._CallStatic (System.IntPtr methodID, System.Object[] args) [0x00000] in <00000000000000000000000000000000>:0
does anyone have the same problem ?
Code of Conduct
The text was updated successfully, but these errors were encountered: