Valid local names are not always valid dbus object paths
markmcclain opened this issue · 0 comments
markmcclain commented
The problem
The character set for local name (utf-8) and dbus paths (limited ascii ) are different.
Reproduction
On linux, create a server with a name of test-dash-name
Python Exception is raised when started the server:
dbus_next.errors.InvalidObjectPathError: invalid object path: /org/bluez/test-dashed-name/service0001
Expected behavior
Server will start and advertise test-dash-name with dbus backend.
Screenshots
N/A
Desktop (please complete the following information):
- OS: Linux
Additional context
Dbus object path requirements: https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-marshaling-object-path