From: mariasophia@comprehension.com   
      
   Martin Schöön wrote:   
   > I tried installing OpenContacts yesterday using f-droid and was met by   
   > an error message. I did not have the presence of mind to screenshot   
   > it but it was something about issues with digital signing of the   
   > application.   
      
   Hi Martin,   
      
   First and foremost, thank you for having the common decency and respect for   
   your fellow friends & neighbors in your contacts to even test it out.   
      
   Most likely cause in your case you may have had an older OpenContacts build   
   perhaps, or a fork perhaps, or maybe even a version installed from   
   somewhere other than F-Droid perhaps as in *those* cases, F-Droid will   
   refused to overwrite it because the signing keys won't match.   
      
   Even so, I'm well aware most people have no concept of respectful decency   
   when it comes to asking permission to upload willy nilly other people's   
   private data, so I already give you huge kudos for trying to be respectful   
   to your fellow man.   
      
   Very very very very very few people are respectful of others like that.   
   I am. But most people don't respect the privacy rights of other people.   
      
   You do.   
   And that's why I commend you for trying.   
      
   On the thread about numbers of contacts, we've already found that there are   
   many (hidden) apps (mostly system) which can read our contacts, and anyone   
   who says they've protected them is being overly optimistic on their skills.   
      
   Speaking of skills, I really never have figured out signature protection   
   myself, but you seem to be running into one of the most common F-Droid   
   installation problems of a signature mismatch. Based on what's known about   
   F-Droid's signing model and the kinds of errors users report, here's the   
   clearest explanation of what likely happened.   
      
   F-Droid rebuilds most apps from source and signs them with F-Droid's own   
   signing key, not the developer's. If the user already has a version of the   
   app installed from another source (GitHub, developer website, another repo)   
   or a leftover package with a different signature... then Android will   
   refuse to install the F-Droid version because the signatures won't match.   
      
   At least this seems to be the same class of problem described in other   
   F-Droid signature-mismatch reports, where the client blocks installation or   
   update when the signature differs from what's already on the device   
      
      
   The message typically looks like:   
    "Signature verification failed"   
    "App not signed with the same key"   
    "Incorrect signature"   
   Where these errors appear when:   
    a. The app was previously installed from a different source   
    b. The package name is the same, but the signing key is different   
    c. F-Droid refuses to overwrite it for security reasons   
      
   This is similar to other "incorrect signature" issues users encounter when   
   F-Droid detects a mismatch between expected and actual signatures in a repo   
   or app package    
      
   My suggestions?   
   a. Uninstall Dopen Contacts completely & re-install it.   
   b. Download the APK from F-Droid's web site & tap to install   
   c. Use App Manager (Muntashirakon) to "install only"   
      
   Muntashirakon App Manager allows installing mismatched-signature APKs   
   without uninstalling first, similar to what users describe when bypassing   
   signature checks for other apps.   
      
   Note almost everyone on Android who knows anything about Android already   
   has Muntashirakon App Manager so if you don't have it, get it. :   
      
      (apk)   
       (doc)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)