When using a custom partition scheme, the filesystem upload command does not include the -build.partitions="partitions.csv" parameter. This parameter is crucial for the upload tool to identify and use the data partition configuration (such as FFAT) defined by the user.

Steps to Reproduce:

In a Visual Micro project for ESP32, create a data folder with files.

Create a custom partitions.csv file in the project's root directory. In this file, define a data partition with a fat subtype.

In the Visual Micro settings, select the "Custom" Partition Scheme.

Attempt to upload the files from the data folder using the filesystem upload tool.

Actual Behavior:

For predefined partition schemes, the upload command includes the -build.partitions="[scheme_name]" parameter, which allows the tool to function correctly.

However, when using a custom partition scheme with a partitions.csv file, this parameter is missing from the upload command. This likely causes the tool to fail when attempting to locate the data partition variables, preventing the files from being uploaded.

Additional Information:
The issue is centered on the generation of the upload command for custom schemes. The filesystem upload tool needs the reference to the partitions.csv file to obtain the necessary information for the process. The absence of the -build.partitions parameter appears to be the root cause of the failure.

Attachments:
Logs from two upload attempts are attached for review.

The log from an attempt using the noota_ffat scheme, which works correctly.

The log from an attempt using the Custom scheme, which fails.

Prior to the upload attempt, it has been verified that the project compiles successfully and the program is correctly uploaded to the ESP32. In both configurations (no_ota_ffat and the Custom scheme with a partitions.csv), the ESP32 recognizes and uses the partition scheme, confirming that the partition definition in the .csv file is valid.

It has been noted that the custom partitions.csv file is applied regardless of the selection made in the IDE's Partition Scheme menu (e.g., Custom vs no_ota_ffat). To prevent its use, the file must be renamed or removed from the project's root directory. This behavior is not consistent with the expected logic, which would suggest the file should only be applied when the Custom option is explicitly selected, although this is a minor issue in my case.

The only significant difference between the compilation logs of both scenarios is the absence of the -build.partitions="partitions.csv" parameter in the upload command when the custom scheme is used. The reference to the partitions.csv file is omitted, which appears to be the direct cause of the upload command failure. A simple comparison of the compilation logs confirms this discrepancy.