Receipt verification on my app's server suddenly started giving an error, and all billing-related processes became errors. The error that is occurring is Signature verification failed　is.(FireBaseJWT throw Exception) The code is below, but it was working fine until 3 days ago. JWT::decode($lastTransaction['signedTransactionInfo'], $appleCertificate, ['ES256']); The certificate used here was created by the server developer, so I don't know how to create it. Could you please help me which certificate should I use? I tried using the ApplePKI certificate, but the same error occurred. 私のアプリのサーバでのレシート検証が突然エラーを吐くようになり、課金関連の処理が全てエラーになってしまいました。 発生しているエラーはSignature verification failedです。(FireBaseJWTのException) コードは以下になっていますが、3日前までは正常に動作していたコードです。 JWT::decode($lastTransaction['signedTransactionInfo'], $appleCertificate, ['ES256']); ここで利用している証明書はサーバ開発者に作成して貰っていたので作成方法が分かりません。 どの証明書を使えば良いか助けて貰えないでしょうか。 ApplePKIの証明書は粗方試してみましたが同様のエラーになっています。

Have been trying to Download iOS 17.0 Simulator for the last six hours. Using Activity Monitor to determine the speed to the Download. One time, Downloads window indicated 99% had been reached. It appears the Apple server connection may be unreliable? So what would be your User Experience?

Hi, our App client now uses the StoreKit Original API to implement In-App Purchase. Now we want to upgrade to using StoreKit 2 for iOS15 and above. Here's our plan: For clients running iOS versions lower than 15, we intend to continue using the transactionReceipt interface.To reduce the workload, we plan to skip the version of getting receipts using appStoreReceiptURL. Clients using iOS 15 and newer versions will employ StoreKit 2's interfaces to get transactions. The client sends receipts or transactions to the backend, where the backend use the transaction info API to verify the transactions. I would like to inquire if this approach seems reasonable.And if there's a possibility that the transactionReceipt function within the StoreKit Original API could become entirely unusable in the next two to three years (for example, the transactionReceipt interface call fails or returns null).

Hi, I’m investigating switching from the /verifyReceipt endpoint to the App Store Server API. I’ve noticed that some transaction IDs we have in our system return 4040001 (AccountNotFound) from the “Get All Subscription Statuses” endpoint. These transaction IDs are associated with receipts that used to verify OK with the /verifyReceipt endpoint, but now return 21010 (receipt unauthorized). Under what circumstances do transactions which used to be valid start returning “account not found”?

Currently, my app validates App Store receipts on the device, so as per this news, I need to make changes to it, But I am unable to make a decision on where I should start, Can anyone please help me out on this? Do I need to make changes in the device receipt validation? If yes, what steps should I take? OR Should I do the receipt validation from the server side? If yes, then what steps to follow to make a receipt validation on the server? Your suggestions will be highly appreciated.