Android Question Problem about "Supported options"

[wdegler]

For a long while now, I have had no problems debugging, compiling and running my apps. Now, suddenly, every attempt to compile ANYthing is resulting in this error message:

"Signing package file (debug key). Error
Unsupported option: --v3-signing-enabled. See --help for supported options."

I have tried redownloading and reinstalling all of B4A. but the problem persists. I have B4A version 10.7.
The suggestion "See--help for supported options" is unclear to me ...See Where?

Can someone tell me how to get back up and running again?

Help!

 

[MikeSW17]

A forum search often helps

10.7 BETA unable to compile due to signing error

This post is related to the thread about 10.7 BETA. I opened a test project that I've been working with all day using 10.6, and tried to run a debug (*) build: B4A Version: 10.70 BETA #1 Parsing code. (0.00s) Java Version: 11 Building folders structure. (0.00s) Compiling code...

www.b4x.com

 

[Jeffrey Cameron]

From @Erel's post on the 10.7 version:

B4A 10.7 depends on a recent version of the build tools. If you get an error similar to:

Signing package file (debug key). Error
Unsupported option: --v3-signing-enabled. See --help for supported options.
Then you are using an old version of Android SDK and need to upgrade. It is very simple to upgrade the SDK: https://www.b4x.com/b4a.html

 

[wdegler]

A forum search often helps

10.7 BETA unable to compile due to signing error

This post is related to the thread about 10.7 BETA. I opened a test project that I've been working with all day using 10.6, and tried to run a debug (*) build: B4A Version: 10.70 BETA #1 Parsing code. (0.00s) Java Version: 11 Building folders structure. (0.00s) Compiling code...

www.b4x.com

I did a search already. When I wrote I had reinstalled ALL of B4A, I meant that to include "Android SDK Command Line Tools" and "Required Resources" as well.
The problem persists. I am going to try these installations yet again. Thanks for responding.

 

[wdegler]

I have now redownloaded and installed B4A 10.7.
I have also redownloaded and extracted SDK Command Line Tools, and Required Resources to C:\Android.
I have reconfigured paths to javac.exe and android.jar.
I am attaching a file showing a directory of Android files with dates shown.
The problem attempting to compile persists, yet was not a problem a few days ago.
I have used the link suggested above to get all the required files. as indicated in the attachment.
Does anyone have what I can try next?

 

[MikeSW17]

You don't mention downloading and installing bundletool.jar ?
See: https://www.b4x.com/android/forum/threads/b4a-v10-7-is-available-for-download.128734/#content

 

[wdegler]

You don't mention downloading and installing bundletool.jar ?
See: https://www.b4x.com/android/forum/threads/b4a-v10-7-is-available-for-download.128734/#content

I did download bundletool.jar and I put in in C:\Android. However, Erel wrote that it is not related to this problem.

You don't mention downloading and installing bundletool.jar ?
See: https://www.b4x.com/android/forum/threads/b4a-v10-7-is-available-for-download.128734/#content

Correction: I did download Bundletools and put it in C:\Android\tools\bin.
Problem is still present.

 

[MikeSW17]

Ok, I can't remember how I got to this point - probably playing around with SDK Manager - but I ended-up with an additional folder : "\Android\cmdline-tools\3.0\bin.
For some reason, I put a copy of bundletool.jar in there too.
I know its a wild-guess, but if you have anything similar it might help.

Other than that, did you use 7-Zip to extract the Tools & Resources Zips? (Windows Extract DOES corrupt the sub-folder structure).

EDIT*
Also try cleaning project before compiling.

 

[Erel]

It is not related to bundletool. Delete your current SDK. Download the two components and configure the IDE paths. It will work.