Here are the different mobile library properties available for analysis in Heap, along with some nuances of what you’ll see in the results.
Core Library
This indicates whether this event was captured using the swift_core or android_core library. The swift_core library can run on iOS, iPadOS, tvOS, macOS, and visionOS; the android_core library can run on Android, Android Automotive, FireOS, and related operating systems.
Whether you're using one of our autocapture libraries or precision tracking via our track API, all native mobile tracking requires one of these two Core Libraries, depending on the type of device your app is running on.
Events captured on a webpage, rather than in a native mobile app, will show a Core Library value of web. Server-side and integration events will show a value of (No data) for this property.
Library Version
This is the version number of the Core Library that captured the event. You can compare these values to the values in our iOS and Android changelog files to better understand which version of Heap’s Core Libraries was running in your app when a given event was captured. This can be used to make sure your installed version of Heap is up to date.
Events captured on a webpage, rather than in a native mobile app, will also have a Library Version value reflecting the version of Heap.js installed on that page. Server-side and integration events will show a value of (No data) for this property.
Overlay Library
This indicates the Heap autocapture or bridge library used to capture events. The most common values are ios_capture, android_view_autocapture, android_compose_autocapture, react_native_autocapture, and flutter_autocapture, representing our autocapture SDKs. If you take advantage of Heap’s precision-tracking libraries in a cross-platform app, you may also see values like flutter_bridge, xamarin_bridge, or capacitor_bridge.
Events captured outside of a native mobile app, including events captured on your website, will show a value of (No data) for this property.
Overlay Library Version
This is the version number of the Overlay Library that captured the event. As with Library Version, you can compare these values to the values in our iOS and Android changelog files to better understand which version of Heap’s Overlay Libraries was running in your app when a given event was captured. This can be used to make sure your installed version of Heap is up to date.
Events captured outside of a native mobile app, including events captured on your website, will show a value of (No data) for this property.
Overlay Platform
This indicates the underlying platform your app was built on when a given event was captured. For events captured in fully native apps, this property will share its value with the Platform property; both will show the specific operating system version your app ran on. For events captured in cross-platform apps, this will show the version of React Native or Flutter your app was built with. In this case, you can use the Platform property to see which operating system your app ran on.
Events captured outside of a native mobile app, including events captured on your website, will show a value of (No data) for this property.