You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the delayed sdl_connect by old SDLIAPTransport instance is called after the reconnection by another SDLIAPTransport is done, deallc of old SDLIAPTransport occurs and causes unregistration of EAAccessoryManager. This prevents the succeeding EA events detection. Please check the following logs.
In addition, when other components other than SDL uses EA Accessory, EAAccessoryManager#unregisterForLocalNotifications also affects the EA event listening of such components.
One of our SDL apps uses EA accessory other than SDL. The application sometimes stops SDLManager (this lead to call EAAccessoryManager#unregisterForLocalNotifications) in some situation, but it still needs to use EA accessory for the other purpose (with other protocol strings.)
Therefore, in any way, I think SDL proxy framework should not call EAAccessoryManager#unregisterForLocalNotifications.
Bug Report
When the delayed
sdl_connect
by old SDLIAPTransport instance is called after the reconnection by another SDLIAPTransport is done, deallc of old SDLIAPTransport occurs and causes unregistration of EAAccessoryManager. This prevents the succeeding EA events detection. Please check the following logs.In addition, when other components other than SDL uses EA Accessory, EAAccessoryManager#unregisterForLocalNotifications also affects the EA event listening of such components.
One of our SDL apps uses EA accessory other than SDL. The application sometimes stops SDLManager (this lead to call EAAccessoryManager#unregisterForLocalNotifications) in some situation, but it still needs to use EA accessory for the other purpose (with other protocol strings.)
Therefore, in any way, I think SDL proxy framework should not call EAAccessoryManager#unregisterForLocalNotifications.
This is copied from the comment below.
#1315 (comment)
Reproduction Steps
Expected Behavior
Connection does not fail
Observed Behavior
Connection sometimes fails
OS & Version Information
Test Case, Sample Code, and / or Example App
I will create PR
The text was updated successfully, but these errors were encountered: