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
  • 3 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

J
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.

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

I use the same topic for both pull and push subscriptions and I didn't change anything there. I use default configuration for both pull and push subscriptions, didn't change match. The only difference would be I also pass a token parameter in the endpoint of my push subscription but enrollment completion logs arrive okay. So it shouldn't be a problem I think. Can it be device android version or Device Policy app lacking certain permissions?


The Android version for the deployment scenario is fine, so I don't think that's the issue. 

 

You could pull a bug report after 15+ mins in lost mode state and see if the device itself is sending things up?

 

I'll do some testing today also with my project. 

Terms & ConditionsCookie settingsAccessibility statement