Yeah, a 1-3 day response period is not normal. That's just one Apple employee being obstinate - per usual - as one review is assigned per Application Submission. Apple reviewers, who are not being ultra-passive aggressive, respond almost immediately during business hours, even when backlogged. An in-app purchase that has a problem in the system is a front-end problem where the back-end data is not being loaded correctly. This means Apple's App Store Connect website is in need of a technical fix. Patience won't do a lick of good. Stop posting in threads to annoy people with your pseudo-knowledge. It causes a lot of problems for people looking for actual solutions to their issues.

Do you really think a Fortune 50 company engineered their servers so poorly that a holiday would slow down their backend? Where can I get the delusional pills you are on?

Seriously, get off this forum. The idea that the "backend is slow" is absolutely ludicrous. Giving people bad advice - without technical merit - is worse than giving people no advice at all.

This accepted answer is incorrect. You do not need to wait 24-48 hours. The system is instantaneous to when the application is published on the store. If it's in the backend, it's in the backend. Period. If its not, well, you need to wait for it to be in the backend. Once approved, it gets automatically added to the backend. The problem is that the App Store Connect website does not always list the in-app purchases to add to a particular App Store version that is to be submitted. This is a problem with engineers simply removing the section where you can click the checkbox. Why do they do this? No idea. Its honestly bonkers. The other problem is that when an in-app purchase is submitted for review, and gets returned to you for "correction", it is impossible to re-submit it back to the store because there is no way to fix the corrections and the newly submitted version won't update to re-send the in-app purchases with the current app version you want to be submitted. This is a technical problem on Apple's side. The only way to fix it is for Apple to go in their and manually fix it. This has been a problem for a very long time apparently. No idea how Apple is allowed to continue to use this system and hasn't been hit with a class action law suit. Undue delays are authorized damages in a court of law.

This is a development issue on Apple's end. Hence, I am posting in the developer forums. The goal is to get Apple to fix their system checking so it includes the same system checks when submitting an app to the App Store Review team as it does when you upload a binary from Xcode to TestFlight. This seems like an obvious measure honestly. Also, a plist and/or entitlement issue is a development issue and not an App Store Connect problem, as it invalidates the entire binary. You might have had an argument that it wasn't if you could modify the entitlements after submission (which makes more sense) but because they are included as esoteric code in the code itself, you don't really have an argument. Also, this post was to verify that other posts which state deleting Xcode and reinstalling it was a time-consuming solution and not really a solution at all.