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
Fatal Exception: java.lang.IllegalStateException: FragmentManager has been destroyed
at androidx.fragment.app.FragmentManager.enqueueAction(FragmentManager.java:1825)
at androidx.fragment.app.BackStackRecord.commitInternal(BackStackRecord.java:341)
at androidx.fragment.app.BackStackRecord.commit(BackStackRecord.java:306)
at androidx.fragment.app.DialogFragment.show(DialogFragment.java:502)
at com.schibsted.account.webflows.loginPrompt.LoginPromptManager.showLoginPromptIfAbsent(LoginPromptManager.kt:30)
at com.schibsted.account.webflows.client.Client.requestLoginPrompt(Client.kt:360)
at com.schibsted.publishing.hermes.simplifiedlogin.AppStartSimplifiedLoginPromptInitializer.init(AppStartSimplifiedLoginPromptInitializer.kt:26)
at com.schibsted.publishing.hermes.newsfeedweb.NewsfeedWebFragment$launchAppStartSimplifiedLoginPrompt$1.invokeSuspend(NewsfeedWebFragment.kt:318)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:811)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:715)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:702)
Occurs on different devices while using login prompt. Allowing state loss when showing this dialog should be easiest solution.
The text was updated successfully, but these errors were encountered:
Occurs on different devices while using login prompt. Allowing state loss when showing this dialog should be easiest solution.
The text was updated successfully, but these errors were encountered: