Signing problem after update to Rev4

After update SDK to 2.4 Rev4 signing app in Unity doesn’t work.

I was trying make new certyficates, reinstall all, but still I can sign application.

UnityException: Build Failure!
Failed to sign and package the application. Check the editor log for more details.
UnityEditor.Tizen.TizenUtilities.ShowErrDlgAndThrow (System.String title, System.String message, System.Exception ex) (at /Users/builduser/buildslave/unity/build/PlatformDependent/TizenPlayer/Extensions/Managed/TizenUtilities.cs:64)
UnityEditor.Tizen.TizenUtilities.ShowErrDlgAndThrow (System.String title, System.String message) (at /Users/builduser/buildslave/unity/build/PlatformDependent/TizenPlayer/Extensions/Managed/TizenUtilities.cs:58)
UnityEditor.Tizen.PostProcessTizenPlayer.PostProcess (BuildTarget target, System.String stagingAreaDataUpperCase, System.String stagingArea, System.String stagingAreaDataManaged, System.String playerPackage, System.String installPath, System.String companyName, System.String productName, BuildOptions options) (at /Users/builduser/buildslave/unity/build/PlatformDependent/TizenPlayer/Extensions/Managed/BuildPostProcess.cs:178)
UnityEditor.Tizen.TizenBuildPostprocessor.PostProcess (BuildPostProcessArgs args) (at /Users/builduser/buildslave/unity/build/PlatformDependent/TizenPlayer/Extensions/Managed/ExtensionModule.cs:53)
UnityEditor.PostprocessBuildPlayer.Postprocess (BuildTarget target, System.String installPath, System.String companyName, System.String productName, Int32 width, Int32 height, System.String downloadWebplayerUrl, System.String manualDownloadWebplayerUrl, BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/PostprocessBuildPlayer.cs:316)
UnityEditor.HostView:OnGUI()

I didn’t change anything in app setings. Before update I was able to make build and run app on Samsung Z1.

Is there any more information in the editor log or in
tizen-sdk/tools/ide/ncli.log?

I have seen this error as well and have some work done to correct it. I just want to make sure that we are both seeing the same issue

2016-03-11 00:29:20,398 [ERROR] Main.java(147) -
2016-03-11 07:35:13,381 [TRACE] Main.java(85) - Start running Tizen CLI Main class…
2016-03-11 07:35:13,384 [TRACE] Main.java(86) - Argument count:4
2016-03-11 07:35:13,393 [TRACE] ConfigCLI.java(78) - Execute configCLI…
2016-03-11 07:35:13,398 [TRACE] NCLIConfigLoader.java(102) - isConfExist:true
2016-03-11 07:35:13,404 [TRACE] NCLIConfigLoader.java(102) - isConfExist:true
2016-03-11 07:35:14,084 [TRACE] Main.java(85) - Start running Tizen CLI Main class…
2016-03-11 07:35:14,087 [TRACE] Main.java(86) - Argument count:9
2016-03-11 07:35:14,095 [TRACE] PackageCLI.java(221) - Execute PackageCLI…
2016-03-11 07:35:14,097 [TRACE] PackageCLI.java(226) - getRealWorkingPath: C:\Users\Coolmer\Desktop\Unity\2Cars\Temp\StagingArea\build
2016-03-11 07:35:14,104 [TRACE] NCLIConfigLoader.java(102) - isConfExist:true
2016-03-11 07:35:14,108 [TRACE] NCLIConfigLoader.java(102) - isConfExist:true
2016-03-11 07:35:14,112 [DEBUG] PackageNativeCLICommand.java(306) - Base project directory: C:\Users\Coolmer\Desktop\Unity\2Cars\Temp\StagingArea
2016-03-11 07:35:14,121 [ERROR] AbstractCLI.java(92) -
java.lang.NullPointerException
at org.tizen.ncli.ide.subcommands.PackageNativeCLICommand.call(PackageNativeCLICommand.java:101)
at org.tizen.ncli.ide.subcommands.PackageNativeCLICommand.call(PackageNativeCLICommand.java:31)
at org.tizen.ncli.ide.subcommands.AbstractSubCommand.runCommand(AbstractSubCommand.java:76)
at org.tizen.ncli.ide.shell.PackageCLI.execute(PackageCLI.java:790)
at org.tizen.ncli.ide.shell.AbstractCLI.execute(AbstractCLI.java:90)
at org.tizen.ncli.ide.shell.Main.run(Main.java:141)
at org.tizen.ncli.ide.shell.Main.main(Main.java:73)
2016-03-11 07:35:14,123 [ERROR] Main.java(147) -

