I can't get IAP - only subscriptions

I have the problem that I can’t get a product that is configured as non-consumable IAP in App Store Connect. I don’t have any issues with getting the subscription products though.

The error is “Could not find products with identifiers: f“lifetime_2499”]. There is a problem with your configuration in App Store Connect.”

My process for setting up the IAP is the same as for the subscription products. And since that works it is not an issue with the Paid Apps agreement (?).

Status is “Ready for submit” which is the same for the subscription products.

I am using Capacitor and the unofficial @capgo/capacitor-purchases plugin.

Any ideas what I might be missing? I am testing on a real device.

Page 1 / 1

Same issue on Testflight and debug mode with the flutter sdk, subscriptions are being found, but not IAPs:

>Purchases] - DEBUG: No existing products cached, starting store products request for: f"marker_test_EFaywnx"]

pDefault] uStoreKit] Did not receive any products or error for products request.

pPurchases] - DEBUG: Store products request request received response

Same issue on Testflight and debug mode with the flutter sdk, subscriptions are being found, but not IAPs:

>Purchases] - DEBUG: No existing products cached, starting store products request for: f"marker_test_EFaywnx"]

>Default] uStoreKit] Did not receive any products or error for products request.

>Purchases] - DEBUG: Store products request request received response

Might be a general issue?? no idea

Yes, I think so: https://developer.apple.com/forums/thread/726252

Hi @Paul Janns, @skuske , and @Ole Nirwing,

Thanks for bringing this to our attention! If you all have enabled the new Apple base price functionality , we are trying to get more information to compile and give back to Apple so they can look more into this issue as well.

Can you please send to support@revenuecat.com the following: (if you haven’t already - @skuske I believe you already have a ticket with us)

Product ID/ID#
Original price
Date-time changed
Scope of price change (countries/new price)
The date-time response became nil
sysdiagnose logs

Thank you for your help! Let me know if you have any questions. In the meantime, if it’s not possible to revert back the pricing change, it seems like this may be working fine with USD, so that could be worth trying as well.

@kaitlin

I had provided everything but the sysdiagnose, which I have just send to Michael. Hope that helps. :)

It looks like the issue has been fixed. Products are delivered in Sandbox again here…

For me as well, but now I get a different error

2023-03-17 10:06:40.328698+0100 App[28798:5939585] <SKPaymentQueue: 0x282948150>: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3502 "Dieser Artikel ist nicht verfügbar." UserInfo={storefront-country-code=DEU, client-environment-type=Sandbox, AMSServerErrorCode=3502, NSLocalizedDescription=Dieser Artikel ist nicht verfügbar.}

basically saying this product is not available. There is also a recent Apple Dev forum post about that

https://developer.apple.com/forums/thread/726675

Full log:

2023-03-17 10:06:38.494598+0100 App028798:5939584] 9Purchases] - DEBUG: Vending Offerings from cache

2023-03-17 10:06:38.499266+0100 App628798:5939015] :Purchases] - INFO: Purchasing Product 'lifetime_pro_2499' from package in Offering 'pro life'

2023-03-17 10:06:38.500721+0100 App028798:5939585] 7Purchases] - DEBUG: StoreKit1Wrapper (0x0000000280f58360) updatedTransaction: lifetime_pro_2499 0

2023-03-17 10:06:38.501087+0100 App828798:5939585] pPurchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction date - this is an issue with the App Store. Unix Epoch will be used instead.

Transactions in the backend and in webhooks are unaffected and will have the correct timestamps. This is a bug in StoreKit 1. To prevent running into this issue on devices running iOS 15+, watchOS 8+, macOS 12+, and tvOS 15+, make sure `usesStoreKit2IfAvailable` is set to true when calling `configure`.

2023-03-17 10:06:38.501319+0100 App 28798:5939585] +Purchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction identifier - this is an issue with the App Store. Transactions in the backend and in webhooks are unaffected and will have the correct identifier. This is a bug in StoreKit 1. To prevent running into this issue on devices running iOS 15+, watchOS 8+, macOS 12+, and tvOS 15+, make sure `usesStoreKit2IfAvailable` is set to true when calling `configure`.

