I’ve tried signing the command line packaged app for some time now, but so far without a success. When the package is re-packaged using IDE (as per suggestion), it works. However, to fully integrate the signing into development process, it needs to be doable via command line.
Certificate: Created .p12 file using both IDE and command line tools. No difference in outcome.
Updated profiles.xml (following the IDE generated profiles.xml)
Building & signing: Using web-build and webtizen commands
Package contents seems same when comparing the outcome with both CLI and IDE-packaged versions. Only the hashes in XML file are changed, not the contents themselves.
The error that I’m getting: CERTIFICATE_INVALID [33]. I also tried putting the CLI -generated signature files into IDE -based WGT -package, but then error was: SIGNATURE_INVALID [22].
Therefore: Any hints where to look in a case of error: 33?
CLI certified package considered invalid [33]
UPDATE: Issue solved, see end of the thread.
I’ve tried signing the command line packaged app for some time now, but so far without a success. When the package is re-packaged using IDE (as per suggestion), it works. However, to fully integrate the signing into development process, it needs to be doable via command line.
The error that I’m getting: CERTIFICATE_INVALID [33]. I also tried putting the CLI -generated signature files into IDE -based WGT -package, but then error was: SIGNATURE_INVALID [22].
Therefore: Any hints where to look in a case of error: 33?
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio
BY
30 Oct 2023
Tizen Studio