createApnSettings returns -1 ‘Invalid MVNO type’ error

Environment

• Knox SDK
• Knox 3.4 (API Level 29)

Overview

When creating or updating the APN Settings with the Knox SDK methods ApnSettingsPolicy.createApnSettings or ApnsSettingsPolicy.updateApnSetting, the return value is -1, Invalid MVNO type.

The following error appears in the log file:

ApnSettingsPolicyService: Invalid mvno type!
ApnSettingsPolicy: createApnSettings: -1

The ApnSettings object passed as a parameter to the method also has its mvno_type field set as a string value that is not:

• empty string
• MVNO_SPN
• MVNO_IMSI
• MVNO+GID

Cause

There are two reasons for the invalid MVNO type error:

1. From Knox API Level 29 (Knox version 3.4/Android P), ApnSettings.mvno_type and ApnSettings.mvno_value are required fields. If the APN does not require a MVNO type and value, you must enter empty strings in the MVNO type and value fields.

2. Due to a defect, the Knox framework was unable to configure ApnSettings.mvno_type and ApnSettings.mvno_value fields on the device.

Resolution

For customers to be able to configure or update their APN Settings, ensure the conditions below are met:

1. On devices running Knox 3.4 and higher, your UEM partner must update their implementation to support the mvno_type and mvno_value fields in the ApnSettings class. For details, please refer to the Knox SDK documentation.

2. The customer must update the firmware containing the fix that allows the MVNO type and value to be set with the Knox SDK.

Additional information

If you require further troubleshooting assistance, please raise a support request through the Knox Admin Portal with the following details:

• A device dumpstate captured after the APN is created

• A list of all the APNs and the value of each APN field (obtained by inserting the SIM card into a device and listing the values from the device’s Settings app)