fixed wrong api called when install writable prealod app encrypted.
authorSoyoung Kim <sy037.kim@samsung.com>
Tue, 15 Oct 2013 06:19:50 +0000 (15:19 +0900)
committerGerrit Code Review <gerrit@gerrit.vlan144.tizendev.org>
Thu, 17 Oct 2013 07:25:15 +0000 (07:25 +0000)
commit9085d5a5cf9034b843794169e3a002c3ae6f48e7
treeb9ea26fcb796c3f9d12249f07240ce89aafb9536
parent56cb6980f7043d68ef19d2d0a20e8d68837afb93
fixed wrong api called when install writable prealod app encrypted.

[Issue#] N/A
[Problem] can't install writable preload app during building image.
[Cause] failed to encrypt resource because wrong api was called at encryption.
[Solution]
- There are encryption api separated with preload and download.
(ssm_encrypt_preloaded_application(), ssm_encrypt_application())
- So preload encryption api is called when installing writable preload app.
[SCMRequest] N/A

Change-Id: I67fa5721c317b5a5fb9a1c2d881bf3fa522d8a03
src/jobs/widget_install/task_encrypt_resource.cpp