Bluetooth Low Energy App on Win 10 - UUID file is not found

Hi,

I´m using the nRF Connect with the Bluetooth Low Energy app on Windows 10. I want to edit the UUID definitions file to add some custom UUIDs, but the application is throwing an error that the file can not be opened.

My guess is that the application can not handle spaces in the file path properly, because the complete path contains a space and the file exists under `C:\Users\Daniel Kampert\AppData\Roaming\nrfconnect`.

Parents
  • Hello,

    Which application are you trying to edit the file with? Could you detail exactly how you are attempting to modify it?
    Could you attempt to navigate to the file location and edit the file in place directly instead?
    I too think this likely is due to the whitespace in the path - I can let the developers know when you have confirmed how you attempted to modify the file when this error showed.

    Best regards,
    Karl

  • Hi Karl,

    one additional note: The issue happens also when I try to open a log file by clicking "Open Log File" under the log console in the device overview of the Bluetooth Low Energy app

  • Ah, that's a little more inconvenient!
    Thank you for this additional information as well - this strengthens the suspicion that it is due to the whitespace in the path.

    The workaround for this would also be to go through the file navigator to open files directly, in this case C:\Users\<USERNAME>l\AppData\Roaming\nrfconnect\pc-nrfconnect-ble\logs

    I have updated the internal ticket with the developers to contain this information as well. Unfortunately I do not have any estimates for when this will be fixed, but once the summer holiday season concludes I wouldnt think it would be long :)

    Thank you again for this bug report - we're always happy to receive this type of feedback!

    Best regards,
    Karl

Reply
  • Ah, that's a little more inconvenient!
    Thank you for this additional information as well - this strengthens the suspicion that it is due to the whitespace in the path.

    The workaround for this would also be to go through the file navigator to open files directly, in this case C:\Users\<USERNAME>l\AppData\Roaming\nrfconnect\pc-nrfconnect-ble\logs

    I have updated the internal ticket with the developers to contain this information as well. Unfortunately I do not have any estimates for when this will be fixed, but once the summer holiday season concludes I wouldnt think it would be long :)

    Thank you again for this bug report - we're always happy to receive this type of feedback!

    Best regards,
    Karl

Children
No Data
Related