title: paymentQueueRestoreCompletedTransactionsFinished: return queue with empty transactions array
body: <p>Problem: I call <code>[[SKPaymentQueue defaultQueue] restoreCompletedTransactions];</code> And it return to my observer <code>paymentQueueRestoreCompletedTransactionsFinished:</code> <code>SKPaymentQueue</code> with empty transactions array. But I have purchased <strong>non-consumable</strong> in-apps.</p>
  <p>I'm testing how my app could restore purchases from different states.</p>
  <p>Simple steps to reproduce:</p>
  <ol>
  <li>Add payment and complete purchase. The queue returns <code>SKPaymentTransactionStatePurchased</code> transaction, so the app enables feature and finalize transaction in queue.</li>
  <li>Remove information about purchase, so I can re-purchase. (imagine, that a user reinstalled the app, or start using the app on another device)</li>
  <li>Try to purchase in-app again. receive &quot;<em>You've already purchased this. Tap OK to download it again for free.</em>&quot;. Press OK, and the queue returns <code>SKPaymentTransactionStatePurchased</code> transaction, so the app enables feature and finalizes the transaction in queue.</li>
  <li>Remove information about purchase again.</li>
  <li>Try to purchase in-app once again. Receive &quot;<em>You've already purchased this In-App Purchase but it hasn't been downloaded.</em>&quot;. There is only one OK button, and even before you could press it, you'll receive transaction with state <code>SKPaymentTransactionStateFailed</code>. The app finalizes the transaction, but it won't enable feature when transaction is failed.</li>
  <li>Finally try to restore completed transactions with <code>[[SKPaymentQueue defaultQueue] restoreCompletedTransactions];</code>. And it return to observer <code>paymentQueueRestoreCompletedTransactionsFinished:</code> <code>SKPaymentQueue</code> with empty <code>transactions</code> array.</li>
  </ol>
  <p>I feel that something is broken in Apple Sandbox servers, so I can't restore transactions correctly. Or am I doing something wrong?</p>