[AC-2210] Ti.Storekit: "Deploy to Device" will not run in "Live" environment

GitHub Issue	n/a
Type	Bug
Priority	n/a
Status	Closed
Resolution	Fixed
Resolution Date	2013-05-22T21:41:53.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	Appcelerator Modules
Labels	documentation, store, storekit
Reporter	Fokke Zandbergen
Assignee	Shak Hossain
Created	2013-05-22T15:00:41.000+0000
Updated	2016-03-08T07:41:12.000+0000

Description

In the example code it says in app.js, starting on line 37:

1) Storekit works in two different environments: "Live" and "Sandbox". It automatically uses the "Sandbox" when you
 run your app in Xcode. This means that "Deploy to Device" in Titanium Studio will connect to the "Live" environment!
 Using a test account in "Live" will ruin the test account. And paying for items with a live account will quickly
 suck up your hard earned cash. So be careful!

I ran an app over "Deploy to Device" as well as "Ad Hoc/Enterprise" distribution and in the simulator, but it always works in "Sandbox". Be aware that I'm not talking about TC-2329! It shows when you login to do a purchase, using a live Apple ID. You will get a system alert (not generated in the app) telling you to use a Test User for the sandbox environment it's in, as shown in the attached image. The only environment in which you are *not* in sandbox, is when distributed via the App Store. The comments in the app.js should be updated for that.

Attachments

File	Date	Size
alert.png	2013-05-22T15:00:41.000+0000	48979

Comments

Fokke Zandbergen 2013-05-22

Double checked: * The Ad Hoc distribution WAS signed with a distribution certificate, not a development. * I was signed out of any Test User account before doing the purchase.
Jeff English 2013-05-22

Updated comment in app.js file. Updated module (version 2.0.2) will be in the MarketPlace shortly.
Shak Hossain 2014-01-03

Hi Fokke Zandbergen, I believe this is fixed. Please let me know if this ticket can be closed. Thanks, Shak
Fokke Zandbergen 2014-01-04

Yes, the comments in the example are now correct

JSON Source