Repository navigation
@Receiver never called with OnAttachOnDetach + local #1132
Description
Activity
@westito why do you need the registration in onAttach? wouldn't onCreate or start/resume be enough?
@WonderCsabo any idea? we could check if an
IntentFilter/@Receivershould be registred in onAttach and then setup the filter there. but this could bring issues to the caching if we are not carefull, as we currently only care about the actions and dataSchemes.actually i would suggest to consider removing the onAttach registration options. first it is only available to
Fragmentsand second onCreate is called right after onAttach so there shouldn't be any issues with registration after create instead of attach.@yDelouis is the author of this feature, so i think he should decide. Personally, I would not drop
OnAttachOnDetachsince it is already implemented, only if fixing this is too hard.currently i don't have much time as i'm busy with my own project. i'll try to take a look at this as soon as the update i'm working on is done.
Any news on this one?
yeah, sorry for the delay. totaly forgot this one. :(
Fixed.
LocalBroadcastManager can't register the IntentFilter because the IntentFilter.addAction() called in onCreate AFTER onAttach (where the filter added to the manager). The filter is empty when AA try to register the action in manager. Therefore the action won't be registered.