Merge pull request #30 from CAAPIM/develop

Develop

README.md

@@ -81,7 +81,7 @@ The Mobile SDK for Android is now compatible with ProGuard, the open source tool
 | Issue or Limitation                      | Description                              | Workaround                               |
 | :--------------------------------------- | ---------------------------------------- | ---------------------------------------- |
 | DE388462: Special characters in email addresses | MAG, OTK, and the Mobile SDK supports special characters in email addresses as noted in the RFC 1779. However, the MAG and OTK do not support the following characters: & \| | None.                                    |
-| US466920: All SDKs Errors on specific devices | If you have unexplained or intermittent SDK errors that occur only on specific devices, environments or settings, it may be because users are using an unsupported version of the platform, or they have tampered with or customized the device. The Mobile SDK is tested only on devices using official platform versions.  When devices are tampered with or customized, the SDK can behave in unexpected ways. | Check that users are using a supported version for their platform. Next, verify that users have not jailbroken or unlocked the OS (iOS), or customized the device ROM (Android). If either case is true, users should upgrade to a supported version of their platform. |
+| US466920: Errors on specific devices     | Unexplained or intermittent SDK errors occur only on specific devices, environments, | 1. Check that users are using a supported version for their platform. The Mobile SDK is tested only on devices using official platform versions.<br>2. Verify that devices are built using native SDKs. The Mobile SDK only supports devices built using native SDKs. (For example, some Huawei devices add plugins and use different libraries).</br>3. Verify that users have not jailbroken or unlocked the OS (iOS), or customized the device ROM (Android).</br><br>If any of these are true, the user must move to supported devices and versions.</br> |
 | Request with client certificate on HTTP 403 fails | If the MAG/OTK is configured to generate an HTTP 403 error, and the client certificate is configured for mutual SSL, the Apple Transport Layer determines that the certificate is bad and kills the entire transaction with the following error: `FAILED: Error Domain=NSURLErrorDomain Code=-1206 "The server “our.server.here” requires a client certificate.` | Developers can workaround the bug in their app, or Admins can change all HTTP status codes from 403 to another status code. |
 | MCT-177: All SDKs Social login limitation | The current social login implementation supports user profiles. The Mobile SDK libraries MASIdentity (Users and Groups) and MASConnecta (Messaging/Pub/Sub) do not support social login. | To integrate social login with an Identity Provider (for example, LDAP), you must create a custom policy. Contact Services for help with customizing policies for IDPs. |