Description

One Line Summary

Added flags to ensureaddEventListener() only registers each native handler once per event type, eliminating unnecessarycordova.exec calls.

Details

Motivation

I noticed that we may be creating too many native handlers, once per each invocation ofaddEventListener(). This could cause a potential memory leak in the consuming applications.

Scope

AnyaddEventListener function across theInAppMessages,Notifications,User, andPushSubscription namespaces.

Testing

Unit testing

One tested added that ensures thatcordova.exec is only called once, no matter how many event listeners are added.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out allREQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

This change is