You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] [P1] Solo over USB fails whenever another USB device is attached: UsbCableTransport uses deviceList.values.first() (5.0.4 to 7.1.0) #287
Solo over USB never connects on an Android device that has any other USB device attached. com.sumup.reader.core.pinplus.transport.UsbCableTransport takes the first entry of UsbManager.getDeviceList() (manager.deviceList.values.first()) and looks for the Solo's class-255 interface on that one device. getDeviceList() is a HashMap keyed by device path, so "first" is arbitrary. When it is not the Solo, no class-255 interface is found, the interface stays null, and the claim fails. SoloUsbIdentifier already picks the Solo by VID 13403 / PID 2; UsbCableTransport does not.
The same code is in com.sumup:merchant-sdk 5.0.4 and com.sumup:reader-core 6.0.0, 7.0.0 and 7.1.0. The problem was described in #214 (March 2024, and again in August 2025 after that issue was closed).
What is blocked by this issue?
Checkout with a Solo connected by USB. On POS hardware with more than one USB device (PC-based tills, tablets with a USB scanner, keypad or printer) the reader cannot be connected at all. These are the setups that need a cable most: many have no Bluetooth, and some sites have no mobile data indoors, so the Solo's own internet connection is not an option either.
Steps to Reproduce
Android device with a second USB device attached (here: a barcode scanner 1A86:5723 and a USB touch panel).
On the Solo, switch ON "Connection via USB" in the Connections menu and connect it by USB.
Log in with the SDK and open the card reader setup (CardReaderSetupActivity).
It opens in CABLE mode, SoloUsbIdentifier.isEligibleToConnect() finds the Solo (VID 13403, PID 2, class-255 interface), and USB permission is granted.
Expected Behavior
UsbCableTransport selects the device with VID 13403 / PID 2 and a class-255 interface, the same way SoloUsbIdentifier does, and the Solo connects.
Actual Behavior
The connection fails and EnableUsbFromReaderFragment shows "To continue, please ensure the USB toggle in the Solo Connections menu is switched on." The toggle is ON. Logcat, on every attempt:
E/SumUp: Failed to claim USB interface
E/SumUp: onCommunicationFailed()
E/SumUp: onTransportError() CardReaderError{Name = TRANSPORT_ERROR mErrorCode=3}
E/SumUp: onDetectionError()
Android Version(s)
Android 11
Impacted Devices
An x86_64 POS computer running an Android 11 based system, with a USB barcode scanner and a USB touch panel attached. Any device whose getDeviceList() holds more than one entry.
Impacted Readers
Solo
Firmware Version(s)
Not recorded. The fault is in the SDK's device selection, before any firmware exchange.
Crash Log
No crash. Logcat is above.
Dependency Versions
SumUp SDK: com.sumup:merchant-sdk 5.0.4 (the same code is in reader-core 6.0.0, 7.0.0, 7.1.0)
Kotlin: 1.9.22
Android Gradle Plugin: 8.2.1
Gradle: 8.2.1
Video / Screenshot
None.
Other Information
Can this be fixed in the next SDK release? Is there a supported workaround in the meantime?
Activity