Skip to content

Releases: mixpanel/mixpanel-android

Release v7.5.2

16 Apr 01:10
Compare
Choose a tag to compare

v7.5.2 (2024-04-16)

Enhancements

  • Remove Mixpanel internal tracking #835

Release v7.5.0

09 Apr 06:28
Compare
Choose a tag to compare

v7.5.0 (2024-04-09)

Enhancements

  • feat: add headers support for mixpanel proxy api calls #833

Release v7.4.2

15 Mar 23:25
Compare
Choose a tag to compare

v7.4.2 (2024-03-15)

Enhancements

  • feat: Enable data separation for each MixPanel API instance #830. Thanks so much @surajbokey-cred!

Release v7.4.1

02 Feb 23:35
Compare
Choose a tag to compare

v7.4.1 (2024-02-02)

Fixes

  • MPConfig instances created through MixpanelAPI are not being utilized when making API calls from AnalyticsMessages. #827

Release v7.4.0

22 Jan 19:05
Compare
Choose a tag to compare

v7.4.0 (2024-01-22)

Non-Singleton MPConfig Class

In this release, we've introduced a significant change to the MPConfig class. Previously implemented as a singleton, MPConfig is now designed to provide instance-specific configurations. This change allows the creation of multiple MPConfig instances, each with potentially different configuration settings. check the docs for more details

Enhancements

  • bump target API level to 33 #826
  • make 'MPConfig' not a Singleton in favor of supporting multiple configurations for multiple Mixpanel instances #825

Release v7.3.3

12 Jan 21:43
Compare
Choose a tag to compare

v7.3.3 (2024-01-12)

Fixes

  • Fix the potential NullPointException crash from getOptOutTracking #824

Release v7.3.2

14 Sep 02:37
Compare
Choose a tag to compare

v7.3.2 (2023-09-14)

Fixes

  • Fix integration event when opted out #819

v7.3.1

28 Apr 23:23
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v7.3.0...v7.3.1

Release v7.3.0

02 Mar 00:21
Compare
Choose a tag to compare

v7.3.0 (2023-03-02)

NOTE:

  • From this version, we will prefix randomly generated device-specific distinct_ids with "$device:". The prefix is applied the next time a new random ID is generated, any IDs generated by previous SDK versions and persisted on the device will continue to be used as-is until reset is called to generate a new ID. This does not change the value sent for the $device_id property, which will continue to be the randomly-generated ID without a prefix. Mixpanel's $identify endpoint has been updated to accept UUIDs with this prefix to coordinate with this change. #810

Release v7.2.2

30 Jan 23:10
Compare
Choose a tag to compare

v7.2.2 (2023-01-30)

Enhancements

  • replace original with distinct_id in alias #808