Add missing IntroEligibilityStatusNoIntroOfferExists
#335
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NachoSoto
force-pushed
the
nacho/sdk-3269-unity-fix-introeligibilitynointroofferexists-compatibility
branch
from
dfa7d61 to
aedc3ad
Compare
tonidero
approved these changes
Oct 3, 2023
NachoSoto
deleted the
nacho/sdk-3269-unity-fix-introeligibilitynointroofferexists-compatibility
branch
Merged
MarkVillacampa
added a commit
that referenced
this pull request
Oct 5, 2023
**RevenueCat Unity SDK v6** is here!! 😻 This latest release updates the SDK to use BillingClient 6 in Android. This version of BillingClient brings little change compared with BillingClient 5 which brought an entire new subscription model which resulted in large changes across the entire SDK. The only modification at the API level involves replacing "ProrationMode" with "ReplacementMode". The specific replacement modes remain unchanged. If your app doesn't currently use DEFERRED replacement modes, then you should be safe to upgrade to this version without changes in behavior. If your app supports product changes using [DEFERRED replacement mode](https://www.revenuecat.com/docs/managing-subscriptions#google-play), then you can either stick with the previous major version until support for DEFERRED is re-introduced in this major version, or you can remove DEFERRED replacement options from your app. If you are using the SDK in observer mode, you should only use v7 in Android if you're using BillingClient 6. See the [Android Native - 6.x to 7.x Migration](https://github.com/RevenueCat/purchases-android/blob/main/migrations/v7-MIGRATION.md) for more details. If you come from an older version of the RevenueCat SDK, see [Android Native - 5.x to 6.x Migration](https://www.revenuecat.com/docs/android-native-5x-to-6x-migration) for a more thorough explanation of the new Google subscription model announced with BillingClient 5 and how to take advantage of it. ### Bumped minimum Android SDK version RevenueCat SDK v7 bumps minimum Android SDK version from Android 4.0 (API level 16) to Android 4.4 (API level 19). ### Support for InApp Messages We've added new APIs to support InApp messages both in Android and iOS. You can read more about: * [Google Play InApp Messages](https://rev.cat/googleplayinappmessaging) which will show users a snackbar message during grace period and account hold once per day and provide them an opportunity to fix their payment without leaving the app. * [App Store InApp messages](https://rev.cat/storekit-message) which will show a modal during grace period once per subscription. InApp Messages are shown by default in both platforms. If you want to disable this behaviour during configuration of the RevenueCat SDK, setup the `shouldShowInAppMessagesAutomatically` property during configuration to `false`: ```c# Purchases.PurchasesConfiguration.Builder builder = Purchases.PurchasesConfiguration.Builder.Init("api_key"); Purchases.PurchasesConfiguration purchasesConfiguration = builder.SetShouldShowInAppMessagesAutomatically(false) .Build(); purchases.Configure(purchasesConfiguration); ``` ### New Features * Add missing `IntroEligibilityStatusNoIntroOfferExists` (#335) via NachoSoto (@NachoSoto) ### Dependency Updates * [AUTOMATIC BUMP] Updates purchases-hybrid-common to 7.0.0 (#336) via RevenueCat Git Bot (@RCGitBot) * [Android 7.0.0](https://github.com/RevenueCat/purchases-android/releases/tag/7.0.0) * [iOS 4.27.0](https://github.com/RevenueCat/purchases-ios/releases/tag/4.27.0) * [iOS 4.26.2](https://github.com/RevenueCat/purchases-ios/releases/tag/4.26.2)
aboedo
pushed a commit
that referenced
this pull request
Oct 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.