BTReal: Treat libusb_get_string_descriptor_ascii failure as non-fatal warning #10878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://forums.dolphin-emu.org/Thread-unable-to-pair-remotes-hci-command-timeout, which was apparently introduced by #10729.
My guess as to what's happening here is that
device_descriptor.iSerialNumber
is 0, andlibusb_get_string_descriptor_ascii
doesn't like 0 as it indicates a special case, returningLIBUSB_ERROR_INVALID_PARAM
in that case (which matches the log). However, I haven't tested this change at all.