|
cstuckey
|
May 23, 2015 at 3:40 am
I am prepping for my event next week, and it seems now that the EE3 ticket scanning app is allowing tickets to be accepted when the attendee was already scanned and let it. What could the problem be here? I appreciate a quick response given the impending the event.
Thank you!
|
|
cstuckey
|
May 23, 2015 at 3:50 am
Update: It seems after 5 minutes of waiting and trying again the ticket was declined. This does not prevent people from having multiple of the same ticket and scanning the same ticket print out multiple as if they were a group to get multiple credentials. Any idea why there is such a delay, and any idea how to fix that?
|
|
Dean
|
May 25, 2015 at 2:42 am
Hi,
There shouldn’t be that length of a delay unless there was an internet connection issue?
The scanning is based on the number of attendees booked in one go. E.g if someone books a group of five people, the ticket for each is the same, so one copy can be scanned five times – was the ticket you tested a group booking?
|
|
cstuckey
|
May 25, 2015 at 2:44 am
No I just tested an admin created ticket. The internet connection should not have been an issue (more than 50mbps of bandwidth with no other devices being used). It was a good 5 minutes for the update itself occurred, even though the online attendees list showed they were checked in.
|
|
Dean
|
May 25, 2015 at 4:26 am
Can you confirm your exact version of:
EE core plugin
EE API plugin
EE mobile app
In the API settings, what have you got “API Session Timeout After” set to?
Also, what device are you using to scan?
|
