R RichardN Well-Known Member Licensed User Longtime User Oct 26, 2024 #1 As I am working away from home for a while I have made a clean install of the latest version of B4A to my laptop together with the 3 resource packages detailed on the 'Products' page. I copied my project files, keystore files and libraries from my PC to appropriate locations on the laptop. Using a portable SSD all the files appear to have copied without error. On first run of a previously sound project I get a Keystore error on installation. The password is correctly recorded and entered. I have overwritten the keystore files as fresh copies from the SSD. Whilst it is remotely possible the original Keystore file copied to the SSD was corrupt it seems unlikely. Perhaps there is some element of the resources or dependencies that I have missed?
As I am working away from home for a while I have made a clean install of the latest version of B4A to my laptop together with the 3 resource packages detailed on the 'Products' page. I copied my project files, keystore files and libraries from my PC to appropriate locations on the laptop. Using a portable SSD all the files appear to have copied without error. On first run of a previously sound project I get a Keystore error on installation. The password is correctly recorded and entered. I have overwritten the keystore files as fresh copies from the SSD. Whilst it is remotely possible the original Keystore file copied to the SSD was corrupt it seems unlikely. Perhaps there is some element of the resources or dependencies that I have missed?
teddybear Well-Known Member Licensed User Oct 26, 2024 #2 Which JDK version are you using, 14? Upvote 0
R RichardN Well-Known Member Licensed User Longtime User Oct 26, 2024 #3 Yes 14. This is a little bizarre as my home PC is also right up to date with B4A and JDK versions detailled by @Erel but works fine....? No such algorithm exception SHA 256? Last edited: Oct 26, 2024 Upvote 0
Yes 14. This is a little bizarre as my home PC is also right up to date with B4A and JDK versions detailled by @Erel but works fine....? No such algorithm exception SHA 256?
teddybear Well-Known Member Licensed User Oct 26, 2024 #4 Try creating a new key to check if the problem is from the old key. Upvote 0
R RichardN Well-Known Member Licensed User Longtime User Oct 26, 2024 #5 Creating a new Keystore for a clean install seems to work OK. I can only conclude that the Keystore copy I have used is corrupted and sadly I don't currently have access to the original. I am also left with several other problems but I don't think they are Keystore related Upvote 0
Creating a new Keystore for a clean install seems to work OK. I can only conclude that the Keystore copy I have used is corrupted and sadly I don't currently have access to the original. I am also left with several other problems but I don't think they are Keystore related
