Paul, I noticed these messages while testing something else, and was able to reproduce reliably by killing both unity8 and the click scope, then starting up the click scope:
- it will print the assertions just after unity restarts.
This agrees with what I was seeing while trying to reproduce it manually - it seemed to print the assertions the first time I opened the apps scope after restarting the phone.
Paul, I noticed these messages while testing something else, and was able to reproduce reliably by killing both unity8 and the click scope, then starting up the click scope:
pkill unity8; pkill click; G_MESSAGES_ DEBUG=all ./src/click-scope
- it will print the assertions just after unity restarts.
This agrees with what I was seeing while trying to reproduce it manually - it seemed to print the assertions the first time I opened the apps scope after restarting the phone.
Hope this is useful...