MrKim Well-Known Member Licensed User Longtime User Aug 22, 2017 #1 I upgraded from 7.(01? - the last version) to 7.30 and I am getting: App Not Installed 'The package conflicts with an existing package by the same name'. There is no mention of a conflicting Key. In this particular case I don't mind uninstalling and reinstalling, I am just wondering what are the rules regarding this? In the future when should I expect this to happen so I can plan for it? No I don't save old versions and don't plan to. I am not that organized.
I upgraded from 7.(01? - the last version) to 7.30 and I am getting: App Not Installed 'The package conflicts with an existing package by the same name'. There is no mention of a conflicting Key. In this particular case I don't mind uninstalling and reinstalling, I am just wondering what are the rules regarding this? In the future when should I expect this to happen so I can plan for it? No I don't save old versions and don't plan to. I am not that organized.
Erel B4X founder Staff member Licensed User Longtime User Aug 22, 2017 #2 Make sure that you are using the correct signing key. It does sound like a conflicting key issue. Upvote 0
nibbo Active Member Licensed User Longtime User Aug 22, 2017 #3 As Erel says, it is a signing issue. Are you using a private signing key when you compile and release your app? If not then it is deploying with the debug key which may change between B4A versions. You can uninstall and reinstall to get around it but using your own key will future proof it. To add your own key go into 'Tools' > 'Private Sign Key' and complete the form. (make sure you put a full file path in the save as bit!). Upvote 0
As Erel says, it is a signing issue. Are you using a private signing key when you compile and release your app? If not then it is deploying with the debug key which may change between B4A versions. You can uninstall and reinstall to get around it but using your own key will future proof it. To add your own key go into 'Tools' > 'Private Sign Key' and complete the form. (make sure you put a full file path in the save as bit!).
