Currently the plugin pulls the `PACKAGE_NAME`, early on in the build process. After working with Android product flavors where I am building different APKs with different applicationIds (com.test.app.alpha, com.test.app.beta, com.test.app) the permission still sticks with the core package name. These permission requests then conflict with each other when having multiple APKs on the same device, and can even stop the app from being downloaded from the Play Store if the user has an another app on the device with the same permissions.

By using `{applicationId}` it will grab the current App's application ID later on so the current ID is used instead.

Make sure the  object exists in the notification.

Issue #274: Callbacks for actions buttons

Pimp my readme

Mentioning that the unregister method also cleans up event handlers on the docs.

Fixed a typo in README.md

Now calling .trim() to each array String element when parsing them to Ints/Longs

fix Issue 354

When a vibration pattern is sent as e.g. [0, 150, 250, 100], or a ledColor as e.g. [0, 255, 127, 64], the space after each comma will now be trimmed, which would otherwise cause a NumberFormatException when trying to parseInt/parseLong the string " 0255".

add sound default statement

Added event handler removal

Update README.md

Added detail about requiring no extension as the file name.