Releases: newrelic/video-agent-iOS
Releases · newrelic/video-agent-iOS
v4.1.1
v4.1.0
v4.0.5
v4.0.4
v4.0.3
v4.0.2
v4.0.1
Changes
- fixed concurrent access crash in NRTimeSinceTable
- fixed Inaccurate totalPlayTime
v4.0.0
Release Notes - v4.0.0
🎉 Major Features
Standalone Agent with Advanced Harvest Logic
- Introduced standalone initialization with advanced harvest logic for improved event processing
- Added multi-task harvest scheduler for efficient data collection and transmission
- Implemented priority-based event buffering system
- New optimized HTTP client with enhanced networking capabilities
Enhanced Event Management
- New crash-safe event buffer with persistent storage
- Integrated dead letter handler for failed event recovery
- Priority event buffer for critical events
- Default size estimator for optimized memory usage
Swift Support
- Updated iOS agent with Swift code support
- Added Swift example implementation (PiPExampleSwift)
- Improved Swift interoperability
🔄 Architecture Changes
Pod Restructuring
- Breaking Change: Renamed
NewRelicVideoCoretoNewRelicVideoAgent - Updated pod specifications and dependencies
- Streamlined component factory pattern
New Core Components
NRVAVideo- Main video agent interfaceNRVAVideoConfiguration- Centralized configuration managementNRVATokenManager- Enhanced authentication handlingNRVAHarvestManager- Centralized harvest orchestrationNRVAVideoLifecycleObserver- Video lifecycle managementNRVADeviceInformation- Device information collectionNRVAErrorExceptionHandler- Centralized error handling
Storage & Persistence
- New offline storage capabilities with crash recovery
- Crash-safe harvest factory for reliable data persistence
- Integrated dead letter handling for failed events
⚠️ Breaking Changes
- Pod Name Change:
NewRelicVideoCorehas been renamed toNewRelicVideoAgent- Update your Podfile:
pod 'NewRelicVideoAgent'
- Update your Podfile:
- Initialization Changes: New standalone initialization pattern with configuration objects
- API Changes: Some internal APIs have been refactored for the standalone architecture
v3.0.1
Changes
- Minor Change: The
errorNameattribute has been renamed toerrorMessage.
v3.0.0
Release Notes
New Features & Enhancements
- New Event Types Introduced
- VideoAction: This event type represents standard actions related to video playback and interaction.
- VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
- VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
- VideoCustomAction: A flexible event type for custom actions and interactions within video applications.
Deprecations
- MobileVideo
- The
MobileVideoevent type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.
- The
New Attributes Introduced
- We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types
Please refer to the data model documentation for more details.
Event Types
• VideoAction: Events triggered by general video interactions, such as starting, pausing, or seeking.
• VideoAdAction: Events related to ad playback, such as starting, completing, or skipping an ad.
• VideoErrorAction: Events triggered by errors encountered during video or ad playback.
• VideoCustomAction: Custom events defined to capture specific actions or interactions beyond default event types.
Impact & Actions Required
- Transition from MobileVideo: Users currently tracking
MobileVideoevents should adapt their implementations to utilise the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. - Update Implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
- Testing & Validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.
Additional Information
For more details on implementing these changes, refer to the updated documentation and integration guides available [here]. Should you have any questions or require further assistance, please reach out to our support team.