BasicOTA with ESP32 and Arduino 2.0.0 rc3 = espota.py error

[tombo9999]

Board

Esp32-Cam

Device Description

In Arduino Boards Manager selected ESP32 Wrover Module

Hardware Configuration

Minimal SPIFFS

Version

other

IDE Name

Arduino 2.0.0 rc3

Operating System

macOS 12.1 and Windows 10

Flash frequency

80 Mhz

PSRAM enabled

yes

Upload speed

115200

Description

I like BasicOTA because it's simple ;)
Tried on Windows 10 + Arduino IDE 1.8.19 and MacOS Monterey 12.1 + Arduino IDE 1.8.18 and it works without any problem.
Wanted to try Arduino 2.0.0 rc3 nightly build, I can compile and upload using the serial port.
If I use the board IP address, can't upload (no problems compiling).
I'm just a hobbyist, not a programmer, surely I'm making some silly mistake.

MacOS
Sketch uses 690349 bytes (52%) of program storage space. Maximum is 1310720 bytes.
Global variables use 41348 bytes (12%) of dynamic memory, leaving 286332 bytes for local variables. Maximum is 327680 bytes.

Compilation complete.
Usage: espota.py [options]

espota.py: error: option -p: invalid integer value: '{upload.port.properties.port}'
Upload error: Failed uploading: uploading error: exit status 2

Windows 10 (same error)
...
espota.exe: error: etc

Sketch

Just BasicOTA

Debug Message

espota.py: error: option -p: invalid integer value: '{upload.port.properties.port}'
Upload error: Failed uploading: uploading error: exit status 2

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[JAndrassy]

arduino/arduino-ide#740

[VojtechBartoska]

Hello, is this still valid?

[per1234]

Hi @VojtechBartoska. Unfortunately yes it still is.

@me-no-dev did an investigation and reported the findings here:
arduino/arduino-ide#740 (comment)

[VojtechBartoska]

Adding to the roadmap and we will investigate this more.

[lsdlsd88]

still happening. ide 2.3.2 on win 10

[rftafas]

This is referring version 2.0.x and seems to have a solution appointed above. Please, re-test this with the latest release, update the bug report to current requirements and re-open if the problem persists.