User Profile

I am currently getting an error on the App Store Connect page that says: "These in-app purchases can’t be promoted on the App Store because your latest approved binary doesn’t include the SKPaymentTransactionObserver method." However, my latest approved binary includes that method. How is it possible that App Store Connect is saying something doesn't exist when it does exist? Is this just more of Apple anti-competitive, malicious practices or should I chalk this up to an accidental "glitch"? One has huge legal implications. For instance, one event means the App Review team can just make up whatever they want in terms of rejections on the frontend by un-hooking the backend. Then, they can modify the page. The other means the software engineers at a Fortune 50 company are trash (unlikely) or they've been hacked (more likely). I have added the photos of both my implementation and the dialog the App Store Connect is showing me. Any solution would be much appreciated.

I am getting an invalid binary when submitting my app for review. I am able to upload the build and run it as a pre-production beta on my device using TestFlight. I was under the assumption invalid binary checks were done when the app was uploaded and you would get an invalid binary for an entitlement or plist issue. However, I did not get any of these errors when uploading. I only get them when submitting to the App Store Review Team for review. My core problem is that invalid binary is nondescript and there is no way to trouble shoot this problem without knowing what exactly makes my entitlements and/or plist get flagged by production checks as invalid (binary seems entirely inaccurate here but I’ll go with it). Really, I’m not going to post my code here and it’s not an Xcode specific/versioning issue, like previous posts have mentioned. I’d really like an Apple professional to send me what I’m missing in my entitlements or plist (they do this) or a poster to tell me where I can go to determine, after an upload, where an invalid binary was flagged so I can get the error code and fix it. I’m also curious (as an aside) if Apple has the ability to reject apps for an invalid binary, bypassing the automated production checks in the backend. I’m sure Apple has the capability to give permissions to do it but I’m curious whether there is technical implementation to allow this to occur. I feel like it’s weird for me to pass checks when uploading (required to upload and TestFlight any app) and fail when going to the review team (no reason to redundantly recheck checks already completed on a local machine in Xcode and during the upload process with another re-re-check). I guess it doesn’t hurt to check your re-check and re-check your re-check but then the question becomes if this is an indication of a deeper problem with code in the backend that an engineer isn’t fixing/maintaining properly. Any information would be appreciated.