Extracting archives does not work in the expected way and that cannot be changed

[Danny3]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.6.1

Affected Android/Custom ROM version

Android 16 / LineageOS 23.2

Affected device model

Samsung Galaxy S10+

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Create a folder on your computer. I created a folder named A on the Desktop of a Debian OS.
2. Put many folders and files in it. I created this folder with many things inside so I can copy paste many things in one go to my Android phone.
3. Archive the folder as Zip with compression set to store (for no compression).
4. Copy the A.zip file (or whatever you called it) to the root of the internal memory.
5. Extract it.

Expected behavior

I expecting it will give me the exact folder structure that I had inside.
Meaning:
A single folder called: A
With everything that was inside when I archive it to still be inside, in the same exact hierarchy.
Without anything extra being added.

Actual behavior

The file manager automatically creates a folder named A and then it puts inside of it what I have in the archive.
So the hierarchy is now like this:
A
-A
--The contents of A meanind the folders and files that were inside of it.

Screenshots/Screen recordings

No response

Additional information

I took this route of archiving the folder with everything inside it because the folder is very big, more than 20 GiB and copying-pasting normally takes very long and it's very error-prone, with multiple failures.
Copying a single file seems to be faster and less error-prone.
I've put the archive at the root of the internal storage because there I would've normally copied the folder, if it worked without problems.
So extracting the archive there should've gave me a single A folder at the root of the internal memory and not 2 A folders nested.
The second worst thing is that I cannot even move out the inner A folder as the name will conflict with the outer A folder.
The third worst thing is that the outer A folder cannot me renamed to anything else so I can move the inner A out as I don't see anything in the menu after selecting the out A folder to rename it.
I've tried to rename the outer A folder from the computer and while it looked like it worked, it gave an error after some time about some movement failure.

I see now that this file manager show the outer as renamed, but after that movement error I'm not sure anymore if I still have the same folders and files in it without any problems, so I prefer to delete it and start over.
But unfortunately extracting the archive will give me again the same double folder in a nested way.
I think the same thing happened to me in the past with a .tar archive, so I assume this behavior is the same for all archive files extraction.
Can you please fix it to stop doing these automatic unexpected things?
And in the meantime, give a way to manually stop them, if the proper fix is hard to do and takes a long time?

Thank you!