Error when installing launcher profile

[sygrovec]

Hi

has anyone had the below error when trying to install a launcher profile to rugged android devices. It has been working prior to console upgrade last night and now not working. If anyone has seen it how did they resolve the issue. ERR Error when connecting to CDNDE02.awmdm.com (response code :403) Tries 5 times and then get an error saying ERR Error setting up ground Lockdown

Would appreciated any help on this. Thanks

[ACalvez]

Hello,
I have a similar problem : Impossible to enrol a device with Launcher anymore (it was working previously, with android legacy and android for work).
On the agent, it seems downloading for a while and indicates ' failed'  (' com.airwatch.lockdown.launcher'  failed).
I tried to revert back to previous version (4.2.0.21) without success (this version is installed on previously enrolled devices but doesn't install on new devices)

[sygrovec]

Hi

I have a call in with them now and had to send device logs. Our launcher profile was working the day before an console upgrade and stopped working day after so i can only assume something change in the new release.

We have tried launcher 3.3.0 to launcher 4.4.0 and nothing seems to be work.

once i have a response from Airwatch or a fix i shall let you know.

[ACalvez]

Thanks for your answer !
To my side, I don't know exactly when the problem came but we were able to enrol with launcher and it doesn't work anymore.
We also tried different launcher version, without success.
I tried to declare launcher APK as internal app and deploy it without more success (other installations are working, whether they are internal apps or store apps).
I found a way to make it working, when sideloading and manually install the APK. Not convenient, but it works....
I also opened a ticket, hoping they find a solution.

[admin]

i have had this occur for several years now while employed at two different companies.  if you experience this issue after a console upgrade, AirWatch did not seed Launcher (or other service application if still using Legacy Android) in your console during the upgrade.  this can happen with a single version (i.e., you are pushing 3.3 and that one doesn't work, but all other do) or, like in your case, with all versions so that no Launcher is able to be pushed to your device during profile installation.  we now verify which versions of the service applications that we are deploying and request that AirWatch verifies that the correct service applications were seeded post upgrade.