Help Center>
IoT Device Management>
FAQs>
Secondary Development>
FAQs About Product Development>
Plug-In Development>
Codec Exception Occurs After a Plug-In Package Developed Offline That Has Been Checked Is Uploaded to the IoT Platform
Updated on 2022-02-24 GMT+08:00
Codec Exception Occurs After a Plug-In Package Developed Offline That Has Been Checked Is Uploaded to the IoT Platform
- This fault is caused by the plug-in code. Generally, the dependency is not introduced or the code logic is incorrect. You can rectify the fault based on the Java exception prompt in the log.
- Print logs at the key code of the offline plug-in (for example, at the entrance and exit of the decode function), and contact IoT platform personnel to obtain logs in the background to locate the fault.
Figure 1 Example logs
Parent topic: Plug-In Development
Plug-In Development FAQs
- How to Develop Codecs
- Failed to Deploy a Plug-in That Is Developed Online
- What Is the Code Rule for Fields of the string and varstring Types
- What Is the Code Rule for Fields of the array and variant Types
- Whether Plug-Ins That Are Developed Online Support Transparent Transmission
- How to Use messageId During Online Codec Development
- How to Configure a Command Delivery Response During Online Codec Development
- Failed to Deploy a Plug-in That Is Developed Offline
- Failed to Upload a Plug-in That Is Developed Offline
- Plug-In Package Developed Offline Has Been Checked But Cannot Be Found When Uploading to the IoT Platform
- Codec Exception Occurs After a Plug-In Package Developed Offline That Has Been Checked Is Uploaded to the IoT Platform
- Offline Signature Fails
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore