Maybe it is caused by change of identifier behaviour in "Android O". It is described in detail in the Adroid Developer Blog. Unfortunately I'm not allowed to post the link here.
I've seen it - when 8.0 (Google's) was in beta. These changes don't affect our app.
I've got a Nexus 5x with Google's 8.0 in front of me - no issues since first 8.0 "developer preview" or now with the "official" 8.0.
And so it seems that One Plus decided to "go the extra mile" and made more changes, their own, without telling anyone. We did not have any advance notice on that, it was a complete surprise.
That being said:
- We already implemented a workaround.
- It's in today's update of the Unlocker app on Google Play (1.0.27-655) and the main app's 1.12.0-651.
- The main app's 1.12.0-651 is currently enabled for 20% of all users
- If you don't have that version (of the main app) yet, you can find it here on the forum under "Development builds".
- The Unlocker app 1.0.27-655 was uploaded to Play today and is enabled for everyone.