6356de3f9b
The screens don't work as expected if they're launched in the work profile. The reason for this is that Settings handle the user separately with an extra inside the intent. I assume launching the actual screen in a separate user is not supported. Note that I've also: 1. Added a safeguard to make sure that the "active unlock" code path only occurs in the profile parent — it seems preferrable (see b/277877289#comment4) 2. Added the user id as an identifier on the intents lauched by the entries. The reason we do this is to make sure the user id is taken into account in the PendingIntent#equals implementation. This was automatically taken care of when launching with the profile context, but now that we launch everything in the profile parent context we have to make sure the user id is taken into account Bug: 278665241 Bug: 277877289 Test: manual Change-Id: Idcaa31cd56ed64768aa8f069d30d2adeb7269099