title: How long will store kit keep unfinished transactions?
body: <p>I'm working on this app with in app purchase enabled.
  The happy path is all covered, everything is fine, I'm trying to work out the non happy path.</p>
  
  <p>To put it simply, the purchase is bound to a server side component.
  On purchase, when the transaction is in the "Purchased" state, I'm supposed to go out to the server, which will enable the user's account.
  When the request comes back, I then clean up some stuff and eventually call -finishTransaction: on the SKPaymentQueue.</p>
  
  <p>The non happy path is pretty much when the server call fails for whatever reason. Network not available, network timeout, the user closed the app right after purchasing it and just before I could make the server call, you name it.</p>
  
  <p>My tests in the 5.1 simulator with a sandbox account show me that an unfinished Purchased transaction will come back in the queue on next start up, and my delegate will be properly called with it.
  But, after a little while, say 5 minutes for instance, boom, gone is the transaction.
  Considering the whole stability of sandbox accounts, I'm willing to call that on the simulator's implementation, but it's hard to tell.</p>
  
  <p>What's the appropriate way of dealing with this problem?</p>
  
  <p>Bonus question: when does apple actually charge somebody? Sounds like it should be AFTER the app called -finishTransaction:, but I couldn't find any evidence of this anywhere.</p>
  
  <p>Thanks,
  /kra</p>
  
  <p>UPDATE:
  testing on physical device, almost an hour and the transaction is still there. Looks like the transactions disappearing is a simulator thing.</p>