Release 4.6.1

This is Release 4.6.0, but with Android 15 support and targeting. If you are targeting Android 15 you will want to use this version, if you are still targeting Android 14 please use Release 4.6.0.

Updated gradle version.
compileSdk and targetSdkVersion changed from 34 to 35 - Android 15 support.
Updated dependencies.
Added proper insets to PulsateCardBackFragment, PulsateFeedFragment, PulsateThreadFragment, PulsateBigInApp to support Android 15 edge to edge.

Release 4.6.0

Version Updates:

Changed Java Version to 17 from 1.8.
Changed minSdkVersion to 28

New Features:

Added new method getFeedUnreadCount() to allow direct access to unread count and help keep inside App badges / unread count up to date - https://docs.pulsatehq.com/v2.8.2/reference/badges#using-getfeedunreadcount
Added new callback to showFeed - onFeedClose - this informs you when the user has exited the Pulsate Feed. This is a good time to for example call getFeedUnreadCount() and update your UI.
Added PulsateConfig with two flags
PulsateConfig.NOTIFICATION_CHANNEL_SHOW_BADGES - https://docs.pulsatehq.com/v2.8.2/reference/badges#app-icon-badges
PulsateConfig.NOTIFICATION_USE_LARGE_ICON. - https://docs.pulsatehq.com/v2.8.2/reference/theming-1

Bug Fixes:

Fixed some margins in Big In Apps.
Fixed possible crash in PulsateBeaconManager logCurrentState.
Added try catch to getFcmToken(). On failure it will return an empty token instead of crashing.
Fixed warning caused by nested res directories.

Release 4.5.6

Bug Fixes:

Fixed possible crash that could happen on some devices when setting a custom vibration pattern for Notification Channel

Release 4.5.5

New:

New method "UserHasLoggedIn"
- Enables in apps
- Shows last bounced in app
- Sets user as authorized
- Shows last unauthorized message
New method "UserHasLoggedOut"
- Disables in apps
- Sets user as unauthorized
New method "getUnreadCount" - this method will send a request to Pulsate and return the current unread count for the user.
New interface IPulsateLinkListener - URLs and Deeplinks will be sent first to this new listener if set. On return false Pulsate will handle the URL / Deeplink. On true we return.

Improvements:

Stats will now sync more often
showLastInAppNotification will now always show an In App, even if In Apps have been disabled
showLastUnauthorizedMessage will now always open Feed, even if user is still unauthorized
Networking - added retries for when requests fail due to missing access token also added a limit to how many requests can be sent per minute to Pulsate.
Improvements to daily jobs.
Many other improvements to performance, moving code off the main thread, improving throttle / debounce / queue implementations.

Bug Fixes:

Many crash fixes reported to New Relic by SDK 4.1.20
Many ANR fixes reported to New Relic by SDK 4.1.20
Fixes to edge cases where destinations would not open - for example Push to Feed Post
Fixed edge cases where app would flash / flicker for unauthorized users when clicking on pushes if app was killed by the system instead of opening the Login page
Fixed edge cases where some users could fall into a loop that would cause them to spam end sessions for a few mins
Fixed bug with In App buttons not rendering properly. Depending on App theme In App buttons could be very small. In App buttons will now use their own button style based on Widget.AppCompat.Button and should always be the proper size.

