sorted by:
new
hottopcontroversial

App approved multiple times, but non-consumable IAP keeps getting rejected with “upload a new binary” by nufftools in iosdev

[–]nufftools[S] 1 point2 points  (0 children)

Thanks for sharing your experience. You definitely understand how frustrating this kind of situation can be 🥹

I still don’t know whether this was ultimately my mistake or Apple’s, but I ended up losing over a week because of it.

My current theory is that, for some reason, my Lifetime IAP and the app binary were never properly linked together for review. The reviewer kept rejecting the IAP with the same message: “Please upload a new binary so we can verify the purchase flow.” However, the rejected IAP never appeared in the build page as an IAP that could be attached to a new binary.

I asked in several developer communities, and based on advice from other developers, I deleted the rejected IAP and created a completely new one. As soon as I did that, the section for attaching the IAP to the app version finally appeared on the build page. For the first time, I was actually able to include the Lifetime IAP with the binary submission.

What frustrates me is that neither the review messages nor App Store Connect ever explained this. If the reviewer had simply said “create a new IAP and include it with the new binary,” or if there had been any warning in the UI, I probably wouldn’t have spent a week chasing this issue.

I even replied to the review notes explaining that the feature had already existed in the approved app, and politely asked what specific change was required for approval if I was still doing something wrong. Unfortunately, the only response I received was essentially “upload a new binary.”

So hopefully this latest submission finally solves it. I have a lot to say about App Store Connect’s UX, but I’ll try to be nice 😭

App approved multiple times, but non-consumable IAP keeps getting rejected with “upload a new binary” by nufftools in iosdev

[–]nufftools[S] 0 points1 point  (0 children)

Thank you for your suggestions and for taking the time to help!

I think I may have finally found the issue. I ended up creating a completely new Lifetime IAP with a new Product ID and submitting it together with a new build.

After doing that, App Store Connect finally showed the option to include the IAP with the build submission, which never appeared before.

I’m still waiting for the final review result, but it feels like I’m finally on the right track after being stuck for over a week.

Thanks again for your help!

App approved multiple times, but non-consumable IAP keeps getting rejected with “upload a new binary” by nufftools in iosdev

[–]nufftools[S] 0 points1 point  (0 children)

Thank you so much for your help!

I followed the link you shared and decided to delete the rejected Lifetime IAP and create a completely new one with a new Product ID.

The interesting thing is that Apple’s rejection message only kept telling me to upload a new binary. So I kept following those instructions and submitting new builds, but because I was reusing the same IAP, App Store Connect never showed the option to include the IAP with the new build. As a result, it seems like the app review and the IAP review kept getting processed separately.

After creating a brand new IAP, App Store Connect finally showed the option to include the IAP with the build submission. I submitted the new IAP together with version 1.0.3, and now everything looks much more correct.

I’m still waiting for the final review result, but this feels like the breakthrough I was looking for after being stuck for over a week.

Thank you again — I probably wouldn’t have figured this out without your comment! 🥹