Skip to content

[in_app_purchase][iOS] Implement StoreKit2 Product.SubscriptionInfo.isEligibleForIntroOffer property #164382

Closed as duplicate

Description

@jvdberg08

Use case

I would like to be able to tell whether or not I should show the introductory offer of a given product, without having to query my backend for existing purchases and without having to somehow get all receipts/transactions and deducing intro offer eligibility from that.

Proposal

I would like to have either the property be added, or the static function (or both).

Note that during my research of this property, it seems to return true even when the subscription has no introductory offer, so for users who have one subscription with and one without an introductory offer, determining whether or not to show it also requires #161393 to be implemented (I think). For me personally this isn't that interesting, as all my subscription products have the same free-trial offer.

Couldn't find a similar issue, but this is obviously related to #157558 as it's entirely related to StoreKit2.

Activity

  1. added
    in triagePresently being triaged by the triage team
    on Mar 3, 2025
  2. huycozy commented on Mar 3, 2025

    @huycozy
    Member

    #161393 might be related, and I think we could also concentrate on #116383 (see #116383 (comment)), couldn't we?

  3. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Mar 3, 2025
  4. jvdberg08 commented on Mar 10, 2025

    @jvdberg08
    Author

    Yes, #161393 is related, as is the comment #116383 (comment) you mentioned (it's the exact same as this issue, I saw it before but figured I'd make an issue for it, hope that's not a problem)

  5. removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Mar 10, 2025
  6. huycozy commented on Mar 11, 2025

    @huycozy
    Member

    Thanks for your response. Marking this as a duplicate of that one. Please follow it for updates.

  7. added
    r: duplicateIssue is closed as a duplicate of an existing issue
    and removed
    in triagePresently being triaged by the triage team
    on Mar 11, 2025
  8. maRci002 commented on Mar 11, 2025

    @maRci002
    Contributor

    I think this issue should be mentioned in the umbrella issue otherwise, it might not be implemented.

  9. huycozy commented on Mar 11, 2025

    @huycozy
    Member

    @maRci002 Please add a comment there so PIC(person in charge) may be aware of this.

  10. github-actions commented on Mar 25, 2025

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  11. locked as resolved and limited conversation to collaborators on Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    r: duplicateIssue is closed as a duplicate of an existing issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions