You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then use the [MX access manager](https://techdocs.zebra.com/mx/accessmgr/)to allow your application to call the service identifiers associated with the serial number and IMEI
16
+
Then add the uses-library element to your application
16
17
17
-
The MX access manager settings to enable this are as follows:
18
-
- Service Access Action: "AllowCaller" (or 'Allow Caller to Call Service')
19
-
- Service Identifier: For the serial number use content://oem_info/oem.zebra.secure/build_serial. For the IMEI use content://oem_info/wan/imei. If you want to allow your app access to both, you will need to declare two different instances of the AccessManager.
20
-
- Caller Package Name: Your package name, in the case of this sample it is com.zebra.emdk_deviceidentifiers_sample.
21
-
- Caller Signature: The signing certificate of your application. For more information on generating this see https://github.com/darryncampbell/MX-SignatureAuthentication-Demo.
22
-
23
-
You can apply the MX access manager settings in one of three ways:
24
-
1. Via StageNow
25
-
2. Via your EMM
26
-
3. Via your application, using the EMDK Profile Manager.
27
-
28
-
For example, StageNow will look as follows to enable access to the serial number:
If you failed to correctly allow your application access to oem_info service, you will see an error stating so against each property you did not assign access to, as shown below:
0 commit comments