Help Center>
IoT Device Management>
FAQs>
Secondary Development>
FAQs About Product Development>
Plug-In Development>
Failed to Deploy a Plug-in That Is Developed Offline
Updated on 2022-02-24 GMT+08:00
Failed to Deploy a Plug-in That Is Developed Offline
- Use the NB-IoT codec plug-in check tool to check the plug-in.
- Rectify the fault based on the error code returned by the tool. For details about how to handle the error codes, see the NB-IoT Codec Plug-in Check Tool Instructions in the tool package.
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
