Frequently Asked Questions

Kony Management 8.2.0 wrapping script supports AAPT. If you build an Android application with Visualizer SP2, the application is not wrapped in Kony Management. This is because Visualizer V8 SP2 uses Gradle version 3.0.x which by default uses APPT2. Android applications built with AAPT2 do not work with AAPT. To solve the issue, you must disable AAPT2 in Kony Visualizer.

To disable AAPT2 in Kony Visualizer, do the following:

1. In your Visualizer project, navigate to Project Settings > Native > Android.
2. In the Android tab, navigate to the Manifest Properties & Gradle Build Entries section.
3. Click the Gradle Entries tab.
4. In the gradle.properties entries: section, enter the following text.
   android.enableAapt2=false
5. Click Finish.

On iOS devices, Kony Enterprise Store app takes five minutes time to send the data logs to the server about status of user action (Install or Cancel) on installing a child app on the device to Kony Management Administrator console. If you have canceled the child app installation, you might still see the status of the install process as Installing on the enterprise store on the device. If you check the status after five minutes, the status will be refreshed and you will see an Install option.

You can send notifications to all devices enrolled in Kony Management suite by creating devices sets. Once you have a device set, you can send messages to all devices in that device set.

Important: You can only send messages to devices that are enrolled in EMM enrollment mode.

Note: For devices enrolled in MAM/MCM mode, you must send a bulk email through your email service.

• Sending a message to all devices
• Sending a message to all iOS devices
• Sending a message to all Android devices

For more information on sending push notifications and email messages, refer Kony Management User Guide.

Sending a Message to All Devices

To send a message to all devices, do the following:

1. In Kony Management admin console, under Device Management, click Device Sets. The Device Sets page opens with the list of existing device sets. By default, an All Devices set exists.
   
2. Click All Devices. The All Devices set details page opens with the Description tab open by default.
   
3. Click Messages. The Messages tab opens.
   
4. Click New Message. The Compose Message page appears.
   
5. In the Send As field, select Push Notification.
6. In the Message Box, enter your message.
7. Click Send. The Send Message - Success message appears.
8. Click OK. Your message is sent to all devices in the device set.

Sending a Message to all iOS devices

To create a new device set for iOS and send a message to all iOS devices, do the following:

1. In Kony Management admin console, under Device Management, click Device Sets. The Device Sets page opens with the list of existing device sets.
2. Click + New Device Set next to the Device Sets label at the top of the page.
   
   
   The New Device Set window appears.
   
3. In the Device Set Name field, enter iOS Devices.
4. In the Description field, enter a brief description for the device set.
5. Click Create & Edit. The Device Set Details page opens with the Description tab open by default.
   
   
6. Click Conditions tab. The Conditions tab opens.
   
7. From the Device Parameter list, select Operating System.
   
8. From the Device Attribute list, select Platform.
   
9. Leave the Condition list as is to Equal To.
10. From the Definition list, select iOS.
    
    The condition is added.
    
    
11. Click the Condition number to add it to the Definition set.
    
12. Click Validate & Search. All devices that meet the definition criteria set will appear below.
13. Click Save & Activate. The device set page appears with the newly created device set in the list.
    Note that the state of the device set is set to Active.
14. From the Status column of the device set, click Published to publish the device set.
    
    The Status Change dialog appears.
    
15. Click Published to publish the device set. The Status Change dialog appears.
    
16. Enter your comments in the page and click Publish. A status change message appears.
17. Click OK.
18. Click the device set. The Device Set Details page appears.
19. Click Messages. The Messages tab opens.
    
20. Click New Message. The Compose Message page appears.
    
21. In the Send As field, select Push Notification.
22. In the Message Box, enter your message.
23. Click Send. The Send Message - Success message appears.
24. Click OK. Your message is sent to all devices in the device set.

Sending a Message to all Android devices

To create a new device set for Android OS and send a message to all Android devices, do the following:

1. In Kony Management admin console, under Device Management, click Device Sets. The Device Sets page opens with the list of existing device sets.
2. Click + New Device Set next to the Device Sets label at the top of the page.
   
   
   The New Device Set window appears.
   
3. In the Device Set Name field, enter Android Devices.
4. In the Description field, enter a brief description for the device set.
5. Click Create & Edit. The Device Set Details page opens with the Description tab open by default.
   
   
6. Click Conditions tab. The Conditions tab opens.
   
7. From the Device Parameter list, select Operating System.
   
8. From the Device Attribute list, select Platform.
   
9. Leave the Condition list as is to Equal To.
10. From the Definition list, select Android.
    
    The condition is added.
11. Click the Condition number to add it to the Definition set.
    
12. Click Validate & Search. All devices that meet the definition criteria set will appear below.
13. Click Save & Activate. The device set page appears with the newly created device set in the list.
    Note that the state of the device set is set to Active.
14. From the Status column of the device set, click Published to publish the device set.
    
    The Status Change dialog appears.
    
15. Enter your comments in it and click Publish. A status change message appears.
16. Click OK.
17. Click the device set. The Device Set Details page appears.
18. Click Messages. The Messages tab opens.
    
19. Click New Message. The Compose Message page appears.
    
20. In the Send As field, select Push Notification.
21. In the Message Box, enter your message.
22. Click Send. The Send Message - Success message appears.
23. Click OK. Your message is sent to all devices in the device set.

 

Note: When there is a major release or hot fix deployed on Kony Management cloud, cloud deployment will take care of wrapping and creating a new version of the enterprise store as and if required.

Branding

Kony Management provides a default Branding set that can be used for an enterprise store for branding. When a new branding set is created or if an existing branding set is modified, when the new/modified set is applied on an enterprise store, the store is re-wrapped.

Specifically:

• Any change in the configuration of a Branding set which is assigned to an Enterprise Store will trigger wrapping for that Enterprise Store.
• Also, if a Branding set assigned for an Enterprise Store is changed to another Branding set, wrapping would trigger for that Enterprise store.

Application Settings – Certificates:

Modifications to any certificates in the Application settings triggers wrapping of enterprise apps and enterprise stores associated with those certificates.

• Android Key Store / Android Maps / Project ID – All Android and Android Tablet Platform Enterprise Stores and Enterprise Apps.
• IOS Enterprise Distribution Certificate – All iOS Enterprise Stores and Apps.
• IOS Wild Card Provisioning Profile – All iOS Enterprise Apps.
• IOS Enterprise Store Provisioning Profile – All iOS Enterprise Stores.
• Two-Way SSL Certificate – Android and Android Tablet and iOS Enterprise Stores would be re-wrapped.

Application Settings – Encryption Key:

Using the Encryption Key feature in the Application settings page, an administrator can generate new encryption keys or schedule an automated triggering of generating an encryption key.

When new encryption keys are generated, wrapping is triggered for enterprise stores and all “wrap and signed” enterprise apps would be triggered.

Note: Wrapping would be triggered for Android, Android Tablet and iPad and iPhone platforms.

Device Settings – Tracking Settings:

In the Device Settings page, when you modify the rule for the Enable Device Location Tracking feature, wrapping will be triggered.

Note: All Enterprise stores (All platforms) and Enterprise Apps (All platforms).

Authentication Settings – Kony Fabric Authentication settings:

In the Authentication Settings page, wrapping can be triggered in two scenarios.

• When you enable the Use Kony Fabric Identity feature, wrapping will be triggered for all Enterprise Stores (excluding windows platform).
• If the Use Kony Fabric Identity feature is already enabled, modifications to the following will trigger wrapping.
  • Change in the App Key/App Secret
  • Change to the Enable SSO feature
    • Android and Android Tablet – when Android Broadcast phrase is modified.
    • iPad and iPhone – when iOS Keychain group is modified.

• User name and password are stored in the device in encrypted form.
• Sensitive information (for example, Password) is masked when it is displayed on the screen.
• Sensitive data (for example, Password) is cleared from the forms when navigating away from the forms.
• All sensitive information is encrypted using industry standard SSL during access and transmission between client and server.
• Copy and Paste function is disabled for sensitive data (for example, Password).

• Sensitive data such as user name and password are not logged to the console or files (server/client side). Where required, the sensitive data is encrypted and moved into logs.
• Sensitive information like session IDs, user names are not printed in the logs.

