BLE OTA mobile app does not display ESP device (AEGHB-175)

[MarcFinetRtone]

INSTRUCTIONS

Before submitting a new issue, please follow the checklist and try to find the answer.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

Environment

• Development Kit: Yd-esp32-c3

• Kit version (for WroverKit/PicoKit/DevKitC):

• Module or chip used: ESP32-C3-MINI-1

• IDF version (run git describe --tags to find it): v5.0.1 nor v5.1-dev-4558-ga8b97b4e02

• Build System: CMake

• Compiler version (run xtensa-esp32-elf-gcc --version to find it): 11.2.0

• Operating System: Linux

• Power Supply: USB

Problem Description

I'm trying the ble_ota example with the apk provided here

Expected Behavior

See my device on the mobile app.

Actual Behavior

Nothing on the mobile app, even after refresh (I have given the location rights).
The nRF connect app correctly 'sees' the ESP&C119 device.

The mobile app shows other BLE devices, but not my ESP.

Steps to reproduce

1. compile
2. flash
3. start the mobile app

Code to reproduce this issue

Unfortunately the code of the mobile app is not provided (https://github.com/EspressifApps/esp-ble-ota-android/tree/rc), only an apk.

[XionHsieh]

This issue has been resolved, please use the master branch to test.

[Letian-stu]

This issue has been resolved, please use the master branch to test.
@XionHsieh Hello, I'm currently using the latest branch, but this problem still exists. May I ask which branch or commit you are using?

[sako85]

Same here, and even if I found the device, the connection is lost so that I cannot update the firmware to that device... "Device not connected"

oh, I used wrong app... nvm.