Project

General

Profile

Actions

Bug #10243

open

Google work profile not working

Added by Arshana Atapattu about 1 year ago. Updated 2 months ago.

Status:
Needs Improvement
Priority:
Critical
Start date:
10/09/2024
Due date:
13/09/2024 (24 days late)
% Done:

0%

Estimated time:
Device Type:
Component:
Type:
Android

Description

Environment details
6.1.0 server
tested on UEM staging server
Agent Version: 4.05.00.09
Tested on: 4.05.00.14 as well

Prerequisites
Enrolled a device as a google work profile

Steps
Enroll a device as a google work profile.

Description
Device does not enrolled.
device was stuck at "device is being enroll"
No errors in backend, or logcat

when scanned through agent, it was came back to home screen. ideally after scan and proceed it should switch to agent inside the workprofile.
i had to manually switch to agent inside the workprofile. but inside that agent it was stuck at "device is being enroll".

Note: This is working in production env

Note: Enrollment was success on a android 14 device(Samsung galaxy A04/3GB ram)
But was unsuccessful [1] on a android 11 device(Samsung galaxy M02/ 2GB ram)
It shows a authenticating window, but never completes(waited around 20,30 mins). Even to get the authenticating window it took quite a lot of time.

Result
device does not enroll.

[1]
[1]


Files

1000229722.jpg (172 KB) 1000229722.jpg [1] Arshana Atapattu, 10/07/2024 04:02 AM
Actions #1

Updated by Oshani Silva 11 months ago

  • Status changed from New to QA
Actions #2

Updated by Arshana Atapattu 11 months ago

  • Subject changed from Google profile not working to Google work profile not working
Actions #3

Updated by Arshana Atapattu 10 months ago

  • Status changed from QA to QA Reject
  • Priority changed from High to Critical

This does not work

Actions #4

Updated by Arshana Atapattu 10 months ago

  • Description updated (diff)
Actions #5

Updated by Oshani Silva 10 months ago

  • Assignee changed from Inosh Perara to Sandaru Daminda
Actions #6

Updated by Oshani Silva 9 months ago

This will be addressed with an agent fix after the release.

Actions #7

Updated by Oshani Silva 9 months ago

  • Project changed from product-uem 6.0.0 GA to product-uem 6.1.0 GA
Actions #8

Updated by Viranga Gunarathna 8 months ago

  • Project changed from product-uem 6.1.0 GA to Backlog
Actions #9

Updated by Viranga Gunarathna 8 months ago

  • Project changed from Backlog to product-uem 6.1.0 GA
  • Type set to Android
Actions #10

Updated by Arshana Atapattu 7 months ago

  • Description updated (diff)
Actions #11

Updated by Arshana Atapattu 7 months ago

  • Description updated (diff)
Actions #12

Updated by Arshana Atapattu 6 months ago

  • Project changed from product-uem 6.1.0 GA to product-uem 6.2.0 GA
Actions #13

Updated by Sandaru Daminda 5 months ago

  • Due date set to 06/05/2024
  • Start date changed from 27/07/2023 to 02/05/2024
Actions #14

Updated by Sandaru Daminda 4 months ago

  • Due date changed from 06/05/2024 to 31/05/2024
  • Start date changed from 02/05/2024 to 29/05/2024
Actions #15

Updated by Sandaru Daminda 4 months ago

  • Due date changed from 31/05/2024 to 07/06/2024
  • Start date changed from 29/05/2024 to 05/06/2024
Actions #16

Updated by Sandaru Daminda 4 months ago

The issue is not reproducing with Google Pixel and Xiaomi devices and devices enrolling without issues.

Actions #17

Updated by Viranga Gunarathna 3 months ago

  • Status changed from QA Reject to On hold
Actions #18

Updated by Arshana Atapattu 3 months ago

Actions #19

Updated by Arshana Atapattu 3 months ago

  • Description updated (diff)
Actions #20

Updated by Thilina Sandaruwan 3 months ago

  • Project changed from product-uem 6.2.0 GA to Backlog
Actions #21

Updated by Sandaru Daminda 2 months ago

  • Project changed from Backlog to product-uem 6.3.0 GA
  • Due date changed from 07/06/2024 to 13/09/2024
  • Status changed from On hold to Needs Improvement
  • Start date changed from 05/06/2024 to 10/09/2024
Actions

Also available in: Atom PDF