Skip to main content
New Member
December 19, 2023
Question

Android for work (ColorOS 14) cannot enroll

  • December 19, 2023
  • 1 reply
  • 2 views
Hi everyone,
 
I'm trying to enroll my new OnePlus 12 phone (based on ColorOS 14 which is based on Android 14) to Android for work to access my company apps like slack. I've added the company email account, and it started the work profile, started google service in work profile, have some work apps setup android device policy under work profile etc., and everything works fine, until to the very last step and in the screen it just hangs and do nothing.
 
I've further debugged thru ADB and find those logs which I think very relevant:

 

 

12-18 11:45:05.745 21753 21753 D ActivityThread: ComponentInfo{com.google.android.gms/com.google.android.gms.signin.activity.ConsentActivity} checkFinished=false 2 12-18 11:45:05.745 21753 21753 D ResourcesManagerExtImpl: applyConfigurationToAppResourcesLocked app.getDisplayId() return callback.displayId:-1 12-18 11:45:05.747 1820 1820 D Layer : reparent to null sequence=576, seq[2], name=Surface(name=1bbdf2 NavigationBar_displayId_0)/@0xd3fb08d - animation-leash of insets_animation#576 12-18 11:45:05.747 1820 1820 D Layer : reparent to null sequence=577, seq[1], name=Surface(name=9cf7768 StatusBar)/@0xf8c8790 - animation-leash of insets_animation#577 12-18 11:45:05.747 1820 1820 D OplusLayer: setGameMode WindowToken{e49a7d9 type=2011 android.os.Binder@66c1220}#400, 0 12-18 11:45:05.747 3181 4414 I Osense-BaseDecisionMaker: notifySceneToAthenaPolicy: SCENE_ACTIVITY_IDLE, bundle: Bundle[{scene=SCENE_ACTIVITY_IDLE}] 12-18 11:45:05.747 3181 4414 D Osense-MemoryReaderUtils: actualSwapTotalMem: 17407, actualSwapFreeMem: 17407 12-18 11:45:05.748 1170 3493 I android.system.suspend-service: --mSuspendCounter = 2 12-18 11:45:05.748 3181 4414 D Osense-MemoryReaderUtils: actualSwapTotalMem: 17407, actualSwapFreeMem: 17407 12-18 11:45:05.748 22576 23266 E AuthPII : [RequestTokenManager] getToken() -> BAD_AUTHENTICATION. App: com.google.android.apps.work.clouddpc, Service: oauth2:https://www.googleapis.com/auth/androiddevicemanagementregistration 12-18 11:45:05.748 22576 23266 E AuthPII : ahdm: Long live credential not available. 12-18 11:45:05.748 22576 23266 E AuthPII : at ryt.a(:com.google.android.gms@233918044@23.39.18 (190400-572044148):993) 12-18 11:45:05.748 22576 23266 E AuthPII : at rza.b(:com.google.android.gms@233918044@23.39.18 (190400-572044148):26) 12-18 11:45:05.748 22576 23266 E AuthPII : at ryx.a(:com.google.android.gms@233918044@23.39.18 (190400-572044148):612) 12-18 11:45:05.748 22576 23266 E AuthPII : at rsb.h(:com.google.android.gms@233918044@23.39.18 (190400-572044148):3) 12-18 11:45:05.748 22576 23266 E AuthPII : at vtf.i(:com.google.android.gms@233918044@23.39.18 (190400-572044148):19) 12-18 11:45:05.748 22576 23266 E AuthPII : at vtf.eY(:com.google.android.gms@233918044@23.39.18 (190400-572044148):1327) 12-18 11:45:05.748 22576 23266 E AuthPII : at mfh.onTransact(:com.google.android.gms@233918044@23.39.18 (190400-572044148):117) 12-18 11:45:05.748 22576 23266 E AuthPII : at android.os.Binder.transact(Binder.java:1207) 12-18 11:45:05.748 22576 23266 E AuthPII : at bbyo.onTransact(:com.google.android.gms@233918044@23.39.18 (190400-572044148):10) 12-18 11:45:05.748 22576 23266 E AuthPII : at android.os.Binder.transact(Binder.java:1207) 12-18 11:45:05.748 22576 23266 E AuthPII : at auvb.onTransact(:com.google.android.gms@233918044@23.39.18 (190400-572044148):147) 12-18 11:45:05.748 22576 23266 E AuthPII : at android.os.Binder.execTransactInternal(Binder.java:1387) 12-18 11:45:05.748 22576 23266 E AuthPII : at android.os.Binder.execTransact(Binder.java:1299) 12-18 11:45:05.748 22576 23266 E AuthPII : Message is Long live credential not available. ​

 

 


To be clear, I’m not in China (I’m in US and happen to have a OnePlus phone and I can access all the google services), so I’m wondering what was the issue there that “long live credential not available”?

I’ve tried multiple times to start the phone, clean the work profile (thru system UI or thru ADB) but they don’t work. I also tried to manually install some of the apps in google play in work profile but seems it’s not working either.

 

Anything that I can do to workaround this issue? Or any ideas? Appreciate the help, thanks!

1 reply

Level 4.4: KitKat
December 19, 2023

Hi @Snowman , 

even I'm not entirely sure if it will help but i found this: https://github.com/firebase/FirebaseUI-Android/issues/2066#issuecomment-1299393188

"...Deactive the Google Smart Lock .setIsSmartLockEnabled(false) (true by default) has solved the problem for our users. ..."

SnowmanAuthor
New Member
December 19, 2023

Thanks @Moombas ! I also saw that post and tried it out (disable the smart lock config) but unfortunatelly it doesn't work:(