New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IAPTransport class stops observing accessory notifications incorrectly #1239
Comments
Hi, Thank you. |
@t-yoshii Please check the attached PR to see if the fix works for you |
Thanks for comments. We start testing the fix #1248. We still see some errors. I will report it after analysis. |
We tested repeatedly connect/disconnect EA accessory in a very short period of time. We see "Error creating the session object" error. Event timetable
// iOS console log
|
@t-yoshii Thanks for the logs. I will attempt a fix and let you know when I have pushed the updates. |
@NicoleYarroch |
@NicoleYarroch However, we found 2 issues and create #1310 and #1311 . Could you please check these? |
Bug Report
When an accessory connected notification is received in the
SDLIAPTransport
class, the actual connection connection attempt occurs after a random delay (1.5 to 9.5 seconds). If the user pulls the cord during the delay, the class unregisters for accessory notifications however since no connection has been established, the lifecycle manager does not create a newSDLIAPTransport
object.Reproduction Steps
retryDelay
Expected Behavior
The
SDLIAPTransport
class gets the accessory connected notification and attempts a connection.Observed Behavior
The
SDLIAPTransport
class is unregistered for accessory connected/disconnected notifications.OS & Version Information
Test Case, Sample Code, and / or Example App
The SDL_iOS Swift example app.
The text was updated successfully, but these errors were encountered: