Bug 973268 - ticketmonster-cordova (2.3.0.ER1) iOS contains a debugging alert box
Summary: ticketmonster-cordova (2.3.0.ER1) iOS contains a debugging alert box
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: TicketMonster
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Marek Novotny
QA Contact: Tomas Repel
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-11 15:17 UTC by Tolis Emmanouilidis
Modified: 2014-03-04 00:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-06-13 09:57:16 UTC
Type: Bug

Attachments (Terms of Use)
Final Order screen with alert (175.09 KB, image/png)
2013-06-11 15:17 UTC, Tolis Emmanouilidis
no flags Details

Description Tolis Emmanouilidis 2013-06-11 15:17:41 UTC
Created attachment 759694 [details]
Final Order screen with alert

Description of problem:
When completing an order either 'By Location' or 'By Category' and click the 'Buy' button, then a debugging alert appears.

Version-Release number of selected component (if applicable):

How reproducible:
Open the ticketmonster-cordova in XCode and make an order 'By Location' or 'By Category'.

Steps to Reproduce:
1. Open the ticketmonster-cordova in XCode
2. Compile it and open it on the iPhone simulator
3. Select 'By Category'
4. Select Sporting
5. Select Brazil vs Italy
6. Select Toronto: BMO Field venue
7. Select Tue 12 November 2013 show date
8. Select 03:00 show date
9. Click to book
10. Select B Premium gold reserve section
11. Fill amount 199.5
12. Fill email qa@example.com
13. Click checkout
14. Click Buy

Actual results:
A JavaScript alert appears

Expected results:
The final order should appear

Additional info:
Added screenshot

Comment 1 Tolis Emmanouilidis 2013-06-13 09:57:16 UTC
After investigating the source code, it seems that the alert box appears in case of trying to fulfil an invalid order (e.g when the quantity number is high).

In conclusion the alert box correctly appears and it is not a bug.

Note You need to log in before you can comment on or make changes to this bug.