Closed mattdsteele closed 2 years ago
Hi @mattdsteele , that is just how the plugin was implemented, there is no reason it could not be modified to support multiple receivers as you describe but I have no plans to do so myself.
Any further technicolor as to why receivers are unregistered would be helpful as we start developing this out
It was just less work :)
Thanks for the context; I'll work on submitting a pull request for this.
I'm looking for more details regarding this line in the documentation, under Android Quirks:
I'm not sure I understand why this restriction is in place. From what I can tell, there's no limitation at the OS level for registering multiple
BroadcastReceiver
elements: https://developer.android.com/guide/components/broadcasts#receiving-broadcastsIn particular, this limitation is causing issues in one of our applications, where we have different subsystems of the app, developed by different teams, that need to register separate receivers; and are currently overriding each other.
With the current setup, we'll have to create a new abstraction to ensure we only call
intentShim.registerBroadcastReceiver
once, but I'd like to avoid this if possible, as it adds a layer of indirection.Any further technicolor as to why receivers are unregistered would be helpful as we start developing this out. Thank you!