Open joeljfischer opened 7 years ago
@joeljfischer was this added to the new milestones? Looks like I'm seeing the old handlers being saved in the customButtonHandlerMap
in SDLResponseDispatcher
@SatbirTanda This issue has not yet been fixed and is not currently scheduled for a release. I'm unsure of any good way to fix it, or even if there is a good way, and the downside is not so bad that it needs immediate attention. At some point we will look into it again, but it's not a high priority at the moment.
@joeljfischer -san, We were able to reproduce this issue with v6.5.0. This is a high priority issue for Toyota. Is it possible to include this in the next release plan?
Hi @E-SAITO-TMC, several attempts were made to solve this issue, but all have failed. I believe that this issue is unfixable. I have applied the wontfix label to it. Please let me know if you think differently, but I don't believe that it's possible to fix this issue with the current library architecture.
@joeljfischer -san, Thank you for reply. I understand that this issue cannot be fixed. Please let me know if this status changes.
One way this could be improved is to alter the soft button manager to observe the onButtonPress / onButtonEvent
notifications itself and handle storing the handlers itself instead of relying on the SDLResponseDispatcher
.
Bug Report
We store handlers for button events, including
SoftButton
s. When these handlers are no longer relevant, they should be removed from memory in the iOS library. Currently, however, it appears there is no mechanism in place to do so.Old
SoftButton
s are removed from use when a newShow
message is sent withSoftButton
s. When a newShow
message that containsSoftButton
s is received, we should remove all oldSoftButton
handlers.Reproduction Steps
SoftButton
sSoftButton
sExpected Behavior
The old
SoftButton
handlers are removed from memory.Observed Behavior
The old
SoftButton
handlers remain in memory.OS & Version Information
TODOs