Marketplace release v7.2.0

• We included a migration file for the Java dependencies for Studio Pro 10 compatibility.

Marketplace release v7.1.3

• We updated the “netty” dependencies for the module to version “4.1.94.Final“. Below is a list of updated userlib files.
  (Note: If you are already using this module in your project, after upgrading to this version make sure to remove old versions of the updated libraries and their corresponding '.PushNotifications.RequiredLib' from your userlib folder)

Updated:

• netty-buffer-4.1.94.Final
• netty-codec-4.1.94.Final
• netty-codec-dns-4.1.94.Final
• netty-codec-http2-4.1.94.Final
• netty-codec-http-4.1.94.Final
• netty-codec-socks-4.1.94.Final
• netty-common-4.1.94.Final
• netty-handler-4.1.94.Final
• netty-handler-proxy-4.1.94.Final
• netty-resolver-4.1.94.Final
• netty-resolver-dns-4.1.94.Final
• netty-transport-4.1.94.Final
• netty-transport-native-unix-common-4.1.94.Final

Marketplace release v7.1.2

• We updated XPath in 'UpdateDeviceRegistration' microflow
• We updated the dependencies for the module
  Note: If you are already using this module in your project, after upgrading to this version make sure to remove old versions of the updated libraries and their corresponding '.PushNotifications.RequiredLib' from your userlib folder, See the list below for the changes in this release.

Updated:

• 'checker-qual' to version 3.33.0
• 'j2objc-annotations' to version 2.8
• 'error_prone_annotations' to version 2.18.0

Removed:

• 'checker-compat-qual-2.5.5'

Marketplace release v7.1.1

• We updated the 'guava' library to '32.0.1-android' (Note: If you are already using this module in your project, please make sure to remove the old version '31.0.1-android' from your userlib folder after upgrading to this version)
• We updated the log messages for succeeded and failed notifications

Marketplace release v6.3.1

• We updated the 'guava' library to '32.0.1-android' (Note: If you are already using this module in your project, please make sure to remove the old version '31.0.1-android' from your userlib folder after upgrading to this version)
• We updated the log messages for succeeded and failed notifications

Marketplace release v7.1.0

• We Updated all netty libraries from version 4.1.78 to 4.1.86 (Please make sure to review the userlib folder in your project after updating. Delete all netty libraries that are marked with '.PushNotifications.RequiredLib' having a version below 4.1.86.Final)
• We Added an index on DeviceID attribute in Device entity
• We Updated Pop-up Menu widget compatibility to v3.3.0
• We Updated Data Widgets compatibility to v2.5.9

Marketplace release v6.3.0

• We Updated all netty libraries from version 4.1.78 to 4.1.86 (Please make sure to review the userlib folder in your project after updating. Delete all netty libraries that are marked with '.PushNotifications.RequiredLib' having a version below 4.1.86.Final)
• We Added an index on DeviceID attribute in Device entity
• We Updated Pop-up Menu widget compatibility to v3.3.0
• We Updated Data Widgets compatibility to v2.5.9

Marketplace release v7.0.0

• We updated the module to Mendix 9.18.0
• We switched to a task queue implementation for sending notifications in the background
• We fixed an issue where notifications were sent multiple times in a multi-instance deployment scenario (#164228)
• We fixed an issue where the last notification could remain in 'Pending' status (#167042)

Marketplace release v6.2.0

• We added a status enumeration (Active, Inactive, Invalid) to the Device entity
• We added a scheduled event that sets the status of a Device to 'Inactive' if it has not been used for at least two months (following the FCM best practices)
• We added support for handling invalid token responses from FCM and APNS. If a registration token is known to be invalid, we set the Device status to 'Invalid'
• We removed all write access to the Device entity for User/Anonymous roles (was already restricted to owner only)
• We updated the dependencies for the module. Please make sure to review the userlib folder in your project after updating. See the list below for the changes in this release

Updated:

• auto-value-annotations-1.8.2.jar -> auto-value-annotations-1.9.jar
• commons-codec-1.13.jar -> commons-codec-1.15.jar
• google-auth-library-credentials-1.4.0.jar -> google-auth-library-credentials-1.7.0.jar
• google-auth-library-oauth2-http-1.4.0.jar -> google-auth-library-oauth2-http-1.7.0.jar
• google-http-client-1.41.0.jar -> google-http-client-1.41.8.jar
• google-http-client-gson-1.41.0.jar -> google-http-client-gson-1.41.8.jar
• gson-2.8.9.jar -> gson-2.9.0.jar
• netty-buffer-4.1.74.Final.jar -> netty-buffer-4.1.78.Final.jar
• netty-codec-4.1.74.Final.jar -> netty-codec-4.1.78.Final.jar
• netty-codec-dns-4.1.74.Final.jar -> netty-codec-dns-4.1.78.Final.jar
• netty-codec-http-4.1.74.Final.jar -> netty-codec-http-4.1.78.Final.jar
• netty-codec-http2-4.1.74.Final.jar -> netty-codec-http2-4.1.78.Final.jar
• netty-codec-socks-4.1.74.Final.jar -> netty-codec-socks-4.1.78.Final.jar
• netty-common-4.1.74.Final.jar -> netty-common-4.1.78.Final.jar
• netty-handler-4.1.74.Final.jar -> netty-handler-4.1.78.Final.jar
• netty-handler-proxy-4.1.74.Final.jar -> netty-handler-proxy-4.1.78.Final.jar
• netty-resolver-4.1.74.Final.jar -> netty-resolver-4.1.78.Final.jar
• netty-resolver-dns-4.1.74.Final.jar -> netty-resolver-dns-4.1.78.Final.jar
• netty-transport-4.1.74.Final.jar -> netty-transport-4.1.78.Final.jar
• opencensus-api-0.28.0.jar -> opencensus-api-0.31.0.jar
• opencensus-contrib-http-util-0.28.0.jar -> opencensus-contrib-http-util-0.31.0.jar
• pushy-0.13.9.jar -> pushy-0.13.10.jar
• slf4j-api-1.7.28.jar -> slf4j-api-1.7.36.jar

Removed:

• netty-tcnative-classes-2.0.48.Final.jar

Added:

• netty-transport-native-unix-common-4.1.78.Final.jar

Marketplace release v5.4.0

• We added a status enumeration (Active, Inactive, Invalid) to the Device entity
• We added a scheduled event that sets the status of a Device to 'Inactive' if it has not been used for at least two months (following the FCM best practices)
• We added support for handling invalid token responses from FCM and APNS. If a registration token is known to be invalid, we set the Device status to 'Invalid'
• We removed all owner write access to the device entity for User/Anonymous roles (was already restricted to owner only)