When executing the manifest-tool update device command as suggested in the tutorial, an Invalid API key error occurs. This is strange because the API key should be valid as my device is successfully registered to Pelion. The _.manifesttool.json and _.mbed_cloudconfig.json seem to be correctly filled as well.
Target(s) affected by this defect ?
K64F + I-NUCLEO-S2868A1
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM - gcc-arm-none-eabi-9-2019-q4-major
What version of Mbed-os are you using (tag or sha) ?
Mbed-OS 5.15
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.2
How is this defect reproduced ?
The problem can be reproduced by running the manifest-tool update device on the mbed-cloud-client-example application. The error log is attached.
Description of defect
When executing the
manifest-tool update devicecommand as suggested in the tutorial, an Invalid API key error occurs. This is strange because the API key should be valid as my device is successfully registered to Pelion. The _.manifesttool.json and _.mbed_cloudconfig.json seem to be correctly filled as well.Target(s) affected by this defect ?
K64F + I-NUCLEO-S2868A1
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM - gcc-arm-none-eabi-9-2019-q4-major
What version of Mbed-os are you using (tag or sha) ?
Mbed-OS 5.15
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.2
How is this defect reproduced ?
The problem can be reproduced by running the
manifest-tool update deviceon the mbed-cloud-client-example application. The error log is attached.manifest-tool-update-device-error_log.txt