Description of problem:
I am able to run Tizen applications on actual test devices. However, when I try to run an app on an emulator, I get the following error:
Error code: SIGNATURE_INVALID
Error message:
Command: /usr/bin/pkgcmd -i -q -t wgt -p "/opt/usr/apps/tmp/Milk.wgt"
Management: Check author certificates in Preferences > Tizen SDK > Secure Profiles > Profile items.
Here are some of the things I have tried (none of them work):
----
Setting the system time correctly in the emulated device
Adding the emulator device ID to my device-profile.xml file in ~/tizen-wearable-sdk-data/keystore/device-profile.xml, then putting this on the emulator device in home/developer, then restarting the emulator. [Interestingly, on an actual device, home/developer is empty and I can run programs fine; I did a find and no certificate-registration.xml or device-profile.xml file exists anywhere on the actual device either.]
[I do not have and never received a certificate-registration.xml file. I have only recently started developing on Tizen. If I need that file, and it is now not possible to get it any more, does anyone feel like sending me an extra one?]
Switching workspaces (After doing so, I tried generating and using my own certificate in the IDE. That gives me a different error:
Error code: PRIVILEGE_LEVEL_VIOLATION
Error message:
Command: /usr/bin/pkgcmd -i -q -t wgt -p "/opt/usr/apps/tmp/MilkO.wgt"
Management: Refer to Help contents > Getting Started with Tizen > Overview > Privilege.
If I go back to the certificate I was using before, I also get this same PRIVILEGE_LEVEL_VIOLATION error.)
Rebooting, reinstalling the SDK
Using different .x86 emulator images
Following a hack I found in a Tizen forum whereby running the same program in an emulator and actual device at the same time tricks it into working (https://developer.tizen.org/forums/web-application-development/error-signature_invalid-after-updating-sdk-2.2.1, post by meng zhang)
Going into profiles.xml and setting the correct directories for certificates
-------------
To the best of my knowledge, no files in the project have non-ASCII characters in them.
Do we have to request certificates that include the device IDs (DUIDs) of all emulators we create? Where does the new IDE store the device IDs?
Does anyone know what else I could try, or barring that, where I can get previous versions of the SDK? All the certificate documentation references the old version of the SDK and hence is now useless. (To everyone: omg, do not upgrade. The debugger doesn't even work half the time in the new SDK.)
Thanks for any help anyone can provide.
What I am running:
Mac OS 10.9.5, Tizen SDK 2.3.0_Rev2, build id: 20150121-1659 (I will now try to use TizenSDK 2.3.0 Rev1 WC1 RC4 R3, though the last time I used Rev1 I was unable to run apps on normal devices, so I may end up using Rev2 again.)