Skip to content
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

A new transport session is not created if a background task is not ongoing #1316

Closed
NicoleYarroch opened this issue Jun 24, 2019 · 2 comments
Assignees
Labels
bug A defect in the library
Projects
Milestone

Comments

@NicoleYarroch
Copy link
Contributor

Bug Report

If app on device is closed when trying to create a connection with the SDL enabled accessory:

  1. The connection attempt can fail if the background task is not started.
  2. The reconnection attempt can fail due to the background task being destroyed in the dealloc method of the SDLIAPTransport object.
Reproduction Steps
  1. Configure 13 apps with v.6.3 of the library
  2. Connect the phone to SYNC 3.4 TDK with BT
  3. Go to apps tab and wait for all 13 apps to show up
Expected Behavior

All 13 apps show up on the SDL HMI.

Observed Behavior

Between 1 and 3 apps will sometimes fail to show up. From the logs it looks like the background task expires, so even though a reconnection attempt should be made by the lifecycle manager, nothing happens.

OS & Version Information
  • iOS Version: 12.1.4
  • SDL iOS Version: 6.3
  • Testing Against: SYNC 3.4 TDK (Build 19126_DEVTEST) + iPhone XS Max (iOS 12.1.4)
@NicoleYarroch NicoleYarroch added the bug A defect in the library label Jun 24, 2019
@NicoleYarroch NicoleYarroch added this to the 6.3.0 milestone Jun 24, 2019
@NicoleYarroch NicoleYarroch self-assigned this Jun 24, 2019
@NicoleYarroch NicoleYarroch added this to To do in v6.3 via automation Jun 24, 2019
@NicoleYarroch
Copy link
Contributor Author

All the logs for the apps the fail to connect to the TDK show that the a data session is established but the start session times out because no response is received from Core. The transport is destroyed and a new transport should be created, however, since the background task was destroyed in the dealloc method, the new transport is not created.

@t-yoshii
Copy link

Is this same as #1311 ?

v6.3 automation moved this from To do to Done Jun 26, 2019
@joeljfischer joeljfischer mentioned this issue Jun 26, 2019
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect in the library
Projects
No open projects
v6.3
  
Done
Development

No branches or pull requests

3 participants