Skip to main content
P
Prathik
Level 2.0: Eclair
November 28, 2023
Question

Seeing inconsistency in START_LOST_MODE in android management api

  • November 28, 2023
  • 2 replies
  • 0 views

Hi,

I'm implementing the START_LOST_MODE for my organization. The command works and I see the notification on the device saying that its a lost device. If the user doesn't do anything on the device, we can send the STOP_LOST_MODE and START_LOST_MODE again and it works as expected. But if the user takes some action on the device to unlock or select not my device. Then none of the `START_LOST_MODE` commands work again. Is there a limit to how many times this command can be used? Below is the response I get for GET /operation for the issue command.

 

{ "name": "enterprises/LC02ot****/devices/3e4aa95e427****/operations/1701195873812", "metadata": { "@type": "type.googleapis.com/google.android.devicemanagement.v1.Command", "type": "START_LOST_MODE", "createTime": "2023-11-28T18:24:33.812Z", "duration": "3600s", "userName": "enterprises/LC02ot****/users/10750409941529692****", "startLostModeParams": { "lostStreetAddress": { "localizedMessages": { "en-US": "1800 Amphibious Blvd. Mountain View, CA 94045" }, "defaultMessage": "1800 Amphibious Blvd. Mountain View, CA 94045" }, "lostOrganization": { "localizedMessages": { "en-US": "Example Organisation" }, "defaultMessage": "Example Organisation" } } } }

 

2 replies

P
PrathikAuthor
Level 2.0: Eclair
November 29, 2023

And sometimes I see the below response in the notification endpoint

 

{ "done":true, "error": { "code":2 }, "metadata": { "@type":"type.googleapis.com/google.android.devicemanagement.v1.Command", "type":"START_LOST_MODE", "createTime":"2023-11-29T18:10:11.970Z", "duration":"600s", "errorCode":"UNKNOWN", "userName":"enterprises/LC034k****/users/103356011475399598171", "startLostModeParams": { "lostMessage": { "defaultMessage":"Hello there, this is a lost device" }, "lostPhoneNumber": { "defaultMessage":"1231231234" }, "lostEmailAddress":"ganip@amazon.com", "lostStreetAddress": { "defaultMessage":"123lane WA" }, "lostOrganization": { "defaultMessage":"Amazon" } } }, "name":"enterprises/LC034k****/devices/315c78b0b91fbc21/operations/1701281411970" }

 

J
jeremy
Level 1.6: Donut
December 1, 2023

Hello, according to the lost mode documentation located here: https://developers.google.com/android/management/lost-mode

 

 

A device cannot be placed into lost mode if:

  • The device is not an organization-owned device
  • The device is already in lost mode
  • The device password has been reset by an IT admin in the last 12 hours
  • The employee manually exited lost mode in the last 12 hours
  • It is a work profile on a company-owned device and the work profile is paused

 

Are you waiting 12 hours before trying again?

Terms & ConditionsCookie settingsAccessibility statement