Swiftpack.co - Swift Packages by Bluedot-Innovation

Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.

Packages published by Bluedot-Innovation

Bluedot-Innovation/PointSDK-iOS 16.0.0-rc12
Bluedot PointSDK Framework CocoaPods https://ios-docs.bluedot.io
⭐️ 10
🕓 5 weeks ago
🔖 Release Notes

Releases

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.
16.0.0-rc12
5 weeks ago
PointSDK v16.0.0 (199) # SDK Version 16.0.0 We are excited to announce the release of Point SDK v16.0.0. This major update provides better architecture support with our migration to `XCFramework` for CocoaPods and Carthage and significantly enhances the data available in the `BDPGeoTriggeringEventDelegate` callbacks and new Tempo `tempoTrackingDidUpdate` callback. Here are the key highlights: ## New Features - **Improved Architecture Support:** Migrated to `XCFramework` for both CocoaPods and Carthage, significantly improving support for multiple architectures. - **Enhanced Geo-Triggering Data:** The `BDPGeoTriggeringEventDelegate` callbacks have been updated with more useful information to enhance your use cases. - **New Tempo Tracking Callback:** Added a new callback `tempoTrackingDidUpdate` to `BDPTempoTrackingDelegate` with customer’s ETA data. - **New Destination Information:** Each `BDZoneInfo` now contains destination information accessible via `BDLocationManager.instance().zoneInfos`. - **Support iOS 17 SDK:** Xcode 15 and iOS 17 SDK ## Changes - The `fences` property of `BDZoneInfo` is now non-optional in Swift. - Return a new structure `GeoTriggerEvent` in the `didEnterZone` and `didExitZone` callbacks that replaces `BDZoneEntryEvent` and `BDZoneExitEvent`. - Replaced the `onZoneInfoUpdate(zoneInfos)` callback with `didUpdateZoneInfo()`. The `zoneInfos` is no longer returned as part of this callback, access it via `BDLocationManager.instance().zoneInfos` instead. - Custom Event Meta Data is cleared when the SDK resets. ## Deprecated Features - **iOS 11 Support Discontinued:** The minimum deployment target is now iOS 12. - **Feature Removals:** - Real-time Data Sync feature - URL Action and Message Action - The `BDPointBackgroundLocationEnabledForWhenInUseKey` key in `Info.plist` (to set enable the Background Location Indicator) - **Deprecated Classes and Functions Removed:** Several deprecated classes and functions have been removed, providing a cleaner API. Please refer to the detailed release notes and our updated documentation for more information. We appreciate your feedback and are here to assist you with any questions.
16.0.0-rc11
5 weeks ago
PointSDK v16.0.0 (198) # SDK Version 16.0.0 We are excited to announce the release of Point SDK v16.0.0. This major update provides better architecture support with our migration to `XCFramework` for CocoaPods and Carthage and significantly enhances the data available in the `BDPGeoTriggeringEventDelegate` callbacks and new Tempo `tempoTrackingDidUpdate` callback. Here are the key highlights: ## New Features - **Improved Architecture Support:** Migrated to `XCFramework` for both CocoaPods and Carthage, significantly improving support for multiple architectures. - **Enhanced Geo-Triggering Data:** The `BDPGeoTriggeringEventDelegate` callbacks have been updated with more useful information to enhance your use cases. - **New Tempo Tracking Callback:** Added a new callback `tempoTrackingDidUpdate` to `BDPTempoTrackingDelegate` with customer’s ETA data. - **New Destination Information:** Each `BDZoneInfo` now contains destination information accessible via `BDLocationManager.instance().zoneInfos`. - **Support iOS 17 SDK:** Xcode 15 and iOS 17 SDK ## Changes - The `fences` property of `BDZoneInfo` is now non-optional in Swift. - Return a new structure `GeoTriggerEvent` in the `didEnterZone` and `didExitZone` callbacks that replaces `BDZoneEntryEvent` and `BDZoneExitEvent`. - Replaced the `onZoneInfoUpdate(zoneInfos)` callback with `didUpdateZoneInfo()`. The `zoneInfos` is no longer returned as part of this callback, access it via `BDLocationManager.instance().zoneInfos` instead. - Custom Event Meta Data is cleared when the SDK resets. ## Deprecated Features - **iOS 10 Support Discontinued:** The minimum deployment target is now iOS 11. - **Feature Removals:** - Real-time Data Sync feature - URL Action and Message Action - The `BDPointBackgroundLocationEnabledForWhenInUseKey` key in `Info.plist` (to set enable the Background Location Indicator) - **Deprecated Classes and Functions Removed:** Several deprecated classes and functions have been removed, providing a cleaner API. Please refer to the detailed release notes and our updated documentation for more information. We appreciate your feedback and are here to assist you with any questions.
16.0.0-rc10
6 weeks ago
PointSDK v16.0.0 (197) # SDK Version 16.0.0 We are excited to announce the release of Point SDK v16.0.0. This major update provides better architecture support with our migration to `XCFramework` for CocoaPods and Carthage and significantly enhances the data available in the `BDPGeoTriggeringEventDelegate` callbacks and new Tempo `tempoTrackingDidUpdate` callback. Here are the key highlights: ## New Features - **Improved Architecture Support:** Migrated to `XCFramework` for both CocoaPods and Carthage, significantly improving support for multiple architectures. - **Enhanced Geo-Triggering Data:** The `BDPGeoTriggeringEventDelegate` callbacks have been updated with more useful information to enhance your use cases. - **New Tempo Tracking Callback:** Added a new callback `tempoTrackingDidUpdate` to `BDPTempoTrackingDelegate` with customer’s ETA data. - **New Destination Information:** Each `BDZoneInfo` now contains destination information accessible via `BDLocationManager.instance().zoneInfos`. ## Changes - The `fences` property of `BDZoneInfo` is now non-optional in Swift. - Return a new structure `GeoTriggerEvent` in the `didEnterZone` and `didExitZone` callbacks that replaces `BDZoneEntryEvent` and `BDZoneExitEvent`. - Replaced the `onZoneInfoUpdate(zoneInfos)` callback with `didUpdateZoneInfo()`. The `zoneInfos` is no longer returned as part of this callback, access it via `BDLocationManager.instance().zoneInfos` instead. - Custom Event Meta Data is cleared when the SDK resets. ## Deprecated Features - **iOS 10 Support Discontinued:** The minimum deployment target is now iOS 11. - **Feature Removals:** - Real-time Data Sync feature - URL Action and Message Action - The `BDPointBackgroundLocationEnabledForWhenInUseKey` key in `Info.plist` (to set enable the Background Location Indicator) - **Deprecated Classes and Functions Removed:** Several deprecated classes and functions have been removed, providing a cleaner API. Please refer to the detailed release notes and our updated documentation for more information. We appreciate your feedback and are here to assist you with any questions.
16.0.0-rc9
7 weeks ago
PointSDK v16.0.0 (196) # SDK Version 16.0.0 We are excited to announce the release of Point SDK v16.0.0. This major update provides better architecture support with our migration to `XCFramework` for CocoaPods and Carthage and significantly enhances the data available in the `BDPGeoTriggeringEventDelegate` callbacks and new Tempo `tempoTrackingDidUpdate` callback. Here are the key highlights: ## New Features - **Improved Architecture Support:** Migrated to `XCFramework` for both CocoaPods and Carthage, significantly improving support for multiple architectures. - **Enhanced Geo-Triggering Data:** The `BDPGeoTriggeringEventDelegate` callbacks have been updated with more useful information to enhance your use cases. - **New Tempo Tracking Callback:** Added a new callback `tempoTrackingDidUpdate` to `BDPTempoTrackingDelegate` with customer’s ETA data. - **New Destination Information:** Each `BDZoneInfo` now contains destination information accessible via `BDLocationManager.instance().zoneInfos`. ## Changes - The `fences` property of `BDZoneInfo` is now non-optional in Swift. - Return a new structure `GeoTriggerEvent` in the `didEnterZone` and `didExitZone` callbacks that replaces `BDZoneEntryEvent` and `BDZoneExitEvent`. - Replaced the `onZoneInfoUpdate(zoneInfos)` callback with `didUpdateZoneInfo()`. The `zoneInfos` is no longer returned as part of this callback, access it via `BDLocationManager.instance().zoneInfos` instead. - Custom Event Meta Data is cleared when the SDK resets. ## Deprecated Features - **iOS 10 Support Discontinued:** The minimum deployment target is now iOS 11. - **Feature Removals:** - Real-time Data Sync feature - URL Action and Message Action - The `BDPointBackgroundLocationEnabledForWhenInUseKey` key in `Info.plist` (to set enable the Background Location Indicator) - **Deprecated Classes and Functions Removed:** Several deprecated classes and functions have been removed, providing a cleaner API. Please refer to the detailed release notes and our updated documentation for more information. We appreciate your feedback and are here to assist you with any questions.
16.0.0-rc8
16 weeks ago
PointSDK v16.0.0 (195) # SDK Version 16.0.0 We are excited to announce the release of Point SDK v16.0.0. This major update provides better architecture support with our migration to `XCFramework` for CocoaPods and Carthage and significantly enhances the data available in the `BDPGeoTriggeringEventDelegate` callbacks and new Tempo `tempoTrackingDidUpdate` callback. Here are the key highlights: ## New Features - **Improved Architecture Support:** Migrated to `XCFramework` for both CocoaPods and Carthage, significantly improving support for multiple architectures. - **Enhanced Geo-Triggering Data:** The `BDPGeoTriggeringEventDelegate` callbacks have been updated with more useful information to enhance your use cases. - **New Tempo Tracking Callback:** Added a new callback `tempoTrackingDidUpdate` to `BDPTempoTrackingDelegate` with customer’s ETA data. - **New Destination Information:** Each `BDZoneInfo` now contains destination information accessible via `BDLocationManager.instance().zoneInfos`. ## Changes - The `fences` property of `BDZoneInfo` is now non-optional in Swift. - Return a new structure `GeoTriggerEvent` in the `didEnterZone` and `didExitZone` callbacks that replaces `BDZoneEntryEvent` and `BDZoneExitEvent`. - Replaced the `onZoneInfoUpdate(zoneInfos)` callback with `didUpdateZoneInfo()`. The `zoneInfos` is no longer returned as part of this callback, access it via `BDLocationManager.instance().zoneInfos` instead. - Custom Event Meta Data is cleared when the SDK resets. ## Deprecated Features - **iOS 10 Support Discontinued:** The minimum deployment target is now iOS 11. - **Feature Removals:** - Real-time Data Sync feature - URL Action and Message Action - The `BDPointBackgroundLocationEnabledForWhenInUseKey` key in `Info.plist` (to set enable the Background Location Indicator) - **Deprecated Classes and Functions Removed:** Several deprecated classes and functions have been removed, providing a cleaner API. Please refer to the detailed release notes and our updated documentation for more information. We appreciate your feedback and are here to assist you with any questions.
SDK Version 15.6.8
33 weeks ago
PointSDK v15.6.8 (191) # SDK Version 15.6.8 - Fixed rare race condition crash caused by null pointer on startup.
16.0.0-rc4
40 weeks ago
PointSDK v16.0.0 (178) # SDK Version 16.0.0 - RC4 ## RC4 - Update CI to trigger both master + staging workflows in downstream Demo App + Host App - Fix issue localEventTime can be produced in a wrong format due to device locale, e.g. `2023-06-09T2:23:41.764 PM` where it should be `2023-06-09T14:23:41.764`, causing failure in Rainbow requests. - Fix bug properties of TempoTrackingUpdate are not accessible from Objective-C ## RC3 - Fix bug PercentageFilter not working ## RC2 - Remove UniversalFramework and use XCFramework for all integrations (Cocoapods, Carthage, SPM) - Update TestApp minimum deployment target to iOS 11 - Fix bug crossedFences includes duplicate crossings of the same fence - Refactor Bluebar mode, expose a new flag `backgroundLocationAccessForWhileUsing: boolean` to enable/disable Bluebar mode for While Using permission. - Override `setShowsBackgroundLocationIndicator:` so even if the main app sets this value to `true` for Always permission, the visual Bluebar will not show. - Show current Location permission level (denied, always, while using...) in Test App -> Operations -> BG Location Access For While Using screen. ## RC1 - Added method `toJson()` to `GeoTriggerEvent` class to convert to Json String. - Updated dev docs + Swift headers - Added Helper function for quick access to entryEvent and exitEvent in GeoTriggerEvent in didEnterZone: and didExitZone: callbacks. ## Alpha 2 - Fixed an UI bug in Test App CEMD Configuration screen when the buttons Random, Add, Clear can appear clustered on some devices - Fixed a crash bug in Test App CEMD Configuration screen when adding more than 20 items to SDK's CEMD - Fixed an error when the SDK fails to parse response from TempoStop event ## Alpha 1 - Fixed all warnings in Xcode project + Xcode Static Analyzer issues. Compiling the Xcode project should have no warnings now. - Renamed `onZoneInfoUpdate` to `didUpdateZoneInfo` to be more inline with other callbacks: `didEnterZone` and `didExitZone`. - Use SDK method to `sdkVersion` to determine SDK Upgrade scenario instead of Info.plist key ShortVersion as it can be replaced by the main app's version upon Appstore submission - `didEnterZone:` and `didExitZone:` callbacks are now returning a new model `GeoTriggerEvent`, using (almost) the same structure sent to Rainbow. During this refactoring, ZoneCheckInOutAction will now handle both performing check in/out AND notifying callbacks to the application. Previously the latter task was done by applicationNotificationAction. - `onZoneInfoUpdate` callback now will not include any data. Go to BDLocationManager.zoneInfos to access the latest downloaded zone infos. - New `crossedFences` field in FenceEntered triggerEvent in the Rainbow EntryNotification when checkin happens. Each CrossFence includes: fenceId, fenceName, location, crossTime. - New `tempoTrackingDidUpdate:` callback providing TempoTrackingUpdate to the application - Change to show toast message instead of Alert dialog in Test App when receiving GeoTriggering/Tempo callbacks - New `advertisingId` field in Rule request and Rainbow notification requests, also a new `AdvertisingID` field in Test App UI - Report `didStopTrackingWithError:` with error `tempoNotEnabled` if Tempo requests receive 403 from Rainbow - New CustomEventMetaData Configuration screen in Test App - Clear customEventMetaData when SDK resets - Replace mentioning of apiKey by projectId - Remove deprecated code - Delete Firebase Sync feature - Delete all traces of beacon in source code. (except in old DataModel) - Add new field `destination` in Ruleset download - Delete some leftover legacy code - Save `notificationPermission` in AppState - Replace AppCenter Crashlytics by Firebase Crashlytics - Replace GitHub Unit Test action by Bitrise
42 weeks ago
SDK Version 15.6.7
52 weeks ago
PointSDK v15.6.7 (156) # SDK Version 15.6.7 - Improved the reliability of the SDK under poor or no network access. - Fixed an issue that was preventing the Restart Notification to reliably start.
SDK Version 15.6.6
1 year ago
PointSDK v15.6.6 (150) # SDK Version 15.6.6 Reduced the time between retries when sending Entry/Exit events to our systems. This will help ensure that the Entry/Exit notifications are sent as soon as the device has network access.
iOS

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API | Analytics