I've been there before.
It was because of setTimeout javascript function.
setTimeout calls a Client Action, and that client action call something but screen already destroyed because of it was ran after screen navigation.
I've been there before.
It was because of setTimeout javascript function.
setTimeout calls a Client Action, and that client action call something but screen already destroyed because of it was ran after screen navigation.