Removed unnecessary JARs

v2.2.3

Removed unnecessary JARs

v2.2.2: Prepare for clean AppStore publish

The module was not properly imported in the test and demo projects

v2.2.1: Remove superfluous logging

The widget code accidentally instructed the browser to log on all levels.

v2.2.0: GCM using native REST consume

We have replaced the Java/XMPP-based implementation of the GCM connector with a native Mendix implementation that uses the GCM HTTP/REST API. This should resolve the issue w.r.t. failing push notifications on Android due to a CONNECTION_DRAINING error (issue #45). Other responses are now also properly handled (such as 'device unregistered' errors, or responses with a new canonical registration id).

v2.1.0: Offline support

The Push Notifications module now supports 'offline mobile' mode.
https://world.mendix.com/display/refguide6/Offline

Fixes:

• Entity access to the Device entity was too liberal. Access is now removed entirely, and device registration occurs through a proxy DeviceRegistration entity.

Improvements:

• Removed most warnings and errors that showed up when you imported the Push Notifications module into a project.
• Demo project has been updated to reflect the changes in this release.

v2.0: Anonymous users and multiple devices

• We added a demo project to the repo, in addition to the test project. This project is also published in the app store.
• Users can now be associated with multiple devices. Messages can be sent to all devices of a user at once.
• It is now possible to send push notifications to anonymous users.
• The administration pages look significantly better.

1.0.0

Re-applied fix for GCM response parsing error which was accidentally overwritten.

1.0.0 release candidate

Merge pull request #37 from mendix/development-1.0

#720387: Release MxPushNotifications module v1.0.0

0.9.0

#720894: Release 0.9.0.

Release scope:

• Improve developer visible interface (reorganize module)
• Expose Java actions API
• Update documentation

0.8.0

Improved documentation.