Thanks for sharing the info.
Do you mean you had a rejected app validated just by changing the build settings ?
If so, it could be a nice workaround waiting for the fix 
Thanks for the follow up.
I thought too it might not be related to other IAP stores being included
(especially with āsupportedPlatforms = { android=true }ā defined).
HopeĀ Engineering will have some insight on this.
PS: still waiting for a reply from Apple on my sideā¦
Apple seems to have issues. This is impacting many native developers too:
https://forums.developer.apple.com/thread/78759
And Apple isnāt being very responsive about it.
Rob
What theā¦?
This looks bad!
@GoG,
No. I have a planned āsubmitā at the end of this week. To avoid getting a rejection, I split my build.settings. However, it seems i have mis-understood @rob. I thought he said we should have a separate build.settings for each platform but according to 4 posts up it doesnāt matter.
Thanks for the confirmation.
Unfortunately, it might not make any difference indeed.
This does look badā¦ So it was an issue with Apple review process in the end.
According to the forum, it has been around since early June and still no answer.
Itās still weird that previous version of our apps get validated (week ago) and then abruptly denied.
Just out of curiosity, do you use the Appodeal plugin too ?
As it includes a lot of other ad provider SDK, maybe some of the
code is what triggers Apple bot rejection claim.
No, we just use the basic Corona features and the only active plugin is Flurry analytics.
Thanks for your answer.
Might come from something else thenā¦
Just read another forum post:
https://forums.developer.apple.com/thread/73244
I use collectible coins in my game to unlock harder levels but they canāt be bought.
I know a lot of game that do just that without issue (it even was present in my previously validated versions).
Do you have similar mechanics in yours ? Do you think it can be whatās triggering Apple rejection ?
Thanks
The only thing we did change is the following:
we have defined a string for showing the inapp price in case the price can not be loaded from the store. In this case the predefined hardcoded string is shown. For example:
Someone opens the shop to purchase products, but internet is not available and the correct price can not be loaded from the product onlineā¦ in this case we show ā0.99$ā as a hardcoded string.
If the store can be reached the correct string (price) is loaded and then shows: ā$0.99ā or the price based on the country the product is purchased in.
Maybe itās the āhardcodedā value!?
Iām starting to suspect my ācollect coins to unlock levelsā feature to be the source of the rejection as,
according to Apple guidelines:
3.1.1 In-App Purchase:
- If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may use in-app purchase currencies to enable customers to ātipā digital content providers in the app. Apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.
Ā
Maybe the last iOS reviewer read that quite strictly (compare to previous ones validation my app).
Ā
@d.mach, do you have a similar feature that could explain the rejection too ?
Itās not āanother payment methodā but maybe Apple would disagree hereā¦
Ā
PS: I sent another message to the reviewer, still waitingā¦
Just to be clear, there is ZERO reason to have multiple build.settings files 99.9% of the time. The build.settings file has blocks that are OS specific and if youāre building for iOS, the Android stuff is ignored.Ā For plugins, even if you donāt use āsupportedPlatformsā, we canāt link Android libraries to an iOS build anyway. Only in a couple of odd cases is āsupportedPlatformsā even needed.
In other words, there is no way Apple is seeing any āGoogleā code in our builds.Ā Just keep one, well tabbed, well-organized build.settings and you should be good to go.
Rob
@GoG I could see where a reviewer might get tripped up on in-game currency, in particular, if you donāt let them buy coins.Ā Some of Appleās reviewers are new and they usually feel they have to be the most strict.Ā But they should be able to explain that to you.
Rob
Thanks for your answerĀ @Rob.
Iām still hoping the reviewer will replyā¦ someday 
You canāt buy coins indeed, but the āearn to unlockā mechanism is as old as platformers (plus the IAP does unlock all levels).
It will be sad to confirm that Apple just donāt allow it (even if it shouldnāt be any of their concernā¦)
Guys look here . Other developers also have this problem. Apple scans the binary for Non Apple Payment stuff. Obviously Stripe and more. But it looks like their bot doesnāt work
Thanks for the additional info.
If it is an issue with Apple bot, this is really bad as there is not much we can doā¦
Also, I finally received an answer from the review team (same as @d.mach):
- 3.Ā 1.1 Business: Payments - In-App Purchase
Hello,
Thank you for your reply. Our team has confirmed this app contains non Apple payment methods.
To continue review, it would be appropriate to remove all non Apple payment methods, then resubmit a new binary for review.
Note: Continuing to hide functionality within your app or other dishonest acts may result in the removal of your apps from the App Store and termination of your Apple Developer Program membership and all associated memberships.Ā
Thank you,
App Store Review
As you can see, this is not helpful at all.
I asked for details and they just confirmed itā¦
No comment.
@GoG I go the same message like you.
Will sent them a email where I will tell them which 3rd party SDK the binary had and made a Demo Video of the In-App Purchase mechanism in the app.
When you talk with App Review you need to give them all information You have. They donāt say which code breaks.Ā
My concern is even when I remove ALL 3rd party Sdks the review might break. (Note: Itās not a Corona app)
Their Warning to remove all apps in their message scares me off a little bit.
It is scary indeed.
And I canāt just remove my 3rd parties SDK without breaking essential features either.
On forums, some people say it is because the Apple bot pick up keywords such as āpaymentā
in the app code that donāt belong to Apple IAP framework (even if it is not another payment method).
I think itās weird as previous versions of my app got validated (I didnāt change my 3rd parties since).
I was thinking more of a rejection from a human reviewer in this case (could explain the sudden change).
Please keep us updated if you manage to get your app approved.
Iāll try to get more info from the review team on my side and post it here.
Note: I sent them a screenshot of my single IAP menu/button with my reply
but they didnāt seem to have taken it into account, btwā¦
Someone at the Apple forum posted , he removed Rewarded Ads in his game, and got approved.Ā
Hope they donāt mean āRewarded Adsā is āNon Apple Paymentā Ā since every Ad Network has that it in their SDKsĀ
We also got rejected for this exact same reason last week. We asked for clarification from the reviewer and got the same reply as others in this thread: just stating that we are using a non-Apple payment method. This is puzzling since we do not have any third party non-Apple payment methods implemented. We do have some third party ad networks as well as rewarded ads implemented but these have never been a problem before in the last 3 years that our app has been liveā¦
Ā
We are currently trying to decide what to do next. Please keep us updated if you manage to get any clarification for what could be causing this issue and if you find a way to get your app approved.
Our application has also been rejected, and the reason is 3.1.1. One of my applications was completely without third-party payment, but was also 3.1.1. Now Iāve considered whether the engine is a problem. Hopefully the official will come out and discuss it together.
People who have the issue used Ā Cocos2d, Cocos2d-x, Unity3d and now Corona. Ā So itās across frameworks.Ā
A list what it may be can be (summarize across Forums):
Billing SDKās like Stripe
3rd party SDKs ad networks, analyticsĀ
To much āPurchaseā,āPaymentā symbols Ā in code not related to StoreKit API