Skip to content

Releases: awesomemotive/pushengage-android-sdk

Release 0.1.0

05 Jun 07:27
894c481

Choose a tag to compare

What's New in 0.1.0

  • User Identification — tie subscribers to your own user records

    Associate a subscription with first-party identity fields (and clear them on sign-out) so campaigns and segments can be personalized from your own data.

    • identify(JSONObject fields) / identify(JSONObject fields, PushEngageResponseCallback callback) — upsert subscriber fields. Valid keys are restricted to the predefined set: first_name,
      last_name, email, phone, gender, dob, language, profile_id, country, city, state, zip. Values must be String, Number, or Boolean. If every requested field already matches the locally
      cached value, the call short-circuits with no network request.
    • logout(List fieldNames) / logout(List fieldNames, PushEngageResponseCallback callback) — remove identifying fields while keeping the device subscribed for push. Passing
      null or an empty list clears the default PII set (first_name, last_name, email, phone, gender, dob, profile_id); pass an explicit list to scope the removal.
  • Custom Event Tracking — drive triggered campaigns from in-app actions

    • trackEvent(TrackEvent event) / trackEvent(TrackEvent event, PushEngageResponseCallback callback) — send a custom event for the current subscriber. Custom events are used to trigger or
      exit workflows based on subscriber activity in your app, such as adding items to a cart, completing a purchase, or any custom action you define.
  • Notification Customization

    • setBadgeCount(int count) — control the numeric badge displayed alongside notifications the SDK builds. Pass 0 to clear, a positive integer to set. Applied via
      NotificationCompat.Builder.setNumber(count); surfaces in the system long-press menu. Negative values are coerced to 0.
  • Diagnostics

    • setFcmConfigErrorListener(FcmConfigErrorListener listener) — register a callback that fires when the SDK detects a mismatch between your app's local Firebase configuration and the
      configuration registered for your PushEngage site. Use this during integration to catch sender-ID or project-ID drift early — when a mismatch is detected at sync time, the SDK also skips
      the subscribe call so a permanently-undeliverable subscriber is not created on the server. Pass null to clear a previously-registered listener.

Release 0.0.6

21 Aug 13:25
814127f

Choose a tag to compare

Added

  • requestNotificationPermission() method for requesting notification permissions with callback support
  • getNotificationPermissionStatus() method to check current permission status ("granted"/"denied")
  • getSubscriptionStatus() method to check if user is subscribed to push notifications
  • getSubscriptionNotificationStatus() method to check if user can receive notifications
  • getSubscriberId() method to get unique subscriber hash/ID
  • unsubscribe() method to programmatically unsubscribe users
  • subscribe() method to programmatically subscribe users to push notifications
  • Enhanced initialization with conditional auto-subscription based on permission state

Release 0.0.5

05 Jun 09:42
1c93501

Choose a tag to compare

  • Added support for Trigger Campaign
  • Added support for goal tracking

Release 0.0.4

01 Dec 08:32
e3fe620

Choose a tag to compare

  • Support for Android 13 notification permission added
  • Minor performance improvements

Release 0.0.3

26 Aug 08:34
fa9abd8

Choose a tag to compare

Added method overloading for public API

Initial release

25 Aug 10:12
cc0158c

Choose a tag to compare

Initial release