Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Voting for the Unity Awards are OPEN! We’re looking to celebrate creators across games, industry, film, and many more categories. Cast your vote now for all categories
    Dismiss Notice
  3. Dismiss Notice

[Solved] Promoted In-App Purchases & SKPaymentTransactionObserver method

Discussion in 'Unity IAP' started by PixelEnvision, Aug 24, 2018.

Thread Status:
Not open for further replies.
  1. PixelEnvision

    PixelEnvision

    Joined:
    Feb 7, 2012
    Posts:
    513
    Hello,

    I'm getting "These in-app purchases can’t be promoted on the App Store because your latest app binary doesn’t include the SKPaymentTransactionObserver method." warning in the App Store Connect.

    But I can find the method (paymentQueue:shouldAddStorePayment:forProduct:) in the code and I can also test it's working on the device with their suggested testing method (where you msg yourself a link).

    I have an open radar report which is once closed as solved, but I've re-opened as it didn't. And I've also been in touch with Apple developer support for about 10 days. Their conclusion is there something wrong with the code and I should get code level support. "It seems that the issue is related to the way your SKPaymentTransactionObserver has been implemented."

    I'm using latest LTS (2017.4.9f1) with IAP 1.20.0 + Code-less IAP + Latest non-beta Xcode.

    Any suggestions?
     
  2. ap-unity

    ap-unity

    Unity Technologies

    Joined:
    Aug 3, 2016
    Posts:
    1,519
    @PixelEnvision

    Hmm, that's not a lot of info to go off of.

    I'll let the team know and we'll look into Apple's documentation and our implementation of SKPaymentTransactionObserver.
     
  3. PixelEnvision

    PixelEnvision

    Joined:
    Feb 7, 2012
    Posts:
    513
    @ap-unity

    Thank you, that would be great. I still don't think that's code related as it looks correct but it would nice to have some verification from the team.

    I agree they didn't give much to go off after 10 days and many email/screenshot/video exchanges. :(

    Anyway, I've used one of my Code-Level Support TSIs for this. I'll post the any info/suggestion/solution I'll receive from them.
     
  4. PixelEnvision

    PixelEnvision

    Joined:
    Feb 7, 2012
    Posts:
    513
    I haven't heard from the code-level support yet but my app was reviewed & approved last night and that warning is gone now. I guess that also means there was nothing wrong with the code but the issue was on App Store Connect.

    There is a chance that code check wasn't done until it's gone thru review, so for future reference I would suggest waiting until app review before trying to get this fixed by radar & developer support.
     
    brandonholt95 likes this.
Thread Status:
Not open for further replies.