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
do not unregister EA accessory notification on transport dealloc #1315
do not unregister EA accessory notification on transport dealloc #1315
Conversation
Would a better fix be to change: self.backgroundTaskId = [[UIApplication sharedApplication] beginBackgroundTaskWithName:BackgroundTaskName expirationHandler:^{
SDLLogD(@"Background task expired");
[self sdl_backgroundTaskEnd];
}]; to capture self weakly and use Would that solve the problem of delaying the deallocation of |
Thanks for your comments. I think capturing self weakly will solve the delayed deallocation of SDLIAPTransport, however |
But that's fine, because it is called in - (void)dealloc {
SDLLogV(@"SDLIAPTransport dealloc");
[self disconnect];
[self sdl_backgroundTaskEnd];
self.controlSession = nil;
self.dataSession = nil;
self.delegate = nil;
self.sessionSetupInProgress = NO;
self.accessoryConnectDuringActiveSession = NO;
} |
Oh, understand. I will retest with the suggested solution. Thanks. |
Did the merge of #1317 solve this issue for you? |
Hi @joeljfischer , Thanks for the update. We tested with 6.3.0 and found some problems. When the delayed In addition, when other components other than SDL uses EA Accessory, Therefore, in any way, I think SDL proxy framework should not call
|
@theresalech thanks for the update. |
Fixes #1311
This PR is ready for review.
Risk
This PR makes no API changes.
Testing Plan
We verified this fix with our devboard and OEM HU.
Summary
Calling EAAccessoryManager#unregisterForLocalNotifications makes all SDLIAPTransport instances not be able to receive EA events.
Changelog
Bug Fixes
CLA