2023-03-17 10:06:40.328698+0100 App328798:5939585] <SKPaymentQueue: 0x282948150>: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3502 "Dieser Artikel ist nicht verfügbar." UserInfo={storefront-country-code=DEU, client-environment-type=Sandbox, AMSServerErrorCode=3502, NSLocalizedDescription=Dieser Artikel ist nicht verfügbar.}

2023-03-17 10:06:40.336805+0100 App028798:5939585] 4Purchases] - DEBUG: StoreKit1Wrapper (0x0000000280f58360) updatedTransaction: lifetime_pro_2499 (An unknown error occurred) 2

2023-03-17 10:06:40.336986+0100 Appn28798:5939585] :Purchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction date - this is an issue with the App Store. Unix Epoch will be used instead.

2023-03-17 10:06:40.337087+0100 App<28798:5939585] 0Purchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction identifier - this is an issue with the App Store. Transactions in the backend and in webhooks are unaffected and will have the correct identifier. This is a bug in StoreKit 1. To prevent running into this issue on devices running iOS 15+, watchOS 8+, macOS 12+, and tvOS 15+, make sure `usesStoreKit2IfAvailable` is set to true when calling `configure`.

2023-03-17 10:06:40.337183+0100 Appn28798:5939585] gPurchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction date - this is an issue with the App Store. Unix Epoch will be used instead.

2023-03-17 10:06:40.337269+0100 App`28798:5939585] pPurchases] - WARN: There is a problem with the SKPaymentTransaction missing a transaction identifier - this is an issue with the App Store. Transactions in the backend and in webhooks are unaffected and will have the correct identifier. This is a bug in StoreKit 1. To prevent running into this issue on devices running iOS 15+, watchOS 8+, macOS 12+, and tvOS 15+, make sure `usesStoreKit2IfAvailable` is set to true when calling `configure`.

2023-03-17 10:06:40.341735+0100 Appn28798:5939585] gPurchases] - ERROR: There was a problem with the App Store.

2023-03-17 10:06:40.342066+0100 Apph28798:5939585] Finishing transaction '96086D99-FBBC-4549-8F67-E7E0CF1C5966' for product 'lifetime_pro_2499'

2023-03-17 10:06:40.349256+0100 App'28798:5939015] 9Purchases] - ERROR: Product purchase for 'lifetime_pro_2499' failed with error: Error Domain=RevenueCat.ErrorCode Code=2 "There was a problem with the App Store." UserInfo={NSUnderlyingError=0x28251ff00 {Error Domain=SKErrorDomain Code=0 "An unknown error occurred" UserInfo={NSLocalizedDescription=An unknown error occurred, NSUnderlyingError=0x28251fbd0 {Error Domain=ASDServerErrorDomain Code=3502 "Dieser Artikel ist nicht verfügbar." UserInfo={NSLocalizedDescription=Dieser Artikel ist nicht verfügbar.}}}}, readable_error_code=STORE_PROBLEM, source_function=asPurchasesError, source_file=RevenueCat/SKError+Extensions.swift:64, NSLocalizedDescription=There was a problem with the App Store.}

ERROR MESSAGE: {"message":"Restore failed","errorMessage":"Restore failed"}

2023-03-17 10:06:40.350550+0100 Appe28798:5939585] Purchases] - DEBUG: StoreKit1Wrapper (0x0000000280f58360) removedTransaction: lifetime_pro_2499 (An unknown error occurred) "NSLocalizedDescription": An unknown error occurred, "NSUnderlyingError": Error Domain=ASDServerErrorDomain Code=3502 "Dieser Artikel ist nicht verfügbar." UserInfo={NSLocalizedDescription=Dieser Artikel ist nicht verfügbar.}] 2

Serror] - {"message":"Restore failed","errorMessage":"Restore failed"}

rerror] - listenBuy error {"errorMessage":"Restore failed"}

Yes, indeed. It now produced the error mentioned. One week passed without a fix. What a shame.

One ‘solution’ is just found is to create a sandbox account for the country you set your base price for. I set it for US and now created a new sandbox account for US and then it worked like a charm.

So the base price functionality seems to be buggy. But this at least allows me to test

I’m having the same issue. I’m able to get subscriptions but not IAP. Its been 3 days since IAP approved but not able to fetch it.

Reply

Sign up

‏‏‎ ‎

Log in to the Community

‏‏‎ ‎

Scanning file for viruses.

This file cannot be downloaded