Rc/2.4.0

[tompsota]

What's new

Describe the PR shortly

PR checklist

In-app checks:

• callbacks are received
• dev/prod switch works
• README.md is updated (if applicable)
• example app is working

Pre-release checks:

• CHANGELOG.md is updated
• package.json version is increased
• release label is applied on PR

To be checked by maintainers:

• freeRASP logs are received
• sdkVersion property in logs is correct
• sdkPlatform property in logs is correct

Resolved issues

list of issues resolved by this PR

[martinzigrai]

[martinzigrai]

Same as in Flutter and RN.

To make it completely thread-safe, we should ensure all external calls happen
after releasing the lock. The abstract flow should look like this:

For setting the listener (flush):

1. Lock -> Assign the listener -> Copy cache to a temp list -> Clear cache -> Unlock.
2. Iterate over the temp list and invoke the listener.

For dispatching a new event:

1. Lock -> Check if the listener exists.
2. If YES: Grab the listener reference -> Unlock -> Invoke the listener.
3. If NO: Add the event to cache -> Unlock.

[martinzigrai]

same as in the ExecutionStateDispatcher.kt‎

[martinzigrai]

Since Automation is Android-only, remove this.Automation from the iOS array.

[martinzigrai]

If the plugin is destroyed but the application process remains alive, the singleton will continue to hold the old Context, causing a memory leak. Therefore, the handleOnDestroy method should be overridden to release the dispatcher listeners.

[tompsota]

onDestroy() is not guaranteed to be called in the Android activity lifecycle, so this is not the best place for such actions. However, yes I will add this