04-09-2011 10:19 PM
I signed and submitted an app before the 9.4 sdk was released. After it was approved, I waited to recompile with the new sdk, thinking there might be yet a later version before the tablets were released. That seems unlikely now so I have recompiled and tested with 9.4 and am trying to sign this version. I increased the version number in the -app.xml, recompiled, made a new bar, verified that the sdk version and app version had been changed in the manifest. The simulator can tell that this and the old one are different versions (ids are different). I tried to sign it on the signing server using the same .p12 file as for the first version. Got the error:
Error = Code signing request failed because this file has been previously signed
What did I forget? I seem to be following the recommendations here:
and elsewhere on the forum.
Thanks for any help.
04-09-2011 10:27 PM
04-09-2011 10:55 PM
I ran into a similar problem. Are you using any of the same files that were on the previous .bar? If so, repackage the app using the original files as a source instead.
Hope this helps.
04-10-2011 04:22 PM
I had already seen the thread that mentioned the .sig file and deleted it. It seems to be recreated with every failed attempt but I always get rid of it.
Maybe that link does help. It seems to contradict the recommendation from the thread I referenced in my original post. In your post you say to repeat the csksetup and run the keytool again. I didn't do that. I did try signing with a newly created .p12 file but have never repeated csksetup. Am I supposed to?
Thanks in advance.
04-10-2011 04:30 PM
@arby: I highly recommend you do not repeat the registration process using the same .csj file. it will most likely corrupt your db file and you will be forced to order a new set of keys. it's happened before.
04-10-2011 04:37 PM
can you try to extract the contents of your .bar file and check the manifest file? also here's what you should do:
04-11-2011 04:11 PM
MSohm posted on another thread that the server had sometimes(?) been causing this problem and elsewhere that there is to be server maintenance tonight. I'll let this rest and try again tomorrow.
04-11-2011 04:29 PM
Probably a good idea. Yesterday I continuously got this error and the only solution was to keep re trying until it worked. Hopefully the maintenance tonight will fix this.