• When you sign into the application the first time, you must be connected to the internet so that the application data and the latest version of the metadata around the application screens are fetched from the backend
• The application data and metadata are saved on the device. Each time a user performs a manual sync, the latest data is saved on the device.
• If a new user signs into the same device and from the same application, the previous user’s data is removed from the device and the new user’s data is saved.
• On subsequent log-in attempts:
  • If a user is online, the user credentials are validated against the backend.
  • If a user is offline, the user credentials are validated against the credentials stored in the device, and the last retrieved data and forms are displayed in the application.

• Session is created when a user signs in with valid credentials.
• Session also gets terminated if the application is force-closed.
• User session details are cleared from both device and server, when the session is terminated.

• Validation alerts are displayed for each field or rule (no consolidation).
• The app throws appropriate errors during device interrupts. For example, receive a call while in the middle of a session.

• Throughout the application, a user is shown a busy indicator with blocked page UI implemented as long as the processing is in progress.

• An administrator can configure wrapping server even after installation.
  • iOS: By modifying the hosts.properties file.
  • Windows: hosts_win.properties file.
  • Android: Same as the Android SDK ssetup on the installation computer.

• An administrator must configure four Apple MAC servers for fail-safe.

When Apple WWDR certificate expires, it impacts the Enterprise Distribution certificate. To continue to use it to sign apps, you must delete the old WWDR from the keychain on the signing Mac system. Please follow the steps given below:

1. Open Keychain access on the mac system.
2. Enable View>Show Expired Certificates.
3. Go to System Keychain and delete the expired WWDR certificate
4. Follow step number three for Login Keychain.
5. Import the new WWDR certificate into keychain.

• After you download the Kony Management Enterprise Store apk using any web browser, navigate to your Downloads folder on your android device.

• You can also use a file manager application to open the Kony Management Enterprise Store apk. The apk can be found on the Device storage in the Download folder. Using any file manager application freely available on the Google playstore, you can access the Download folder. Clicking the Kony Enterprise Store from the Download folder will install the Kony Management Enterprise Store app on your device.

The user’s device might be a rooted or jailbroken device. If your Device Settings is set to not allow rooted or jailbroken device, the user will not be able to log in through the enterprise store. In your device settings, if you have configured it to not allow jailbroken or rooted devices,

For iOS Devices

• Jailbroken devices will not be allowed to log in to the enterprise store. The user will receive a Cannot login on the device, please contact your administrator error message.

For Android devices

• If the device is hard rooted: Devices will not be allowed to log in to the enterprise store. The user will receive a Cannot login on the device, please contact your administrator error message.
• If the device is soft rooted (malicious apps installed on the device): Devices will not be allowed to log in to the enterprise store. The user will receive a Cannot login on the device, please contact your administrator error message. The user may have to uninstall any malicious apps and try logging in. In some cases a device reboot will be necessary after removing malicious apps before trying to login.

From V8 release, Kony Management does not support Java 7. If you upgraded from Java 7 to Java 8, Android wrapping may fail. If you encounter the following problem, see the solution available.

Exception in thread "main" brut.androlib.AndrolibException: java.io.IOException: The system cannot find the path specified
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:493)
at brut.androlib.Androlib.buildResources(Androlib.java:427)
at brut.androlib.Androlib.build(Androlib.java:326)
at brut.androlib.Androlib.build(Androlib.java:264)
at brut.apktool.Main.cmdBuild(Main.java:231)
at brut.apktool.Main.main(Main.java:84)
Caused by: java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createTempFile(Unknown Source)
at java.io.File.createTempFile(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:472)

To fix the wrapping fail problem, do the following:

1. Navigate to the catalina property file location. For example, <EMM-InstalledDirectory>/tomcat/conf/
2. Open the catalina.propertiesfile with a note editor.
3. Add the following towards the end of the file.
   java.io.tmpdir=<temppath>
   Replace <temppath> with some folder name of your choice.
   
4. Verify that the %temp% path exists by running appropriate commands in your windows server machine.
5. Restart the Tomcat server.
6. Re-wrap your Android application. It should work fine.