mvp

@eswierk, unfortunately this is not very good approach and arguably is macOS 26 bug. Scenario: I have an executable (e.g. uhubctl) that links to libusb and built using MacOSX15.5 sdk...

@eswierk, unless I am mistaken you are current Apple employee? So you are most equipped to file this or solve this issue on macOS side?

Filed to Apple feedback https://feedbackassistant.apple.com/feedback/18170043. Full text is below: **macOS 26 breaks backwards USB compatibility with libusb** **Please provide a descriptive title for your feedback:** macOS 26 breaks backwards USB...

Interesting. So they did change it from `"usb-port-number"` in first rc to `"port-number"` in last one. This suggests that reverting back to `"port"` is highly unlikely 😢

@seanm, we need to fix libusb then - dynamically check macOS version and use correct property name for macOS 26+. I will try to cut pr for this next couple...

Created pr to fix this https://github.com/libusb/libusb/pull/1700. Unfortunately, I do not have access to macOS 26 yet. I need someone who has macOS 26 installed to test this patch please? This...

Fix pr https://github.com/libusb/libusb/pull/1700 is ready to merge now. This fix has been confirmed to work with uhubctl https://github.com/mvp/uhubctl/issues/623#issuecomment-3300325458 Also, I am getting users requests to fix uhubctl on macOS 26...

When #1700 is merged, it would be possible to fix this on macOS 26 using: ``` brew uninstall libusb --ignore-dependencies brew install libusb --head ``` @seanm, @mcuee, @dickens, @hjelmn: can...

Waiting few months is less than ideal. But at least we can have ``` brew install libusb --head ``` until then. Because without this, macOS 26 users are in huge...

Did you check that vbus goes down when ports are powered off?