HarmonyOS SDK Error Codes
Last updated:2024-09-03
HarmonyOS SDK Error Codes
For inner error codes, see Carrier Error Codes.
| code | message | Notes |
|---|---|---|
| 1000 | verify consistent | Phone number verification consistent |
| 1001 | verify not consistent | Phone number verification inconsistent |
| 1002 | unknown result | Unknown result |
| 1003 | token expired | Token expired |
| 1004 | sdk verify has been closed | SDK-initiated verification is not enabled |
| 1005 | Package name and AppKey mismatch | Ensure the client package name matches the package name configured for this AppKey on the portal |
| 1006 | frequency of verifying single number is beyond the maximum limit | Daily verification quota exceeded for this number |
| 1007 | beyond daily frequency limit | Daily verification quota exceeded for this AppKey |
| 1008 | AppKey illegal | Check the AppKey in app details on the portal |
| 1009 | - | Check app details on the portal; update the integrated Jiguang SDK to the latest version |
| 1010 | verify interval is less than the minimum limit | Verification interval for the same number is too short |
| 1011 | appSign invalid | Invalid app signature; ensure it matches the portal configuration |
| 2000 | content is token | Token obtained successfully |
| 2001 | fetch token failed | Failed to obtain token |
| 2002 | init failed | SDK initialization failed |
| 2003 | network not reachable | Network unavailable |
| 2004 | get uid failed | Jiguang service registration failed |
| 2005 | request timeout | Request timed out |
| 2006 | fetch config failed | Failed to fetch app configuration |
| 2007 | content is exception info | Exception during verification |
| 2008 | Token requesting, please try again later | Token request in progress; try again later |
| 2009 | verifying, please try again later | Verification in progress; try again later |
| 2010 | don't have READ_PHONE_STATE permission | READ_PHONE_STATE permission not granted |
| 2011 | content is exception info | Exception while fetching configuration |
| 2012 | content is exception info | Exception while obtaining token |
| 2013 | content is specific error reason | Network exception |
| 2014 | internal error while requesting token | Internal error while requesting token |
| 2016 | network type not supported | Current network does not support verification |
| 2017 | carrier config invalid | Invalid carrier configuration |
| 2018 | Local unsupported operator | Unsupported local carrier |
| 3000 | SMS verification code obtained | SMS verification code obtained successfully |
| 3001 | not initialized | SDK not initialized |
| 3002 | invalid phone number | Invalid phone number |
| 3003 | requests too frequent | Interval between two requests is shorter than the minimum limit |
| 3004 | unknown error | Request error; see msg for details |
| 4001 | parameter invalid | Parameter error; check parameters such as phone number format |
| 4014 | appkey is blocked | Feature disabled |
| 4018 | - | Insufficient balance |
| 4031 | - | Not a JVerification SDK user |
| 4032 | - | Unable to fetch user configuration |
| 4033 | appkey is not support login | One-click login not enabled (configure RSA public key under Authentication Settings → One-Click Login) |
| 5000 | bad server | Unknown server error |
| 6000 | content is token | loginToken obtained successfully |
| 6001 | fetch loginToken failed | Failed to obtain loginToken |
| 6002 | fetch loginToken canceled | User canceled loginToken request |
| 6003 | UI resource load error | Required SDK resource files were not added correctly |
| 6004 | authorization requesting, please try again later | Login in progress; try again later |
| 6006 | prelogin scrip expired. | Pre-login cache expired; pre-login again |
| 7000 | preLogin success | SDK pre-login succeeded |
| 7001 | preLogin failed | SDK pre-login failed |
| 7002 | preLogin requesting, please try again later | Pre-login in progress; try again later |
| 8000 | init success | Initialization succeeded |
| 8004 | init failed | Initialization failed; see logs |
| 8005 | init timeout | Initialization timed out; try again later |
| -994 | network connection timeout | - |
| -996 | network disconnected | - |
| -997 | registration failed / login failed | Usually caused by no network. If the network is fine and the issue persists, JPush server may reject registration because the HarmonyOS package name or AppKey does not match the app registered on the portal. |
Was this document helpful?