I'm adding in-app purchase support in my app. It says that there are two types of in-app products: durable and consumable. It's ok.
But here: http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh967814.aspx we can read:
ProductType attribute for ProductReceipt element: Determines the product type. Currently only supports a value of Durable.
Can anybody explain what does it mean? O_o
Check here in "Receipts" section, it says type can be Durable or Consumable.
Related
I got rejected from Apple today,
They say
We noticed that your in-app purchase product is set to an incorrect
product type.
(Paid Plan) is set to Non-Consumable.
Next Steps
Since the service offered by your app requires the user to make an
advance payment to access the content or receive the service, please
use the non-renewable subscription in-app purchase product type.
Non-renewable subscription content must be made available to all iOS
devices owned by a single user, as indicated in guideline 3.1.2 of the
App Store Review Guidelines
But in my app, I just have a package to get full access(remove Ads, add some features)
And the user just buy it once!
So that's why I use Non-Consumable.
why apple rejected it?
In My App I have used non-consumable IAP while Login.
and I want to use Auto-renewable subscription for Remove Ad feature.
So, Will it be any chance of rejection from Apple or Is this a valid to use multiple product in one App?
Yes, It is possible but for that you have to create two group in your developer portal. For same group you can't purchase two IAP.
Yes, You can use multiple IAP same time.
There might be a problem If your both active IAPs provide the same features.
Apple might reject it.
I am developing an iOS app which allows in-app purchases.
The in-app purchases are basically different themes/characters for the app.
I offer the default for free (obviously), and some more paid themes.
I implemented the store UI as a table view.
Now this is the part I'm concerned about: I added a free in-app purchase entry for the default theme. My code can identify the free products when it gets the product list from Apple infrastructure, and I treat the free ones as if the user has already purchased them (UI is set as product was purchased, user can use the theme).
My question: is this behaviour is acceptable by apple reviewers or my app/in-app purchase will be rejected for this?
What is the purpose of adding the free in-app purchase? I don't know much about the review guidelines, but it sounds like the kind of thing they would reject your app for. It would probably be easier to detect the default kit in some way other than a free in-app purchase.
EDIT: An alternative would be to add the default theme to the list after the list is retrieved from IAP. You could create a class that holds all the same information, but can be constructed with either data from IAP or from the default theme data.
I do something similar, and it's been approved by Apple for a long time now. However, for my "free" content there is no actual SKU in the Apple infrastructure. Rather than create a SKU with some 'dummy' price (since you can't make an in-app purchase any less than Tier 1), I just present the free option in the UI as a peer of the purchasable options.
I would worry that if you do have an actual SKU with a price, but you give away that SKU, Apple may reject your product out of concern that you are doing an end-run around Apple payment and depriving them of their percentage of the sale. It's also possible they may not reject your app the first time, but will reject some later version when a more thorough tester pokes around. (Yes, really. I have twice had apps rejected that had had the offending behavior through three or four approved versions. Consistency? What?)
Relevant references:
11. Purchasing and currencies
11.1
Apps that unlock or enable additional features or functionality with mechanisms other than the App Store will be rejected
11.2
Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be rejected
...
11.7
Apps that use IAP to purchase items must assign the correct Purchasability type
from App Store Review Guidelines
I've been searching for a while, but it may be too obvious and people don't post about it.
I want to know if I can put a dynamic price for a product.
I have a delivery application and the price may vary with the distance.
Also, it can be a non integer price, like $2,43.
Is it possible?
Also, I couldn't set a price at iTunes Connect, I need to be reviewed first?
Thanks a lot in advance!
As noted by other poster, you cannot have variable in-app purchases. You have to select one of the provided price tiers.
Now assuming you are making a taxi-service app then what you need to do in your app is provide the user with a list of prices that are fetched from your server for example how much will it cost to go from point A to point B. You can then "charge" them outside of the in-app purchases using your own pricing service (credit card over the phone etc).
Again in-app purchase doesn't work with what you need.
You can't set custom prices for an In-app purchase. You need to set the price using one of the tiers available.
You can set different prices for the same product by editing the the In-app purchase, selecting a tier, setting a "Price Effective Date" and "Price End Date" and hitting the button "Add to schedule".
EDIT: This can now be done using Apple Pay
You cannot set your own custom price for an in-app purchase, you can only use the ones that apple provides you with (this is most likely to stop things like in-app purchases for $0.01 or $100,000). Apple gives you plenty of price ranges, so you could just use $1.99 or $2.99 for your needs. In-app purchases are mostly non-integer prices.
Yet, if you were to go threw a third-party, other than apple, say PayPal you could do this easily, yet you won't get as many functionalities that IAPs have, and it would be near impossible to trigger something like removing ads inside of the application on this payment unless you have a server that you are using for your application. To implement PayPal, you could look at their tutorial HERE.
In short, no, you cannot set your own prices for in-app purchases, you can only use the ones that Apple provides (which can range from 0.99 to 999.99), yet, you can use a third-party like PayPal to get this functionality, although it really isn't needed
Does the app have to offer to restore non-autorenewing subscription purchases (the way it is required with one time purchases) or should this be implemented through the "infrastructure" that Apple requires us to build for sharing purchases among different devices?
I ask because in testing mode, when I try to Restore this type of transactions, I get an empty list back from Apple.
Thanks in advance!
Sam
Per response on the Apple Developer's forum, non-renewing subscriptions are not restorable.
Apple does not provide non-autorenewing subscription
below 5 was provided by the apple
1. Consumable
2. Non-Consumable
3. Auto-Renewablesubscriptions
4. Free subscriptions
5. Non-Renewing subscriptions
on which one you are working on.