Tizen platform builds are failing.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Start a new rnv project with rnv new;
2. Cd to the newly created project folder and issue the command: rnv run -p tizen;
3. Check the tizen cli logging output attached in the Screenshots or copy&paste section.

Expected behavior Rnv run and/or build scripts should produce valid targets.

Screenshots or copy&paste Logger output from Tizen cli, written to when running rnv run -p tizen: cli.log

Desktop (please complete the following information):

• OS: Windows 10 Pro
• Node Version v12.16.1
• RNV Version 0.30.4

Additional context This seems to happen when generating certificate profiles and across several versions of node and/or rnv, has occurred on more than one machine. Judging from the Java exception trace, this seems to involved arguments not being properly passed to the relevant class method, i.e. org.tizen.ncli.subcommands.sign.SignCLICommand.getSigningProfile, when signing build products. This happens on both new and existing installations of Tizen SDK.

[damakvarshney]

I found the solution … the problem is with distributor password in tizen studio which can be solved just by going to tizen studio and then to certification manager and write distributor password to “tizenpkcs12passfordsigner”

Good luck

[pavjacko]

@damakvarshney thank you for reporting the solution back!