Hi,

I actually think that clearing up AMS data like you did should be enough to fix this.

The bad thing is this error is so rare (usually happens to less than 5 users/month based on what I read here on the forum and on Google Play) that I have not been able to reproduce it successfully or to get my hands on a device that’s currently experiencing this error, meaning I can’t really fix it :frowning: From time to time I get an idea and change some small bits of code, but it never seem to help so the cause is still unknown to me.

I’m glad you got your installation up and working again though.

Filip