Unity Changelog
Version 4.2.3 (2023-05-18)
Bug Fixes:
- Fixed an issue with Unity-iOS Rewarded Ads hanging onto the ad instances for too long, potentially causing duplicate callback events.
Version 4.2.2 (2023-05-10)
Improvements:
- Updated AdaptersWindow.cs to utilize a more comprehensive JSON schema for better handling of network dependency changes.
Bug Fixes:
- Fixed an issue with InMobi SDK dependencies not being properly defined due to versioning differences.
Version 4.2.1 (2023-05-05)
Bug Fixes:
- Fixed an issue where package information failed to load if projects had a large amount of packages.
- Fixed an issue where main SDK dependency could not be generated through UPM implementation.
Version 4.2.0 (2023-05-04)
Added:
- Editor Window,
AdaptersWindow.cs
, for Chartboost Mediation adapters handling. For capabilities, see below:- Ad Adapters are now decoupled from the Chartboost Mediation UPM package.
- Ad Adapters can be fetched, selected, and upgraded through the new Adapters Window.
Adapters Window
can be accessed through theChartboost Mediation/Adapters
menu.- Public C# API is available to automate tasks such as upgrading, adding, loading, and saving Ad Adapter selections.
- Adapters information is automatically fetched on startup and manually through the Adapters Window.
Improvements:
- Fixed standardized error reporting of
ChartboostMediationError
components in iOS.
API Changes:
- Marked
ChartboostMediationIntegrationChecker.cs
as deprecated. Please utilizeAdaptersWindow.cs
instead.
Version 4.1.0 (2023-03-30)
Improvements:
- Simplified AppId & AppSignature accessors in
ChartboostMediationSettings
. - Added
TestMode
call toChartboostMediation.cs
. - Made Chartboost Mediation errors readable from iOS native layer to Unity.
- Refactored native bridge projects to follow rebranding and newer APIs.
- Fixed usage of placements for unsupported platforms.
- Updated documentation with AdMob and AppLovin AndroidManifest special cases.
Bug Fixes:
- Fixed placements
clearLoaded
in native implementations to return void instead of boolean. - Fixed an issue for iOS banners crashing on removal.
Version 4.0.0 (2023-03-02)
As part of the Marketing team’s efforts to clearly articulate the use cases and customers we support by being more descriptive with our product branding, Helium is being rebranded as Chartboost Mediation.
Starting in 4.0.0, the Chartboost Mediation brand will be used in place of Helium for new additions. In the coming 4.X releases, the old Helium branding will be deprecated and the new Chartboost Mediation branding will be used to give publishers a smoother transition.
Improvements:
- Revamped Helium delegates & callbacks API. (more details to come soon.)
- Added optional PostProcessor to simplify
SKAdNetwork
integration process. - Refactored Ad Placement objects so they return empty values in unsupported platforms.
- Cleanup and Refactoring of iOS Dependencies; native SDKs are now explicitly stated.
- Fixed LogError method in HeliumExternal.
- Banners
ClearLoaded
method no longer returns a boolean value. - Removed
reward
parameter from Reward callback since value was not being utilized. - Minimum iOS version changed to 12.0
Deletions:
-
Removed obsolete APIs in
HeliumSettings.cs
new accessors are available.
API Changes & Rebranding: -
New npm package distribution under
com.chartboost.mediation
-
Namespace
Helium
deprecated and replaced withChartboost
. -
HeliumIntegrationChecker
deprecated and replaced withChartboostMediationIntegration Checker
. -
HeliumError
removed and replaced with descriptivestring
values. -
HeliumBidInfo
renamed toBidInfo
-
Delegates have been renamed from
Helium
toChartboostMediation
: -
ChartboostMediationPlacementLoadEvent
added, it provides bid info on load. -
HeliumRewardEvent
converted to standardChartboostMediationPlacementEvent
. -
HeliumBidEvent
merged into Load delegate mentioned above. -
HeliumInterstitialAd
renamed toChartboostMediationInterstitialAd
-
HeliumRewardedAd
renamed toChartboostMediationRewardedAd
-
HeliumBannerAd
renamed toChartboostMediationBannerAd
-
HeliumBannerAdSize
renamed toChartboostMediationBannerAdSize
-
HeliumBannerAdScreenLocation
renamed toChartboostMediationBannerAdScreenLocation
-
HeliumSettings
renamed withChartboostMediationSettings
-
HeliumPartners
renamed toChartboostMediationPartners
For details on how to migrate from Helium 3.X to Chartboost Mediation 4.0.0, visit the corresponding documentation.
Android Migration from 3.x to 4.0.0
iOS Migration from 3.x to 4.0.0
Unity Migration from 3.x to 4.0.0
Version 3.3.2 (2023-01-26)
Bug Fixes:
- Downgraded Yahoo 1.3.0 to Verizon 1.14.0.
Version 3.3.1 (2022-12-06)
Bug Fixes:
- Updated FAN Dependency from 6.9.0 to 6.12.0
Version 3.3.0 (2022-12-01)
Improvements:
- Refactoring of HeliumSettings Scriptable Object API.
- Network Kill Switch.
- Provide a Publisher API for Partner Initialization Metrics.
Bug Fixes:
NullReferenceException
after initialization without callback subscription.- Credentials warning spamming
- Detect Misconfigured Unity setup & utility methods.
Version 3.2.0 (2022-10-20)
Improvements:
- Converted Android Java bridge to Kotlin.
Documentation:
- Improved UnityAds integration guide and requirements.
Version 3.1.0 (2022-09-15)
Improvements:
- Removed proguard for Android/Unity integration.
Bug Fixes:
- Clear Ad requests return proper clear status. Banners always return true when cleared
Version 3.0.0 (2022-08-18)
Improvements:
- Unity Package Manager distribution of the Helium SDK.
- Helium Unity APIs updated to follow Unity/C# standard coding conventions.
- Banner API updated from a load-show to a load-only paradigm.
- Helium impression events are now separate from partner network impression events.
- Sequential waterfall ad loading for all ad formats.
- Removal of UnitySendMessage callbacks for proper Native callbacks on Android & iOS
HeliumBannerAd
Show
removed. Banners are ready to show upon successful load.ReadyToShow
removed since it is no longer necessary.
HeliumSDK
DidShowBanner
callback removed since it is no longer necessary.- Added the following callbacks for when Helium determines an ad to be visible on screen.
DidRecordImpressionInterstitial
DidRecordImpressionRewarded
DidRecordImpressionBanner
Bug Fixes:
- Ad load requests to the native Helium SDKs are dispatched to a background thread.
Updated 22 days ago