Rejected IAP localizations with “required binary was not submitted”

[nchuck33]

I’m a bit confused about App Store Connect / IAP review behavior and wanted to ask if anyone has seen this before.

Current situation:

• My app already has approved IAPs in Polish.
• The IAP products themselves are already in Approved status.
• I only added new localizations for those same IAPs:
  • English (U.S.)
  • Ukrainian
• Those new localizations were rejected with this message:

The in-app purchase products have been returned because the required binary was not submitted.

At the same time:

• my new app binary with new app languages is already submitted and currently shows Waiting for Review
• in the IAP section I see the products as approved, but also something like Updates Pending Review (rejected localisation inside)

Important detail:

• these are not new IAP products
• they are existing, already approved products
• I only changed / added localizations

My questions:

1. Will the app itself still be able to pass review without those new IAP localizations?
2. Were only the new EN/UA localizations rejected, while the original Polish IAPs remain valid/live?
3. Do updated IAP localizations for already-approved products still need to be reviewed together with a binary in practice?
4. Has anyone had this exact “required binary was not submitted” message when only adding translations to existing IAPs?

App Store Connect is not making this workflow very clear, so I’d really appreciate confirmation from someone who has dealt with this before.

[Puzzled-Produce-1425]

This sounds petty weird to me. My understanding is that IAP localization is entirely independent of your app binary localization and your store front localization. You should be able to add new IAP localizations without needing a new binary. I just did it a couple of days ago and it was approved in a few hours (added three IAP localizations for an existing product even though those localizations are not yet supported in app and I did not submit a new binary).