Android 9.0 P Unable to reset device passcode

[DavidFink]

All other MDM functions appear to work, no issues with the restrictions and exchange profiles. Just the ' Reset Device Passcode'  function does nothing. The logs would indicate it is succeeding but there is no change on the device. Anyone else seeing this behavior? I'm on console 1811, enrolled a Galaxy Note 9 and the official release of Samsung Android 9.

Warning 2/12/2019 2:19 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Device Devices Command Change Passcode Confirmed Message Text : 
awev2:kv0:PPDIkpIyjbCRCQhz:EJseW0jr0tJulyknJqPw7I6vQ7jSbJo=

Warning 2/12/2019 2:19 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Server Dashboard Command Change Passcode Requested Message Text : 
awev2:kv0:LVP3Klqm0Ty3pmER:EOZ0VJIK5NrMUo4rUTWDtYo= 

Warning 2/12/2019 2:15 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Device Devices Command Change Passcode Confirmed Message Text : 
awev2:kv0:3PpFrFE7yzJtOY+x:EB5vcrao9Xx68073Be0YF7cp6/r8GTw= 

Warning 2/12/2019 2:15 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Server Dashboard Command Change Passcode Requested Message Text : 
awev2:kv0:oaz3BR+LyvqPgjkv:EBPqbd0HbnEMeViM/rNNT+A= 

Warning 2/12/2019 2:11 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Device Devices Command Change Passcode Confirmed Message Text : 
awev2:kv0:jcRK2U45nNLdcDg7:EJFwcbiVwx/vMQtr/oBuvuEWZLBuJTGg 

Warning 2/12/2019 2:11 PM DAFINK Android Android 9.0.0 GNWJ DAFINK 
Server Dashboard Command Change Passcode Requested Message Text : 
awev2:kv0:cDE7rvLyU1MuG6QF:ELDykQYg+/zNPng91kVQQ6U=

[LSIMM]

Arrrgh, not this again!

The same thing happened on Oreo, which they eventually fixed, have you logged a support request?

However I just tried on one of our test Samsung S9's on Android v9 and it works fine.  Might be worth checking you have the latest Hub app and Android patches in place.

[LukeDC]

It's not queued is it? I'm having a bear of a time with queued commands and the GCM deprecation it seems.

https://support.workspaceone.com/articles/360015465213

[LSIMM]

On that note, if using GCM, switch to AWCM instead as it offers more capability, plus it doesn't actually stop GCM completely, it works on a priority of AWCM first, then GCM as backup.

[LukeDC]

Yes awcm works for me. Just not the solution I want long term. Have to update to support fire base.

[henkor]

did you read this?
https://developers.google.com/android/work/device-admin-deprecation
get prepared to Android Enterprise...
some functionality that we used to work with starting to disappear...

[DavidFink]

Hey Hen,

From my interpretation of this post from google, everything should still be working under the Device Admin Model with Android 9.0 still.

With the release of Android 9.0, the following policies are marked as deprecated when invoked by a device admin, but the APIs otherwise continue to function. Starting with the 2019 release, the following policies will throw a SecurityException when invoked by a device admin:

USES_POLICY_DISABLE_CAMERA
USES_POLICY_DISABLE_KEYGUARD_FEATURES
USES_POLICY_EXPIRE_PASSWORD
USES_POLICY_LIMIT_PASSWORD
Some applications use the device admin for consumer device administration, e.g. locking and wiping a lost device. The following policies will continue to be available to enable this:

USES_POLICY_WIPE_DATA
USES_POLICY_FORCE_LOCK
USES_POLICY_RESET_PASSWORD

[DavidFink]

Hey Luke, from the device logs in the console it looks I am getting a solid pairing of Requested and Confirmed. Should I be looking somewhere else?

[LukeDC]

I was seeing a message saying NO GCM TOKEN FOUND and saw the requests get sent right away. My AW version doesn't support firebase and the GCM requests were taking forever. Google isn't supposed to deprecate GCM until April according to reports, but it seems they started early. I'm going to patch my system and see if it fixes me up.

The only thing that catches people in my world is you can set a passcode that doesn't meet your minimum security requirements, it will send it out, and mark it confirmed but the device won't accept it since it doesn't meet the minimums. Say my policy says it needs to be 6 characters, letters & numbers. I coultry and send a 4 digit PIN to the device. The console will show it as confirmed, but it will not take effect on the device and no error is reported back.

[Stansfield]

The Hub patch notes (from product announcements) say they start using Firebase not GCM and Firebase I wonder if they dropped GCM support in hub 9.0.2 could be worth checking your app versions (I am updated so I cannot check it)

' • AAGNT-183497: Begin using Firebase Cloud Messaging instead of Google Cloud Messaging (GCM will be deprecated by Google on April 11th 2019). Find out more here.'

I have had trouble with the passcode requirements as well after a passcode clear it never makes me set a new passcode or tells the system it has no passcode (before the 9.0.2 app update have not tested since)

[LSIMM]

Some more info from upcoming console release 1902 for SaaS.
https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1902/rn/VMware-Workspace-ONE-UEM-Release-Notes-1...

Fixed issues.

' AGGL-2924: When an Android device enters Doze mode, the GCM commands fails to get picked up by the device which causes commands, profiles and applications to get stuck in the queue.'

Also new features.

' Out with the old and in with the new. We've added support for Google's Firebase Cloud Messaging service.
Firebase Messaging implementation will replace Google Cloud Messaging (which is soon to be deprecated by Google) for Android device communication, read more about it here: https://support.workspaceone.com/articles/360015465213.'