Sporadic problems with Managed Google Play after enrollment

[Alex_Muc]

Hi!

We had problems with a few devices after enrollment today. The Managed Play Store did not work properly. Restarting and waiting seems to help.

Symptoms

• Empty collection in Managed Google Play
• Spaceship error, because supposedly no apps were made available
• Installation commands from the UEM did not work in some cases
• Apps assigned in UEM cannot be found in Play

I was only able to reproduce the problem in one of 3 attempts. A few automatic app installations worked for me. However, it was not possible to search for the apps manually.

Restarting the device and then waiting a while seems to help. However, a colleague had a strange error in Managed Google Play after a restart when he tried to install an app manually.

"The item you want to buy could not be found."

However, it is not a purchased app or an app with in-app purchases.

Is anyone else currently having problems with Managed Google Play?

[jeremy]

Hello,

I'm seeing these kinds of issues again, and logs are also showing errors like these:

01-24 11:40:56.107 27906 28074 I clouddpc: [PolicyLogHelper.java:logInstallError:192] en_US Install error. Package name: [com.azure.authenticator]. Play error reason [ENTERPRISE_AUTO_INSTALL_ERROR_INSTALL_FAILED]. CloudAPI error reason: [TRANSIENT_ERROR].

I've raised a new issue with our EMM teams, @Lizzie would love some help here 🙂

Thanks

[Lizzie]

Thanks so much @jeremy for highlighting and for offering help. I'll highlight you raised a new ticket for this back to the team working on it. Thanks for your offer of help - I'm sure we will be back in touch! 😁

[Lizzie]

Hey @Alex_Muc, @Flo and @jeremy,

Thanks again for highlighting this. Just to say, we do have an engineer looking at the ticket for this. Once I hear more I'll let you know. But, wanted to say it is being looked into. 👍

If anything changes on your end, please do let us know. 

Thanks so much, enjoy your day. 

Lizzie

[Alex_Muc]

I was able to reproduce the problem today after several attempts.
In the case of an issue, an update from Google Play seems to help. (Google Play > Settings > About > Update Play Store)
On my test device, the problem was resolved about 3 minutes after enrollment. During this time, a Play Store update from 41.1.19-31 to 44.4.19-31 was installed.

Since there is a workaround / solution, I will not open a ticket with Omnissa. They would most certainly not open a ticket with Google in that case.

@Flo  If Ivanti has a ticket with Google and you need more logs, I could send you Verbose logs.

[Lizzie]

Thanks @Alex_Muc for highlighting this, sorry you are experiencing problems. Thanks also you to you @Flo and @jeremy for the additional information.

I did have a quick check late Friday on this and it didn't appear we had received any Android Enterprise reports on this at that time. I'm intrigued to know if this is the same thing that you mentioned here Jeremy. Hopefully it is and it's resolved now, but do keep us posted on your experience.

I did still highlight this to a couple of engineers in our team on Friday. I'll let them know now that a ticket via Ivanti and possibly Omnissa has been filed and they can take a further look and some further testing.

Thanks again,

Lizzie

[jeremy]

There was a confirmed issue last week with the Play Store, but for us it was fixed around the end of the week.

Can you still reproduce these issues?

[Alex_Muc]

I was able to reproduce the problem at least on Friday afternoon. I'll check again tomorrow to see if the problem still exists. 😃

[Flo]

Hi,

We encounter the same issues after enrollment : 

• Spaceship error, because supposedly no apps were made available
• Apps assigned in UEM cannot be found in Play

We have an open case with Ivanti