Forum Discussion

Level 1.6: Donut

2 months ago

Solved

Managed configuration to Gboard has disappeared from MDM

The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment: MDM...

omnissa workspace one

soti mobicontrol

Lizzie
25 days ago
Hey badams1, AndroidE, mattdermody, Stefano, Magcho, Alex_Muc, Moombas, jeremy, Flaviano, Sulander, Kraeutergarten,

I think we have lift off! 😀 🤞🚀

A fix has just been pushed for this, it could take a few hours to start coming through on your side, I wondered if you could validate and let me know if you see any change please?

Massive thank you for all the feedback you've given this has been really helpful. Looking forward to hearing from you.

Thanks,

Lizzie

[Will mark this as an 'Accepted solution' to highlight this at the top of the topic - but this is still pending validation - please still reply below - thank you]

Stefano

Level 1.5: Cupcake

2 months ago

Hi to all of you!

We're experiencing the same issue both with Samsung Knox Manage than with Microsoft Intune and Omnissa Workspace ONE

For what I see on Knox Manage console, the pre-existing configurations still remains from the console side..

..while new assignations are not possibile..

It would be handy to understand if the pre-existing configurations are still up and running on devices

Hope it will be solved soon!

Stefano

Alex_Muc

Level 3.0: Honeycomb

2 months ago

StefanoWith WorkspaceONE you don't have to worry about this for the time being. There you can manually enter Config Keys, Value Type and Values. Despite the current problem, WorkspaceONE sends the existing AppConfig to Google Play. Ideally, you should not change the assignment for the time being.

Some configurations appear to be nested. This is not supported in the UI of WS1 for the manual input of the AppConfig. In Magcho's screenshot, the first entry is “preferences”. This is the array name. (and Value Type = "bundle", what WS1 does not support here) Correcting this configuration immediately could invalidate all nested configurations.

I have created a manual configuration. The configuration arrives at the device and is also applied by Gboard. The config for the size ratios are not nested. Fortunately, the fact that the Gboard is suddenly twice as high can be seen very quickly as feedback. 😆

"productId": "app:com.google.android.inputmethod.latin", "managedConfiguration": { "managedProperty": [ { "key": "config_keyboard_height_ratio_normal_portrait", "valueString": "2.0" } ], "kind": "androidenterprise#managedConfiguration"

Once the problem has been fixed, everything should ideally look the same again. 🙂