Closed tKostka closed 2 years ago
yes it's mentioned in wiki https://androidaps.readthedocs.io/en/latest/search.html?q=play+protect&check_keywords=yes&area=default
the problem is comming from self signed certificate which is evaluated as suspicious by play protect. there is nothing we can do with it
Every scan of google play protect (manual or automatic triggered) kills the connection from AAPS to Combo on my new phone. Only way to re-establish connection to Combo is a forced close of AAPS and restart of AAPS, or restart of phone. This issue is reproduceable, happens every time: trigger play protect scan, give bolus in AAPS -> error message in AAPS
AndroidAPS 3.1.0.3 Nothing Phone (1) with Android 12 I did not have this issue on my old phone - Oneplus 7t with Android 11. There, AAPS and xDrip are working with play protect on.
I now, the workaround is to switch off play protect, but when using an additional work profile on android (to connect to company mails and services), play protect can't be switched off (switch greyed out). I can live without that, but would be easier to have everything on one phone. This is definitely not a problem for most of the users, but is there a possibility for improvement? Would be great.
Attached a logfile. play protect scan triggered 20:22, Bolus given 20:23