I am completely lost - I get a error 400 while building my package, but without any details. Anyone seen this before?
AxiosError: Request failed with status code 400: {“requestId”:“7258709491559177405”,“error”:{“code”:“BadRequestError”,“message”:“Invalid device profile
specification for 23967c74-d512-4880-95bf-8aa2405c597b”,“details”:}}
Quite new to all this, so please let me know what info you need to help me debug.
Okay - seems like the same problem, but I have copied the name directly from CLI prompt. The problem is with either the reference or the capability itself, because when I change the capability id to a standard capability e.g. switch the problem is gone. Is it possible to have an error in a capability that is installed without errors?
Hi, @Meltinis!
It has happened in the past that some capabilities are faulty for some reason and cause issues when trying to use them but there’s no apparent error. Could you share your custom capability ID, please?
ok, I did some tests and the issue is that your capability doesn’t have a presentation. It might sound strange why the profile cares about this, but remember that in Edge drivers, we can use embedded device configurations.
So, I think (because I don’t have all the information) that when we package the driver, the presentation for such profile is created if we don’t include one in the metadata. Therefore, as your capability doesn’t include a presentation, the process fails. (I’ll confirm this with the engineering team)