Skip to main content

Android Certificate/signing application



I tried to update my app on the android market and I got this error : The apk must be signed with the same certificates as the previous version.





Since I just had a couple of downloads, I unpublished it and released it with a new package. I made new certificates, keystore, and alias with eclipse and made back ups of the certificate files. I released it and tried to update the new app some days after. I got the same error on the new app.









  1. I use advanced mode(multiple apks) in the android market, with 2 apks. This is how I signed the app and update it.









  2. Android Tools/Export signed android application. Created a new keystore and a alias and exported it as a apk. The other file, exported I by creating a new keystore and a alias.









When I updated this. I did 1, and instead of creating a new keystore i: Use exsisting keystor and alias. I used the same password. Apk nr2: Use the exisiting keystore to the apk 2 and same alias and same password, but still I get these errors.





This is going to be the 3rd time I need to upload a new application because of these errors. Any Solutions?


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex