Post not yet marked as solved
I have the same problem, and it happens in the production environment. If I change to storekit v1 to initiate the purchase, I can successfully call the payment pop-up window，This problem only occurs in storekit v2
Post not yet marked as solved
This problem is so obvious that many people encounter it. Can't Apple be seen? It's very frustrating
Post not yet marked as solved
I have the same problem,
I just submitted a report: FB11729666
Post not yet marked as solved
I have the same problem
:status: 500
content-length: 0
date: Sat, 25 Dec 2021 05:55:05 GMT
set-cookie: dqsid=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE2NDA0MTEzOTksImp0aSI6Iloza0htM3pKbjNPVzJFeVpmSVlpd1EifQ.vsHqu0ubLPjSmGSV1mYsWj3Jw_szTv-zLQH1iW7BVng; Max-Age=1800; Expires=Sat, 25 Dec 2021 06:25:04 GMT; Path=/; Secure; HTTPOnly
access-control-allow-credentials: true
access-control-allow-origin: https://appstoreconnect.apple.com
access-control-expose-headers: ETag
x-b3-traceid: b7b5752d682d3994
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
x-apple-jingle-correlation-key: ZERDVHGSF4QEWR77LIJEFP7X5Q
x-daiquiri-instance: daiquiri:13851002:mr22p00it-ztbu07032101:7987:21RELEASE200:daiquiri-amp-dsce-asc-int-001-mr
x-content-security-policy: script-src 'self' *.apple.com
x-daiquiri-instance: daiquiri:18493001:mr85p00it-hyhk03154801:7987:21RELEASE200:daiquiri-amp-all-shared-ext-001-mr
x-qtl-request-id: d5f3da5bcce0fcebfc79111799955a74
x-via: 2.0 as-cn-gdfscm5-cache-0005 [500]
server: QTL_Cache/1.2.09
Post not yet marked as solved
Why no reply, Where are the Apple source control engineers?
I use the same workflow. This workflow should be very common. At present, Xcode does not support it?
Post not yet marked as solved
@logicat I have the same problem as you. Have you found the reason
