Closed remulasce closed 9 years ago
Hmm
On Saturday, April 4, 2015, remulasce notifications@github.com wrote:
Don't know the cause. Happens when app is both in foreground and background ... so probably something is also not getting shut down properly.
— Reply hmmto this email directly or view it on GitHub https://github.com/remulasce/metroapp/issues/189.
Clarification: Only noticed on dev_2 branch after implementing synchronized stop-proximity updating.
I integrated an exception-reporter library which prompts the user to email me with a stack trace and other info.
So next time it happens I'll have any sort of clue of what actually happened.
Looks like it was a problem in NotifyService. Null pointer check / handling have resolved it. The Report A Crash thing is great, though.
Don't know the cause. Happens when app is both in foreground and background ... so probably something is also not getting shut down properly.