Make CustomerInfo allPurchaseDates values nullable
#989
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
joshdholtz
approved these changes
Feb 22, 2024
tonidero
deleted the
make-customer-info-purchase-dates-values-nullable
branch
tonidero
pushed a commit
that referenced
this pull request
Feb 29, 2024
**This is an automatic release.** ### Bugfixes * Make `CustomerInfo` `allPurchaseDates` values nullable (#989) via Toni Rico (@tonidero) ### Dependency Updates * [AUTOMATIC BUMP] Updates purchases-hybrid-common to 9.8.0 (#990) via RevenueCat Git Bot (@RCGitBot) * [Android 7.6.0](https://github.com/RevenueCat/purchases-android/releases/tag/7.6.0) * [iOS 4.37.0](https://github.com/RevenueCat/purchases-ios/releases/tag/4.37.0)
Jethro87
pushed a commit
to Jethro87/purchases-flutter
that referenced
this pull request
Jan 4, 2025
This property can have nullable values in the native SDKs, but it was not nullable in flutter. This supports it being nullable. If you use the `allPurchaseDates` property from `CustomerInfo`, you will need to handle nullable values with this change. This should fix: RevenueCat#988
Jethro87
pushed a commit
to Jethro87/purchases-flutter
that referenced
this pull request
Jan 4, 2025
**This is an automatic release.** ### Bugfixes * Make `CustomerInfo` `allPurchaseDates` values nullable (RevenueCat#989) via Toni Rico (@tonidero) ### Dependency Updates * [AUTOMATIC BUMP] Updates purchases-hybrid-common to 9.8.0 (RevenueCat#990) via RevenueCat Git Bot (@RCGitBot) * [Android 7.6.0](https://github.com/RevenueCat/purchases-android/releases/tag/7.6.0) * [iOS 4.37.0](https://github.com/RevenueCat/purchases-ios/releases/tag/4.37.0)
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.
This property can have nullable values in the native SDKs, but it was not nullable in flutter. This supports it being nullable.
If you use the
allPurchaseDatesproperty fromCustomerInfo, you will need to handle nullable values with this change.This should fix: #988