Closed vanthomiy closed 3 years ago
I cant reproduce this. Also before the !! assertet call I am checking the next alarm for NULL value.
I also can't reproduce it right now. But I think it was something wrong with the alarm before. So maybe something different happend before causing this issue.
It happens in the BackgroundTimeHandling /**
There is a !! assertet call which should not be used...