Hello,

FYI I have exactly the same issue with Rev4, same error in ncli.log. I am developing on smart watch Samsung Gear S2. A possible workaround is to uninstall Rev4 and install a previous SDK (available here). It would be great if you could give a bug fix estimate date, just to know if it’s worth the pain (I hate setting up these Tizen certificates).

I was trying uninstall Rev4 and install Rev3, but still I have the same problem.

1 Like

Ok good. That’s the same error that I saw. I will give more information about the fix date as soon as I know.

Ok, looking forward! My project is pending until this bug fix.

And thanks Apogee for sharing your experience, I won’t waste time trying Rev3.

I have the same problem, I already test it with multiples versions of Unity, Tizen Rev2, Rev3 and Rev4, and I’m using a Mac. Do you guys have any news about that problem? Someone made a fix for that?

We are still waiting.

Best Regards,
Mariusz Kulma

You can fix this problem manually by doing this:

  1. go to Temp\StagingArea in your Unity folder
  2. rename folder “build” into “bin”
  3. zip content of StagingArea folder and call that zip file “tizen.tpk”. In the root of this zip file you should have \bin \data \lib and so on
  4. run “tizen.bat package” on this new tizen.tpk file and then use “sdb install” to install this new file

You can copy and modify “tizen.bat package” run command from unity build output and modify that command to use tizen.tpk
In my example I have use this command:

tizen-sdk\tools\ide/bin/tizen.bat package – “D:\Unity\Tizen2\Temp\StagingArea\tizen.tpk” -t tpk -s tizensignalias

I have use Unity 5.3.4f and Tizen SDK 2.4 rev 4 with Samsung Z3 and it works as expected.

Best regards
Bojan

1 Like

Skaljac - it’s work, but I had to generate new certificate, so I can’t upgrade my previus app.
When I use old certificate I get info “Invalid password” (log file), but when I was building app with Rev3 direct from Unity, password was correct.
I didn’t chage anything.

UPDATE: I had to rebuild distributor.p12 in previus certificate and now it’s work.

Best Regards,
Mariusz K.

Thanks for sharing your experience guys, unfortunately skaljac and Apogee tricks don’t work for me, I’m still blocked by an Invalid password certificate exception.
Masterfalcon could you update us? It’s quite critical, we are basically blocked on our Tizen project.

Best,
Nicolas

I’m facing the same issue, Nicolas have you got any other solution other than Bojan suggested.

Regards,
Karan

Hi Karan, no I’m still blocked on that side.

Update: with Unity 5.3.4f1, and after creating totally new certificates from scratch, I have been able to use Bojan’s trick. Luckily our app is not on the store yet so it’s not super critical, but it is still disturbing.

I haven’t seen this issue with Tizen SDK 2.4rev5.

If I understand correctly, the way to resolve this is to uninstall the Tizen SDK and then install the most recent version. You can reuse your Tizen data directory that contains the certificates. You may or may not need to recreate them.

Samsung changes some details of the signing process from time to time and that can cause breakage with Unity.

Hi Nicolas,
I resolved the issue by removing the 2.4 rev4 and using the 2.4, my app is live too :slight_smile:

But now a new challenge, I cannot fing a URL to my app on tizen store, so I’m not able to pop a rate us or do cross promotion in my app.

Regards,
Karan

resolved… its

Application.OpenURL (“tizenstore://ProductDetail/YOUR_PACKAGE_ID”);

still have this issue with Unity 5.4 and 2.4 rev8.

I got
"
There is no default profiles value in config file.

Package( ~/Temp/StagingArea/tizen.tpk ) is created successfully.


Finished package
"
when using tizen.bat package.

and after this I use sdb install I got this error
"
__return_cb req_id[34310002] pkg_type[invalid] pkgid[Invalid package] key[start] val[install]

__return_cb req_id[34310002] pkg_type[invalid] pkgid[Invalid package] key[end] val[fail]

processing result : FATAL_ERROR [61] failed
"

How to solve this problems?
I’m using Unity 5.4 and 2.4 rev8.