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
'SDLManagerDelegate`s are not called if the data session is established successfully but the lifecycle manager does not transition to state ready #1264
Comments
I managed to recreate after pulling the USB cord rapidly multiple times. It looks like the the |
Hi @NicoleYarroch , I see the same issue in my environment. Here is my analysis. SDLFileManager still attempts to resend file even after SDLLifecycleManager becomes I think that to check whether SDLFileManager is
|
Bug Report
The app's
SDLManagerDelegate
s are not called if the data session is established successfully but the lifecycle manager never ends up in stateSDLLifecycleStateReady
.This appears to be some sort of race condition in the lifecycle manager. The lifecycle manager was stuck in state
SDLLifecycleStateSettingUpManagers
so even though Core was sending notifications the app did not get the notifications because the lifecycle manager never finished setting up.Reproduction Steps
Expected Behavior
If the lifecycle manager errors out when setting up, the data session should be destroyed and re-created.
Observed Behavior
The data session stays open, but the app does not get notifications from Core. This means the SDL app UI is empty.
OS & Version Information
Test Case, Sample Code, and / or Example App
Swift example app in the SDL_iOS library
The text was updated successfully, but these errors were encountered: