i have app not plan ever allow user pay remove ads.
however, want beta testers able in final project. creating iap (that can't access within app because don't want people buy it) removes ads work? give testers promo code itunes connect, redeem (or found cool app called tokens mac allows create links) remove ads.
i don't want deal coding sort of login solution, or have static redeem codes in app use (that way if user gives out code technically use it), figure using apple iap allow redeemed once, therefore securing it.
is okay way of doing it, or there better way?
i wouldn't risk it...
you might able squeak by, wouldn't risk it. if app approved once, first update might rejected same reason, or second, etc. they'll know app has in-app purchase capability, , might pop red flags because don't have restore button, etc.
there's very, very fine line apple between "discouraged" , "disallowed," , it's better (and less of headache you) avoid skirting rules wherever possible, if you're technically not breaking any.
...but there plenty of better, , easier, ways.
that being said, using debug macro, or similar. can isolate parts of code work when you're working on debug version of app, rather release version, or vice versa.
doing that, simple this:
code code code... #ifdef release ad code here... #endif code code code... this way, ad appear if user running release version of app. testers won't see ads, actual users will, , won't need else it.
Comments
Post a Comment