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
[x] Any Public API changes are explained in the PR details and conform to existing APIs
Testing
[x] I have included test coverage for these changes, or explained why they are not needed
[x] All automated tests pass, or I explained why that is not possible
[x] I have personally tested this on my device, or explained why that is not possible
Final pass
[x] 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.
[x] 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.
Description
One Line Summary
Fix crash in Android when receiving a notification with action buttons.
Details
We were converting the ActionButtons to a map so we could not bridge to dart from Android native Fixes https://github.com/OneSignal/OneSignal-Android-SDK/issues/1815
Motivation
fix crash
Scope
android push notifications
Testing
Manual testing
tested with Android push and iOS push
Affected code checklist
Checklist
Overview
Testing
Final pass
This change is