Yes, you need both.
ok, but will that still allowe me to test in-apps from different apps with one email account?Each In-App Purchase test user account is tied to one and only one email address. As such, you cannot reuse an existing email address with another test user account.
Restoring non-consumable purchases
As noted above, if you are selling such products then you are expected to provide a way for the user to restore completed transaction.
Once the user requests to restore transactions you need to call MyStore.RestoreTransactions. The PurchaseCompleted event will be raised for each previous purchase of non-consumable products.
The TransactionsRestored event will be raised at the end.
Note that the user might be asked to log in to his account, therefore you shouldn't call this method when the apps starts to find existing purchases (unlike the Android library).
is this a typo? shouldn't it be #provisionfile instead?You can use #MobileProvision to tell the IDE which provision file should be used.
in my opinion just put a button. when the user will click on it he will first get the price of the product then he can decide if he wants to purchase.Is it good to show the price of the various InApp purchases inside the app, in a "purchase" page ?
Or is it better only to place the buttons and let the user to see the prices when it clicks and then appear the box from the AppStore ?