Date	Version	Changelog
21.03.2024	4.5.0	New Features: - PulsateSDK crashes and anrs will now be collected and sent to New Relic.Improvments: - Dependecy updates.
27.02.2024	4.4.0	Location Rework: - Location and Geofencing have been reworked. The amount of active location updates caused by the SDK has been reduced by more than 90% in some cases. Most location updates still happening are caused by the Google Geofencing API itself.Improvments: - Periodic Jobs will now use ExistingPeriodicWorkPolicy.KEEP instead of ExistingPeriodicWorkPolicy.UPDATE. - Fixed Proguard settings. These proguard rules will be used in apps that use obfuscation automatically. - Dependency updates.Bug Fixes: - Fixed a possible issue where start_session would not happen on older devices or devices with older versions of Google Play Services.
01.02.2024	4.3.0	Security: - Updated Okhttp 4.11.0 to 4.12.0 - https://ossindex.sonatype.org/vulnerability/CVE-2023-3635?component-type=maven&component-name=com.squareup.okio%2Fokio&utm_source=ossindex-client&utm_medium=integration&utm_content=1.7.0Network: - Update User / Privacy / Location / Push settings will all be debounced to merge multiple calls into one. This will reduce the amount of requests done and prevent a possibile race condition where we would have two active request updating the same setting to different values. - Added throttle to Pulsate Jobs to prevent from scheduling multiple Jobs for syncing user data, restaring geofencing, end session etc. - Added a delay to startSession and endSession to give the SDK enough time to either initialize all it's dependencies or save all stats before sending them. - Added request limiter - the SDK is now limited to 100 requests per minute, after that the SDK will stop sending requests for 5mins and will send a log to Pulsate. We have found a probable bug on Samsung devices running Android 12 that could cause background Jobs to spam Pulsate. This happens very rarely. - Sessions will now fail instantly if the user has been logged out - we will not retry starting a session multiple times for logged out users.Improvements: - Improvements to stat collection. SDKs will now trigger the whole flow of stats that must have happened to get to this place. - Reduced the amount of background location updates done while geofencing. - Added debounce to PulsateBeaconManager, PulsateGeofenceManager updates to prevent multiple updates overriding. - In Apps will print errors only after last retry failed instead of printing errors on every retry fail. - Small In App cleanup. Early retries will happen faster. - Removed deprecated onBackPressed() and replaced with onBackPressedDispatcher.onBackPressed(). This is required for supporting predictive navigation in future Android releases. This might cause the Android 10 leak to reappear - this leak is a Android System leak, not a Pulsate leak.Bug Fixes: - Fixed possible race conditions that could have resulted in having the wrong state for user / settings when changing a value multiple times in a row. - We will no longer send empty user data to the BE. If firstName / lastName / email / phone are null or empty we will not send it to the BE. - Fixed showing user and admin initials in Talks where avatars are empty. - Fixed Talk button text color.
17.07.2023	4.2.3	Bug Fixes: - Fixed ANR caused by Thread.setDefaultUncaughtExceptionHandler(this) not properly calling defaultUEH!!.uncaughtException(t, e) when the crash is not Pulsate related.
27.06.2023	4.2.2	Bug Fixes: - Fixed collecting stats for second button in In Apps.
15.06.2023	4.2.1	Bug Fixes: - Removed test button from Feed
14.06.2023	4.2.0	New Features: - Dual Buttons - new design, Big In App / Card / Back of Card can now have up to two buttons. - New Colors in colors.xml pulsate_card_one_btn_color pulsate_card_one_txt_color pulsate_card_two_btn_color pulsate_card_two_txt_color pulsate_card_two_btn_outline_color pulsate_card_back_one_btn_color pulsate_card_back_one_txt_color pulsate_card_back_two_btn_color pulsate_card_back_two_txt_color pulsate_card_back_two_btn_outline_color pulsate_big_in_app_one_button_color pulsate_big_in_app_one_button_text_color pulsate_big_in_app_two_button_color pulsate_big_in_app_two_button_text_color pulsate_big_in_app_two_button_outline_colorStats: - Created new usecase - PulsateSendUpdateUserRequest. This usecase is responsible for sending the update request to the BE with stats and user data. This request will only happen if there are actually stats and user data that are waiting to be synced. - Added PulsateSendUpdateUserRequest to beacon events. - Added PulsateSendUpdateUserRequest to geofence events. - Added PulsateSendUpdateUserRequest to location updates. Only happens when geofence list is refreshed. We try to wait at least 1km between each refresh. - Added threshold for PulsateSendUpdateUserRequest. If user actions and user updates size does not pass the threshold the request will not happen. This is to prevent empty requests and prevent background updates to happen for every single update. Thresholds: Alias Change - 0 Logout - 0 Daily sync - 0 Geofence - 1 Beacon - 1 Location Update - 1Other: - PulsateBigInApp and PulsateCardViewHolder code cleanup. - Fixed animations between fragments. - Fixed margins in Big In Apps. - Changed Title for single card view from "New Card" to "New Feed Post".
21.03.2024	4.1.20	New Features: - PulsateSDK crashes and anrs will now be collected and sent to New Relic.
05.05.2023	4.1.12	Improvements: - PulsateLocationManagerPrivate will now restart faster if restart was initialized by PulsateRestartLocationManagerJob. - PulsateRestartLocationManagerJob changed to CoroutineWorker to match all other workers. doWork moved to Dispatchers.IO. - Job logs will no longer be save to database.Stat Fixes: - Moving user data deletion logic to PulsateDataManager. This will help simplify and better control user related logic. - Moving user data sync logic to PulsateDataManager. This will help simplify and better control user related logic. - Added additional user data syncs - on alias change and on user logout.Crash Fixes: - Crash Fix - null view bindings. All view bindings have been rewritten to use _mBinding?.let. This should prevent from trying to access any null view binding.
18.04.2023	4.1.10	Improvements: - SQLiteDiskIOException and SQLiteFullException will now cause the DB to clear all logs, historical data and will cause a DB VACUUM. - In Apps - should now properly catch dismiss stats on exiting the App. - enqueueUniquePeriodicWork will now use UPDATE instead of REPLACE. REPLACE has been deprecated. - The PulsateSDK will do a DB cleanup and DB vacuum on first run after updating SDK to 4.1.10. - Replaced GlobalScope in most places with custom scopes or lifecycleScope.ANR Fixes: - PulsateBeaconManager - start() and stop() will now use Dispatchers.IO, this should reduce the chance of any ANRs. - PulsateGeofenceManager - start(), stop(), updateGeofences() and handleLocationUpdate() will now use Dispatchers.IO, this should reduce the chance of any ANRs. - PulsateLocationManager - handleStartPulsateSessionEvent() will now use Dispatchers.IO, this should reduce the chance of any ANRs. - PulsateLocationManagerPrivate - start() will now use Dispatchers.IO, this should reduce the chance of any ANRs. - PulsateNewRelicManager - logs will now use Dispatchers.IO, this should reduce the chance of any ANRs. - PulsateSendGeofenceJob - will now use Dispatchers.IO.
27.01.2023	4.1.6	Dependency Update: androidx.appcompat:appcompat from 1.5.1 to 1.6.0 org.altbeacon:android-beacon-library from 2.19.4 to 2.19.5 com.google.firebase:firebase-messaging from 23.1.0 to 23.1.1 androidx.test:runner from 1.5.1 to 1.5.2 androidx.test.ext:junit from 1.1.4 to 1.1.5 Improvements: - In App will retry to show every 5 secs, max 10 times. After around 1 min the In App will not be retried anymore and an IN_APP_BOUNCED event will be triggered. - getPulsateDaggerComponent() renamed to getDI() - helps shorten code and makes code more readable. - getInbox() errors will now properly be logged and shown in logcat. - In Apps rework - Moving from RxJava to Coroutines, moving In App Flow logic into "tryToShowInAppMessage" - this makes it easier to follow the flow and find possible bug, collecting stats for In Apps simplified - moved some logic into "tryToShowInAppMessage". - Start session will retry 5 times before failing - this retries the "if/else" conditions needed to start a session not the network call itself. - uncaughtExceptions will now check if stacktrace contains "pulsatehq" before sending the crash to New Relic. - Fixed getUserData() when there is no current user set. getUserData() will now use getActiveUserAlias() which creates a default user if there is no current user. This fixes PulsateUserManagerTests. - Stats for pushes and in apps will be unique per session. - PulsateUploadAndDeleteNewRelic - optimizing code.Crash Fixes: - Crash Fix - Deleting the last item in the inbox will no longer crash. - Crash Fix - createDynamicView - will now check if "attrsList" is before casting to protect from any possible chance of a crash. - Crash Fix - Beacons monitoring can be updated 1 time per minute. When multiple updates happen in a row the next update will wait 1 minute before applying any changes. - Crash Fix - SecurityException - Notifications now require a permission the user can deny, calling .notify to show a push without checking the permission can cause a crash. Added SecurityException try / catch to all .notify calls. - Crash Fix - PulsateFeedViewModel IndexOutOfBoundsException - PulsateFeedViewModel will now use synchronized(mFeedState) when doing any changes to the mFeedState and it's lists. - Crash Fix - PulsateBeaconManager IndexOutOfBoundsException - PulsateBeaconManager will now use synchronized(mAllPulsateBeacons) when doing any changes to the mAllPulsateBeacons list. - Fixed crash - Feed IndexOutOfBoundsException. - Fixed crash - Null Pointer binding. - Fixed crash - Null Pointer In App Point. - Fixed crash - ClassCastException - PulsateCardViewHolder will now check if frontElementAttrs IS before casting it. - Fixed crash - IllegalArgumentException: You cannot start a load for a destroyed activity - Glide will now use application context when loading images into PulsateBigInApp.Bug Fixes: - Deleting the last item in the inbox will properly animate. - Added missing else statements to when brackets. - PulsateCardAttrsSerializer - when type is unknown we will now return PulsateEmptyAttrsDTO. - PulsateCardAttrsDeserializer - when type is unknown we will now return PulsateEmptyAttrsDTO. - Fixed - Feed Display issues - no internet connection message displayed on feed loading screen. Added a 5sec delay after connection network changes before sending connection network errors to give the device time to potentially recover from a short connection loss. - Fixed - Feed Display issues - Bottom of feed continuously loading instead of displaying you have reached the bottom of the feed. PulsateFeedItemLoading and PulsateFeedItemEnd now have unique guids and different types, this fixes PulsateFeedDiffUtilCallback and RecyclerView updates. - Fixed bug in PulsateInboxViewModel mPulsateUserDataLiveData - LiveData setValue called from outside main thread.
17.11.2022	4.1.0	In Apps: - showLastInAppNotification() changed to showLastInAppNotification(force: Boolean = false) - Shows the last in app notification that was blocked due to setInAppNotificationEnabled(FALSE) being called. The force variable by default is FALSE, if you set it to TRUE the SDK will ignore some checks and will try to force the In App to display. For example when force is true the In App will show even if setInAppNotificationEnabled(FALSE) was called and In Apps are disabled. - Will now fail early if they are empty or null. - Added new retry disposable Timer. The disposable will be disposed to make sure there is only one retry job running for In Apps at any time. - ShowInAppMessageDisposable will now be disposed to make sure there is only one show job running for In Apps at any time. - Will retry when they IN_APP_BOUNCE is registered. - In App retry limit increased to 10. New features: - New classes - IPulsateErrorListener & PulsateError - All SDK errors will be pushed to this listener for Developers to be able to log / debug / react to them. Currently only supports In Apps. setPulsateErrorListener(listener: IPulsateErrorListener) added to IPulsateManager.Improvements: - Implemented KSP for Room and Glide. - Added exception: Exception variable to PulsateError class. - PulsateErrors will now be sent to New Relic. - PulsateUserDao rewritten to use Coroutines instead of RxJava. - PulsateSettingsDao started rewrite to use Coroutines instead of RxJava.Bug Fixes: - Removed PulsateAppDatabase encryption - Encryption used CWAC SafeRoom which was deprecated years ago and no longer works properly with Kotlin and Room.Tests: - Added tests for all PulsateUserManager methods related to changing user data. - PulsatePrivacy - added value: String used for tests. - PulsateGender - added value: String used for tests. - PulsateRoomMigrationTest - tests migration from version 7 to 8 and version 8 to 13.
26.10.2022	4.0.3	Improvements - The badge count will now be tracked locally when possible and will send updates to IPulsateBadgeUpdateListener in real time. When a user clicks on a campaign that is unread we set it to read and reduce the badge by 1, when a users clicks on a talk that has unread messages we set the talk to read and reduce the badge by the amount of messages that were unread. - Read / Unread state will be tracked locally, multiple Feed refreshes should always show the proper state.Bug Fixes - Fixed sending push_click stats for talks. This fixes a possible 500 error when sending stats to the BE.Others - Dependency updates. - Code cleanup using ktlint.
29.09.2022	4.0.0	Major Changes - The SDK has been rewritten to Kotlin. - Target SDK changed to 33. - New permission required - POST_NOTIFICATIONS. - Dependency update. For more info please read this article - https://docs.pulsatehq.com/v2.8.2/reference/dependenciesNew Features - Android badges will now be supported. For more info please read this article - https://docs.pulsatehq.com/v2.8.2/reference/android-badges - Crash logging. The SDK will now log crashes caused by the Pulsate SDK and send them to Pulsate.Improvements - forceAttributeSync() will now be delayed by 5 secs and will combine all calls to forceAttributeSync() into one. - Orientation change will no longer cause the Feed and Threads to redownload items. - Removing BroadcastReceivers, jobs will now directly do their work. - Removed EventBus. - Requests will now retry 3 times if API Access Token is not generated before failing a request. - Reworked how API Access Tokens are generated. - Improved Database synchronization when used from multiple threads. - Improved PulsateProvider synchronization when used from multiple threads. - Fixed multiple Feed bugs caused by orientation change.Geofencing - Reduced the amount of location updates done by the SDK. - Improved goefence accuracy.Beacons - Changed exit period to 30 secs to reduce the amount of false exits.In Apps - In Apps will no longer show up multiple times when changing screen orientation or leaving the App. - Added additional checks to In Apps to prevent multiple In Apps to be drawn.Bug Fixes - Pulsate Feed will now work better on screen orientation change. - Added security checks to dagger. Will now only ever create a single instance. - Fixed multiple issues that could cause daily jobs to never run. - Fixed Toolbar to properly take the full width on Foldables, Tablets, Chromebooks. - Fixed showing messages that were blocked for unauthorized users. - Fixed opening the proper destination when opening multiple push notifications at a time.Crash Fixes - Fixed crashes caused by process death or app recreation. - Fixed a crash caused by ProcessLifecycleOwner.
05.12.2022	3.8.2	Improvements: - Backported some In App Improvements from 4.1.0.In Apps - showLastInAppNotification() changed to showLastInAppNotification(force: Boolean = false) - Shows the last in app notification that was blocked due to setInAppNotificationEnabled(FALSE) being called. The force variable by default is FALSE, if you set it to TRUE the SDK will ignore some checks and will try to force the In App to display. For example when force is true the In App will show even if setInAppNotificationEnabled(FALSE) was called and In Apps are disabled. - In Apps will no longer be deleted after retry ends.
13.01.2022	3.8.1	Improvements: - Converted Workers to CoroutineWorkers.Bug Fixes: - Added missing tryOnError() and onComplete() callbacks to BroadcastReceivers. - Fixed WorkerManager crash pre API 31 - setExpedited() isn't enough, we also needed to provide ForegroundInfo. The documentation doesn't make this very obvious, and there's no API enforcement.
15.12.2021	3.8.0	Important Changes: - Added Android 12 Support - Added Accessibility SupportBreaking Changes: - Set minSdkVersion to 23 (Android 6.0). - New Permissions required for beacons android.permission.BLUETOOTH android.permission.BLUETOOTH_ADMIN android.permission.BLUETOOTH_SCAN android.permission.BLUETOOTH_CONNECTImprovements - Added Kotlin. The SDK will be totally rewritten to Kotlin in the next releases. - Added the possibility to remotely enable / disable debug mode and send logs to Firebase. - Fixed geofences and beacons on Android 12. - Updated to newest WorkManager, added expedited jobs. - Moved some work done by the SDK from the main thread to the io thread.In App Rework: Improvements: - In Apps will now survive activity swaps. - Added In App validation. If the In App fields are not valid the In App will not show. - Added In App retry. After an In App fails to show it will retry 3 times. - Added new In App event - in_app_error. - Added Logs.Bug Fixes: - Fixed possible scaling issue for big In Apps. - In Apps will now close the keyboard before showing. The keyboard could cause scaling issues.Beacon Rework: Important!! New Permissions required for beacons android.permission.BLUETOOTH android.permission.BLUETOOTH_ADMIN android.permission.BLUETOOTH_SCAN android.permission.BLUETOOTH_CONNECTImprovements: - Added Support for Android 12. - Updated AltBeacon Library to version 2.19.3 - Fix failing intent-backed scans broken by Android 12 changes in the 2.19 release. - Reworked beacon event sync. The chain for syncing is now - Directly -> Broadcast Receiver -> Background Job. - Added Logs.Bug Fixes: - Fixed saving beacons to database. Previously beacons could get deleted when startSession would happen without data.Geofence Rework: Improvements: - Added Android 12 support. - Reworked geofence event sync. The chain for syncing is now - Directly -> Broadcast Receiver -> Background Job. - Added Logs.Bug Fixes: - Fixed saving geofences to database. Previously geofences could get deleted when startSession would happen without data.Notification Rework: Improvements: - Replying to a Pulsate Notification will now send the reply, inform the user the reply was sent successfully and delete the notification. - Added Logs.Bug Fixes: - Fixed possible crash when the user receives multiple notifications to the same card / talk.Bug Fixes: - Removed com.google.android.geo.API_KEY from SDK. - Fixed crashes in In App and Card when attrs for front elements are empty. - Fixed crash - java.lang.IllegalStateException: schedule()/enqueue() called more than 250 times in the past 60000ms. - Fixed crash- Work Manager IllegalStateException - WorkManager will now try to getInstance, on fail it will try to create a WorkManager with custom config, on fail it will return null and not schedule a job. - Fixed possible crashes caused by sending error events to no longer active emitters.
18.06.2021	3.7.1	SDK Distribution: JFrog has shut down JCenter and Bintray. The Pulsate SDK will now be distributed using MavenCentral. To download the newest versions of Pulsate you must be connected to MavenCentral. Current versions of the Pulsate SDK on MavenCentral can be found here - https://mvnrepository.com/artifact/com.pulsatehq.sdk/PulsateSdk Breaking Changes: - Set minSdkVersion to 21 (Android 5.0).New Features: - Stats - the SDK will now gather stats from pushes, in apps, cards and send them to the server to allow showing advanced campaign stats. - Test Mode - added new Pulsate Test Mode. During Test Mode the SDK will show a notification that the SDK is in Test Mode, clicking on the notification will take the user to the Test Mode UI, where the user can view geofence logs, beacons logs, network logs and send all logs to Pulsate Developers.Improvements: - Reworked end session logic to work better on devices that are overly aggressive with killing / blocking Apps from doing any work in the background. - Big In Apps - improved scaling and appear animation on multiple devices. - Added collecting background_location_permission. - Updated / Removed many dependencies. - Code cleanup.Bug Fixes: - Fixed possible crash when gathering user actions. - Fixed showing .jpeg images in Rich Push Notifications. - Fixed edge cases where the SDK would not clear data after sending it to the server. - Fixed possible leaks introduced in Android 10.
25.11.2020	3.6.0	Improvements: - Fixed a lot of warnings reported by Code Inspect. - Fixed possible memory leaks. - Proguard rules cleanup. - Layouts cleanup. - Deprecated FirebaseInstanceId replaced with FirebaseMessaging - Removed 24h restriction on downloading geofences and beacons. Start Session will now always download geofences and beaconsBug Fixes: - Pulsate BeaconManager will now try to catch all exceptions and handle them silently in the SDK. - Notification Channels will be created on App onCreate() callback instead of creating them in the FCM onNewToken() callback. - Removed setIntent(null); from PulsateInboxActivity this should fix an issue where unauthorized intent wasn't properly set.
12.11.2020	3.5.0	1. New Features - Feed title text size can now be changed. To change the text size add "pulsate_feed_title" to your dimens.xml. - Card button colors can now be changed. To change add "pulsate_card_left_btn_color", "pulsate_card_right_btn_color", "pulsate_card_single_btn_color" to your colors.xml 2. Improvements: - Replace databinding with viewbinding. - Updated Firebase to newest versions - firebase-core:18.0.0, firebase-messaging:21.0.0 - Updated many dependencies to newest versions. - Updated to newest Gradle version. - Removed limits for Admin message in In App Messages and Pulsate cards. The SDK would limit Admin message to 2-4 lines while the CMS would not have any limits. 3. Bug Fixes: - Fixed showing In App Notifications for unauthorized users. - Fixed crash in PulsateBeaconManager when beacon identifiers are broken. The SDK will now ignore beacons that are not properly setup. - Fixed crash when user minimizes App when on the back of a card and clicks on a push notification that opens a new card.
13.10.2020	3.4.3	1. Bug Fixes: - Fixed method - showLastInAppNotification().
05.10.2020	3.4.2	1. Bug Fixes: - Crash Fix - Fixed crash that happens when unauthorized users enter the Pulsate Inbox
01.09.2020	3.4.1	1. New Features: - New method - updatePhoneNumber() - Updates the user's phone number. Gets updated when entering background. - Implemented Screen Recording - the SDK will automatically track what screens of the App the user visits. 2. Improvements: - Database - Less DB actions need to take place per update. Fixed a possible concurrency issue. - Broadcasts - will be handled with LocalBroadcastManager. This makes sure broadcasts stay within the App and are not System wide. This also fixes very rare crashes on some phones. - Updated dependencies. Git stats. 3. Bug Fixes: - Fixed possible crash in Pulsate Feed.
01.07.2020	3.3.1	1. Bug Fixes: - Improved scaling images in In App Notifications. - Improved scaling images in Feed Cards.
10.06.2020	3.3.0	1. New Features: - New method - getFeed(int page, IPulsateValueListener listener). - New method - handleFeedClick(PulsateInboxItem pulsateInboxItem, int destination). - New Method - initializeBackgroundPowerSaver() - Initializes the Beacon Background Power Saver Mode. This mode can save up to 60% of battery in the background. Exit events can happen almost instantly, but depending on device / OS version in can take up to 15 mins to trigger an exit. 2. Improvements: - Updated Gradle to version 4.0.0. - Update Android Studio to version 4.0.0. PulsateBeaconManager code cleanup. - Removed background optimizations for beacons. This makes exit events more responsive. Apps that don't use Background exit events can turn on the background battery saver using the new method - initializeBackgroundPowerSaver() - Improved App Foreground / Background checks. 3. Bug Fixes: - Now properly only the first page of the Feed will be cached. The bug would cause next pages to overwrite previous pages. - Single Card Feed now properly works after pausing the App. Before if the user paused the App while in single Card Feed the view would stop reacting to clicks. - Added missing ReentrantLock unblock to start session. - Crash Fix - fixed possible In App Notification Crash.
16.04.2020	3.2.0	1. New Features: - Added Revenue Events which allow you to track event name, event value and event currency. More info can be found here - https://pulsate.readme.io/v2.8/docs/setting-custom-events#revenue-events 2. Bug Fixes: - Fixed possible crashes in Broadcast Receivers when PendingResult is null. - Fixed possible crash in PulsateCardFrontFragment when Activity is null. - Added a possible fix to possible crashes when Database queries end with an Error and the Observable asking for the data has already been disposed.
08.04.2020	3.1.0	1. Breaking Changes: - Pulsate.install() removed. Pulsate.install() has been deprecated in previous builds and should no longer be used. Pulsate now automatically installs. - Removed Microfencing methods from PulsateManager since Microfencing is not used in the SDK. - startSession will now download Geofence and Beacon data only once per day. - Beacons and Geofences are now set to be active for 1 hour, so any events within that time frame will be labeled as duplicates. - When testing the SDK set PulsateDebugLogs.LOG_LOCATION_MANAGER = true. This causes startSession to download data every time and allows Beacons and Geofences to be triggered every 5mins. Do not use this in release builds. This can slow down the SDK, increase the amount of data uploaded and downloaded by the SDK and increase it's size over time because Logs are gathered and saved in the SDK Database. 2. Geofencing Changes: - Geofence events will now be sent immediately, if the event fails a PulsateJob will be registered to retry within 15mins. Events that return 404 Not Found will not be retried. - There can be more than one active geofence now and all of them will be separately monitored. This change can help us filter out false positives. - Geofence events now use "Triggering Location" from the "GeofencingEvent" received from the system instead of trying to scan for the user location. - Added many fallbacks to location checks. The SDK will first try to do a location scan, on fail it will ask Fused Location for last known location, on fail it will use the last SDK known location. 3. Beacon Changes: - Updated to AltBeacon 2.16.4 which fixes a possible crash when scanning in background and improves discovering beacons on Samsung devices. - Beacon events will now be sent immediately, if the event fails a PulsateJob will be registered to retry within 15mins. Events that return 404 Not Found will not be retried. - Beacon events will now be filtered by UUID, Major and Minor on SDK side to not send to the server beacon events for beacons that don't exist server-side. - Foreground scan periods changed to help filter out possible false positives and reduce battery usage. - BeaconManager will now be set to BackgroundMode when the App is closed. BackgroundMode reduces the amount of scans happening to save battery. - Implemented BackgroundPowerSaver. BackgroundPowerSaver will help reduce battery usage on many devices. - Removed beacon ranging. The SDK will now rely on beacon monitoring which should work better in the background and reduce power usage. - Fixed possible race condition when adding and removing beacons. 4. Bug Fixes: - Fixed a bug that could cause Feed Cards to not be deleted after a user manually deleted them. - Fixed a bug that could cause startPulsateSession to sometimes call onSuccess 2 times. - Fixed a possible crash when PendingResult is null in the Geofence / Beacon BroadcastReceiver. - Fixed a posbbile crash when getting FCM Token from Firebase. - Fixed a bug that could cause the Database to desync. - Fixed possible Database race conditions in User Settings and SDK Settings. 5. Misc: - Added some missing getters to PulsateManager. - Updated some dependncies. 6. Test: - Improved test coverage for PulsateManager methods, User Settings, SDK Settings, Location, Geofecing, Beacons, Database.
29.01.2020	3.0.4	1. Removed bluetooth_state checks and request. 2. Renamed mContext to mApplication in places where the context was the application context. 3. Moved some layouts into subdirectories.
22.01.2020	3.0.3	1. Fixed possible Firebase / FCM crash. Firebase / FCM will now fail silently if it encounters any problems without crashing the App. 2. When Firebase fails the FCM token will be set to an empty string and startSession will happen normally instead of not happening at all. 3. Glide will now show a stack trace when it fails to load an image into a notification. 4. In App Notifications will check if activity is changing configuration or is finishing before showing.