Skip to main content
B
bonnewu
Level 1.5: Cupcake
March 27, 2024
Question

Push pubsub not sending usage logs location event on lost mode

  • March 27, 2024
  • 1 reply
  • 8 views

Hi,
I am using an Android 12 device, company-owned and is fully managed. My enterprise is configured to receive "USAGE_LOGS" notifications and I enrolled the device with token parameter "allowPersonalUsage" set to "PERSONAL_USAGE_DISALLOWED". Also I enforced location mode with a policy. 


I can see the notification that command went through and device enters alert state as expected. Then, I move device in lost state by clicking "I found this device" and expecting location logs to appear. Nonetheless, no usage logs are coming from my push pubsub.

 

Before I was using pull pubsub and actually was able to receive usage logs back then. Don't really know if it's related. Originally, I though that the problem is that I couldn't properly subscribe enterprise to receive USAGE LOGS but it seems that's not the case from my previous question. My previous question on Usage logs 

1 reply

jasonbayton
jasonbayton
Level: 4.1: Jelly bean
March 27, 2024

First question that comes to mind - are you leaving it in the lost state for at least 5 minutes? Location won't be sent before then.

 

And are you seeing any other usage logs from enrolled devices at all?

B
bonnewuAuthor
Level 1.5: Cupcake
March 27, 2024

Hi, thanks for reply.
First, yes USAGE LOGS are on and I managed to receive enrollment completion notifications before. And I have been keeping my device in lost state for more than 5 minutes. No lost mode location logs so far.

 

I am confused because as I mentioned before I was able to receive lost mode location usage logs before with pull subscription. Recently I tried to switch back and as with push nothing came up. I assume I am missing something in configuration but not sure what exactly.

B
bonnewuAuthor
Level 1.5: Cupcake
March 28, 2024

While you're testing it things can go awry, there are lots of limitations in how frequently it can be enabled on a device and such - I had to wait a full day when recording a video on it to be able to reinitiate lost mode as I'd cocked up a step in the video 

 

To get the bug report you'll need to unlock it/recover from lost mode on device. Then you can capture a bug report and it should contain the logs still from while it was there. 


Turns out the problem was with device. I tried using Pixel 3 Android 13 phone and it worked as expected. Now I remembered that I was using this phone before for lost mode testing as well.
I downloaded the logs but couldn't really understand much.
Bug report 

Terms & ConditionsCookie settingsAccessibility statement