Somehow, it doesn't work for Android

[ghuang0207]

I am using ionic2 with your plugin. We are using airwatch in our enterprise.

We published our code to Google Play, set as internal access only. We saw an error message "This app doesn't support app configuration", when we tried to enable "Send Application Configuration" from the airwatch console. ( the same exact code works for iOS).

Also I checked my config.xml file, the version is: ~1.0.1 Does that matter? I tried to do:
cordova plugin rmv cordova-plugin-emm-app-config and
cordova plugin add cordova-plugin-emm-app-config
but I still get version 1.0.1.. I even tried cordova plugin add cordova-plugin-emm-app-config@1.0.2

Could anyone please help me?
We have been running out all the solutions...

Thank you
George

[lpchanora]

Hi George,

1.0.1 or 1.0.2 shouldn't make any difference. 1.0.2 only added some extra description and contains no bug fix or new feature. However, you can update to 1.0.2 by first removing it:
cordova plugin remove cordova-plugin-emm-app-config

The command is "remove", not "rmv".

As for the error message, sounds like it's coming from the Airwatch Console when you try to enable the "Application Configuration" setting, is that correct? If that's the case, it shouldn't be caused by the app itself. It's probably related to the app settings in AirWatch. You may want to contact AirWatch to see what's causing that error message.

Thanks,
Leon

[lpchanora]

Closing this issue since this doesn't appear to be a problem with the plugin itself.

[theaccordance]

Having the same issue as well, and my suspicion leans towards it being the plugin. Reviewing the Google documentation for Setting up Managed Configurations, it appears there should be additional properties injected into the AndroidManifest.xml file?

[theaccordance]

If I'm reading the Android documentation correctly for configuring an application for managed configurations, the plugin needs to do the following to enable the functionality:

1. Add a property to platforms/android/AndroidManifest.xml within the <application> block:

<meta-data android:name="android.content.APP_RESTRICTIONS" android:resource="@xml/app_restrictions" />

2. Add a XML file which defines the properties exposed via AppConfig: platforms/android/res/xml/app_restrictions.xml

As far as I can tell looking at the plugin, it's doing neither. My suspicion is supported by the fact that we don't define anything in Cordova's config.xml file to even define the restrictions, which is something I have to do for other plugins like Deeplinks.

[lpchanora]

@theaccordance Thanks for the comments. Are you also getting error message from AirWatch console?

We had it working with AirWatch without the need to define any restriction. We will investigate to see if there are cases where restrictions may be needed.

[ghuang0207]

Hi Leon,

Thank you for the message!! Yes, we are getting the error message from AirWatch console.
We did contact AirWatch, but they kept saying the problem is in the plugin....

Is it possible you can give us some direction where the setting/configuration part we can check in Airwatch console?

George

[lpchanora]

Hi George @ghuang0207 ,

I'm not sure exactly what to check. I would think AirWatch should know since apparently they are checking for something when they throw the error message. Is your apk file uploaded directly to AirWatch, or do you have it in another app store like Google Play and provide a link in AirWatch?

Another poster has just commented on this issue. Maybe you can try adding the restriction property and file and see if that solves the problem?

Thanks,
Leon

[theaccordance]

@lpchanora Can't speak for Airwatch, my Android woes relating to this plugin are coming from my Mobile Iron customers

[MrTechGadget]

I think @theaccordance is onto something, the Documentation from google clearly states

"To provide externally managed configurations:
Declare the managed configurations in your app manifest. Doing so allows the enterprise administrator to read the app's configurations through Google Play APIs."

That leads me to believe that AirWatch, or Mobile Iron is using the Google Play APIs to check for the keys that can be set. If the app has not correctly declared those in the application manifest it will not be able to read them.

Should be fairly easy to test this by manually adding this data to the manifest to check. If that fixes it, it shouldn't be that hard to add functionality to the plugin to write this data programmatically when built.

[ghuang0207]

@audioeng I think your are right AirWatch asked us to deploy apk through Google Play ( a must )..

[ghuang0207]

To Leon @lpchanora ,

We deployed our APKs to AirWatch through Google Play.

George

[theaccordance]

Here's a patch I'm testing: #3

The PR itself is not ready for merge, the changes I'm showing need to be optimized further to function as a proper plugin.

What the patch is doing:

• Adding a property to AndroidManifest.xml
• Adding a string property for each key to res/values/strings.xml
• Adding a new xml file app_restrictions.xml to res/xml/

I'll report back in after I hear from my customers

[ghuang0207]

To @theaccordance Joe, Thank you very much for all the help!

Actually all we need was just for Airwatch to send us "EnrollmentUser" key and value (string). But I don't know how to configure the app_restrictions.xml to do that. Or can I not set any restriction for the app?

platforms/android/res/xml/app_restrictions.xml