언어 설정

Menu
Sites
Language
Different author signature is preventing me to upgrade my app on store
Hi Tizen Devs !!
I am unable  to upload the updated build 1.1.0 for my game using SDK 2.2.1 on Tizen Seller Office due to different author signature. 
 
What I can do now although I am using the same secure profile. Any advise?
 
In the SDK 2.2.1 I am providing the same secure profile and the relavent password for signing but on uploading it I got the error stating different author signature. Due to which the only option I have is to upload it as a new application instead of upgarding the previous one. Of course to have same name I have to delete the previous version  1.0.0 . 
 
I have the complete source code folder of previous version. Can it help me just to verify either I am using the same secure profile or not?
Is it just the secure profile with password only thing that make your author signature?
 
Any assistance in this regard.
 
thnak you,

 

Responses

5 댓글
Dinh Hao

I have to make a virtual marchine and install sdk in it. Just to build package because I re-install my OS frequently. This rule suck, I dont understand why we have to have a same signature to upgrade our apps. I developed alot of application before and now I have to make a virtual marchine to re-upload everything (and have to keep that VM forever) because i dont remember what information i provide to make previous signature.

Athar Nouman

In my case even I did save the p12 file and its password on email bur still the combination of them is generating different signature in new SDK. I am almost sure about it. Anyways let see.

Dinh Hao
I know. VM is just my only choice.
I have the same problem. I formatted my pc, so i lost the previous certificate. Now i can not upload the binary. please help some one...

I don't understand the problem. I am using the same the secure profile since SDK 2.0 on different OSs (Windows and Ubuntu)

I have upgraded my apps recently to 2.2.1 with same profile and password and had no error