- *BASICS*
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Introduction
- Accept or reject devices
- Upload devices
- Delete devices
- Complete payment
- Send payment overdue notification
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQ
- KBAs
- Support
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
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:
- 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.
- 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 below conditions are met:
- 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.
- The customer must update the firmware containing the fix that allows the MVNO type and value to be set with the Knox SDK.
NOTE—The below list shows some common device models and their build numbers, but is not exhaustive. Please contact Samsung Knox Support for the build number of your particular device model.
Device |
Region |
Model Number |
Build number |
| Galaxy Note10+ | Europe | SM-N975F | N975FXXU1ASHE |
| Galaxy Note10+ | United States | SM-N975U | N975USQU1ASHB |
| Galaxy Note10 | Europe | SM-N970F | N970FXXU1ASHE |
| Galaxy Note10 | United States | SM-N970U | N970USQU1ASH4 |
| Galaxy Note9 | Europe | SM-N960F | N960FXXU3CSI3 |
| Galaxy Note9 | United States | SM-N960U | N960USQU2CSI1 |
| Galaxy S10e | Europe | SM-G970F | G970FXXU3ASIG |
| Galaxy S10e | United States | SM-G970U | G970USQU2BSIO |
| Galaxy S10 | Europe | SM-G973F | G973FXXU3ASIG |
| Galaxy S10 | United States | SM-G973U | G973USQU2BSIO |
| Galaxy S10+ | Europe | SM-G975FC | G975FXXU3ASIG |
| Galaxy S10+ | United States | SM-G975U | G975USQU2BSIO |
| Galaxy S9 | Europe | SM-G960F | G960FXXS7CSI5 |
| Galaxy S9 | United States | SM-G960U | G960USQU6CSI2 |
| Galaxy S9+ | Europe | SM-G965F | G965FXXU7CSK1 |
| Galaxy S9+ | United States | SM-G965U | G965USQU6CSI2 |
Additional information
If you require further troubleshooting assistance, please raise a support request through your Knox dashboard 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)
