Android Question #SignKeyFile: using relative path instead of absolute one

toby

Well-Known Member
Licensed User
Longtime User
Can I use relative path for #SignKeyFile setting? If yes, could someone show me how, please?

B4X:
'I first put the file in the project folder (same as the project file) and use
#SignKeyFile: mykeyfile.keystore

'Then I put the file in its parent folder and use
#SignKeyFile: ..\mykeyfile.keystore

'Neither worked and both returned  file not found error
 
Solution
It is possible to use relative references.

The reference is from the compilation directory which I believe is the Objects directory.
1636795614612.png

If you put the sub-directory within the B4a directory you can access it like this.

1636795718476.png


This will work.

You do the same for the adaptive icon.
1636795802198.png

Andrew (Digitwell)

Well-Known Member
Licensed User
Longtime User
It is possible to use relative references.

The reference is from the compilation directory which I believe is the Objects directory.
1636795614612.png

If you put the sub-directory within the B4a directory you can access it like this.

1636795718476.png


This will work.

You do the same for the adaptive icon.
1636795802198.png
 
Upvote 2
Solution

toby

Well-Known Member
Licensed User
Longtime User
I mistakenly thought that B4A's working folder is where the project file, *.b4a, is located. Now I know that it's the Objects subfolder.
 
Upvote 1

Situ LLC

Active Member
Licensed User
Try Like That :)

SignKeyAlias=gundam_Situ
SignKeyFile=C:\signkey\app.keystore
SignKeyPassword=situ
 
Upvote 0
Top