I noticed that if you use config.scheduleUpdate and then go to the next view, the scheduler is still running and then as soon as you use context.back it stops running at all.
It should stop running when you change a view and continue running after you return.
Is there an existing issue for this?
🐛 Describe the bug
I noticed that if you use config.scheduleUpdate and then go to the next view, the scheduler is still running and then as soon as you use context.back it stops running at all.
It should stop running when you change a view and continue running after you return.
✔️ Expected behavior
No response
👣 Steps to Reproduce
💻 Platform
⭐ Server Version
1.20.2 paper
📚 Library Version
3.1.0
✍️ Additional context
No response