“missing package product”

@Nenad0909 The subscriptions currently show ‘Waiting for Review.’ The Waiting for Review status indicates you have already submitted your In-App Purchase to be reviewed by Apple. You can make edits to the product while it is in this status.

I have created a Feedback Assistant for this: https://feedbackassistant.apple.com/feedback/22266931 Prefect, thank you. Also created a Code-Level Support case, with the same title as with Feedback Assistant but it seems to be private. Yep. I've replied to that with a summary of the situation as well. Please inform if I may have missed anything. Everything looks good to me. At this point, I think you should ignore the issue and proceed with development. This warning won't have any effect on the certification process. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Hello - In reviewing your account, it appears that you were able to successfully resubmit your IAP product on March 16, 2026 with an app update - and both the app update and IAP product are now approved and live in the App Store. Please let us know if you need any further assistance. Thank you.

Hello - In order to resubmit your three IAP subscription products, the status of each needs to change from Developer Action Needed to Ready to Submit. We recommend editing each of them, in order to save an update (e.g.: add a note to the Review Notes section like [Date] Updating IAP to resubmit with new binary of Version 1.x of [App Name]. Once the status of the IAPs has been successfully updated, proceed to submit a new version of the app - and attach the three IAPs for review as documented here under Submit an In-App Purchase of the first time. If you are still unable to resubmit the IAPs with a new app build, please file a detailed ticket (including screenshots and/or video) via Feedback Assistant, and reply back to this thread with that ticket number - and we will follow-up. Thank you.

Hello - In reviewing your account, it appears that the required Paid Apps Agreement has not been signed and is not yet in the Active state. Because of this, your In-App Purchase product is not available for testing in Sandbox during App Review. Please direct the Account Holder to accept the Paid Apps Agreement, complete both the Banking and Tax information, and ensure the status of this agreement is updated to ACTIVE. We also recommend completing a successful Sandbox purchase in your app before you resubmit for App Review. Please let us know if you have any additional questions or need further assistance. Thank you.

Regarding Programs can’t authenticate themselves. I don't try to authenticate my own executable, I am trying to verify a helper binary/dylib inside my product that can be updated separately from the main binary. Before running/dlopening it, I would like to ensure: Test 1) The signature chain of the executable/dylib leads to the apple root. Test 2) The leaf certificate team-id is my team-id. Per my understanding this will ensure that this executable/binary was signed by me. If anyone else has a valid certificate(it can pass Test 1) but it will fail the Test 2 as its team ID will be different. If someone crafts a rogue certificate in order to pass Test 2 then this rogue certificate is not signed by apple and therefore will fail Test 1. Please advise if you see any problem with this approach. Now to my main question: When I try to extract the team id from the executable/dylib using SecCodeCopySigningInformation, I see some posts claim that if that executable is not signed by apple root chain team-id wil

Yes, both are signed Executable=/Users/alexf/Library/Developer/Xcode/DerivedData/Passthrough-fmtxodvbsknmqegwvscnzsczlopk/Build/Products/Debug/PassthroughAppEx.appex/Contents/MacOS/PassthroughAppEx Identifier=com.example.apple-samplecode.PassthroughXXXXXXXX.AppEx Format=bundle with Mach-O thin (arm64) CodeDirectory v=20400 size=476 flags=0x0(none) hashes=3+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=9abcde7d8b79d23164600c46c55cdace7136690a CandidateCDHashFull sha256=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 Hash choices=sha256 CMSDigest=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 CMSDigestType=2 CDHash=9abcde7d8b79d23164600c46c55cdace7136690a Signature size=4781 Authority=XXXXXXXXXXXXX Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Signed Time=17 Mar 2026 at 15:00:17 Info.plist entries=21 TeamIdentifier=XXXXXXXX Sealed Resources version=2 rules=13 files=3 Internal requirements count=1 si

The PPQ outage from last week [1] was a very specific thing and it’s definitely not related to whatever issue you’re hitting now. [quote='819180021, KW-P, /thread/819180, /profile/KW-P'] Ping still fails [/quote] Testing with ping isn’t helpful in this case; AFAICT ppq.apple.com never responds to pings. Consider: % ping ppq.apple.com PING use1-ppq-ext-prod.sbz.apple.com (17.33.200.235): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 ^C --- use1-ppq-ext-prod.sbz.apple.com ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss % curl -I http://ppq.apple.com HTTP/1.1 301 Moved Permanently … Location: https://ppq-ext.v.aaplimg.com/ If you want to try out the redirect link, you have disable the client’s trust evaluation on the server: % curl -I https://ppq-ext.v.aaplimg.com/ curl: (60) SSL: no alternative certificate subject name matches target host name 'ppq-ext.v.aaplimg.com' … % curl -I --insecure https://ppq-ext.v.aaplimg.com/ HTTP/2 404 … Of cou