[BUG] [P1]

[superafroman]

Summary

Air 205 reader won't connect after device restart

What is blocked by this issue?

Using the card reader

Steps to Reproduce

Connect Air 205 card reader. Reboot Android device. Try and connect card reader again -> fails.

Expected Behavior

Successful connection to the card reader

Actual Behavior

Unable to connect to the card reader

Android Version(s)

Tested on Android 10 and 13

Impacted Devices

No

Impacted Readers

Air 205. Switching to a 215 reader fixes the problem.

Firmware Version(s)

Firmware version: 2.0.0.7
Bluetooth software version: 7.30

Crash Log

N/A

Dependency Versions

• SumUp SDK: 7.0.0
• Kotlin: 1.9.25
• Android Gradle Plugin: 8.7.0
• Gradle: 8.13

Other Information

Reverting to SumUp SDK 5.0.3 resolves the issue.

[HeyPouya]

Hi @superafroman,

Thanks for reporting this issue.

We performed several tests using SDK v7.0.0 with an Air 205 reader, but unfortunately, we were unable to reproduce the problem.

Could you please help us with the following information?

• Does this issue occur with only one Air 205 reader, or have you observed it with multiple readers?
• Could you try connecting to the reader using the SumUp App and let us know whether the connection succeeds there?
• Could you also test with SDK v6.0.0 and confirm whether the same issue occurs in that version?

Any additional details you can provide would be greatly appreciated.

Thank you!

[superafroman]

Hi @HeyPouya,

I've been able to reproduce this using the latest SumUp Business app from the Play store. Same process:

1. Open the SumUp app, login and connect the 205 card reader -> connects fine
2. Restart the Android device
3. Open the SumUp app, auto logs in, attempt a payment -> can't connect to the card reader
4. Also tried connecting the reader again via Tools -> Card readers but no luck. This is the same behaviour as when using the SDK

I've attached a few screenshots showing the app being unable to connect and also the card reader details.

On the issue appearing in SDK 6.0.0, yes we've been able to test this now and the issue is also happening in SDK 6.0.0.

[superafroman]

@HeyPouya, here are a few affected reader serial numbers, including mine from above:

• 106011930056
• 106011646651
• 106011923969
• 106011930066
• 106012055794

[HeyPouya]

Hi @superafroman,

Thanks for providing the detailed reproduction steps.

I was able to reproduce the issue on my side as well. We'll investigate it further and update this GitHub issue as soon as we have more information.