Skip to main content
Solved

App not found error 4040003

M
Forum|alt.badge.img+3

While in the process of setup.. 

 

Error enumerating unfinished transactions for first transaction listener: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x28114e0d0 {Error Domain=AMSErrorDomain Code=301 "Invalid Status Code" UserInfo={NSLocalizedDescription=Invalid Status Code, AMSURL=https://mzstorekit-sb.itunes.apple.com/inApps/v1/history?REDACTED, AMSStatusCode=404, AMSServerPayload={

    errorCode = 4040003;

    errorMessage = "App not found.";

    okButtonString = OK;

}, NSLocalizedFailureReason=The response has an invalid status code}}, storefront-country-code=PRT, client-environment-type=Sandbox}

 

 

After this error the following shows up:

 

🍎‼️ Error fetching offerings - Não foi possível concluir a operação. (RevenueCat.OfferingsManager.Error, erro 1.)

There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). 

More information: https://rev.cat/why-are-offerings-empty

 

Do I need to select any StoreKit configuration in Scheme Options?  (None is selected) 

 

 

 

Latest SDK version 

App is in 1.0 Prepare for Submission

Subscriptions are in Ready to Submit. Localization is in Prepare for Submission (why?)

 

 

Best answer by MarkS

This error appears if your app bundle ID does not match the one in App Store Connect

View original
Did this post help you find an answer to your question?

5 replies

M
Forum|alt.badge.img+3
  • MarkS
  • Author
  • Helper
  • 3 replies
  • October 3, 2023

Testing on device 

Sandbox account active

M
Forum|alt.badge.img+3
  • MarkS
  • Author
  • Helper
  • 3 replies
  • Answer
  • October 3, 2023

This error appears if your app bundle ID does not match the one in App Store Connect

M
Forum|alt.badge.img+3
  • matthew-p
  • Helper
  • 3 replies
  • November 22, 2023

The same error. But I checked bundle ID a few times. They are identical.

 

Error enumerating unfinished transactions for first transaction listener: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x280f037e0 {Error Domain=AMSErrorDomain Code=301 "Invalid Status Code" UserInfo={NSLocalizedDescription=Invalid Status Code, AMSURL=https://mzstorekit-sb.itunes.apple.com/inApps/v1/history?REDACTED, AMSStatusCode=404, AMSServerPayload={
    errorCode = 4040004;
    errorMessage = "App not found. Please try again.";
    okButtonString = OK;
}, NSLocalizedFailureReason=The response has an invalid status code}}, storefront-country-code=POL, client-environment-type=Sandbox}

I successfully receive all subscriptions with prices. But the purchase is not successful.

 

 

M
Forum|alt.badge.img+3
  • matthew-p
  • Helper
  • 3 replies
  • November 23, 2023
matthew-p wrote:

The same error. But I checked bundle ID a few times. They are identical.

 

Error enumerating unfinished transactions for first transaction listener: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x280f037e0 {Error Domain=AMSErrorDomain Code=301 "Invalid Status Code" UserInfo={NSLocalizedDescription=Invalid Status Code, AMSURL=https://mzstorekit-sb.itunes.apple.com/inApps/v1/history?REDACTED, AMSStatusCode=404, AMSServerPayload={
    errorCode = 4040004;
    errorMessage = "App not found. Please try again.";
    okButtonString = OK;
}, NSLocalizedFailureReason=The response has an invalid status code}}, storefront-country-code=POL, client-environment-type=Sandbox}

I successfully receive all subscriptions with prices. But the purchase is not successful.

 

 

Ok. Related: https://status.revenuecat.com/incidents/bc051fmc44gg

R
Forum|alt.badge.img
  • Rechard
  • New Member
  • 2 replies
  • November 26, 2023

the same error

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings