|
KLLASC
|
May 28, 2019 at 6:24 pm
We have generated some 300 QR, some which trigger an invalid QR code error, including one that was working previously during testing.
Grateful if you would advise any troubleshooting or remedial actions.
Thanks.
|
|
KLLASC
|
May 29, 2019 at 5:30 am
Hi, appreciate your urgent assistance as our event is ongoing.
We are thinking if resending the ticket/QR notification is the culprit.
|
|
Tony
|
May 29, 2019 at 7:34 am
Hi there,
How did you generate the 300 QR codes?
What are you using to scan the barcodes? The mobile apps? If so which mode are you scanning them in?
Have the ‘invalid’ QR codes all previously been scanned before?
We are thinking if resending the ticket/QR notification is the culprit.
The QR code doesn’t change when you resend, but if the QR code has been previously scanned and ‘checked in’, then you simply ‘checked out’ the ticket again if you scan with the apps for check-in they will see that the ticket has previously checked in and show as invalid.
So are the non-working codes all codes that have been checked in before?
Hi, appreciate your urgent assistance as our event is ongoing.
Note that ‘bumping‘ your threads will have the opposite effect than intended as we work through threads based on reply date. Adding another reply to your thread basically puts the thread to the back of the queue.
|
|
KLLASC
|
May 29, 2019 at 8:31 am
We resent the QR code to registrants using “Resend Ticket Notice”. Yes, using the EE Mobile App, in its continuous scan mode.
No check-in records for these tickets. The invalid code appears in the app itself.
I have uploaded the screen shots here.
|
|
Tony
|
May 29, 2019 at 8:49 am
How did you generate the 300 QR codes?
Can you send me the ticket links for the registrations shown in the screenshot so I can scan them? You can set the reply as private if preferred.
|
|
KLLASC
|
May 29, 2019 at 9:03 am
This reply has been marked as private.
|
|
Tony
|
May 29, 2019 at 11:55 am
The QR codes were generated when users register for the events in EE.
Ok, so just normal registrations, correct?
Subsequently, we resent the Ticket notice as a reminder and also in case some users accidentally deleted the first ticket notification.
That’s fine, resending the ticket notice does not change any of the values used.
The link you sent has 2 pictures of the QR’s rather than the ticket links which I could have used to confirm the details, those QR’s look correct for the above but I can’t be sure without the ticket link.
Which version of the app are you using? iOS or Android?
Are you using an event scan where you select the event and then open up the scanner or are you opening app and then just opening the scanner from the main event list?
|
|
Tony
|
May 29, 2019 at 11:57 am
One step you can do to narrow this down is to install the REST API log plugin.
Scan the ticket and then view the log for the scan request and see what the response is, does it show any errors?
|
|
KLLASC
|
May 29, 2019 at 4:19 pm
Yes, normal registrations.
The links to the ticket are as below:
Reg Code: 16-7-1-145e
Reg Code: 20-7-1-5039
It is a 4-day event, we choose the day of the event before scanning with an iPad
|
|
Josh
|
May 29, 2019 at 4:27 pm
You could try that REST API log plugin as Tony advised. Please note that we do not have admin access to your site, so the links you included are not accessible.
|
|
KLLASC
|
May 29, 2019 at 4:43 pm
This reply has been marked as private.
|
|
KLLASC
|
May 29, 2019 at 4:55 pm
This reply has been marked as private.
|
|
Josh
|
May 29, 2019 at 5:34 pm
Those tickets are for an event that’s in the trash. Specifically, the event that’s named 2019_individual_sessions. That’s why they’re invalid.
|
|
KLLASC
|
May 29, 2019 at 9:34 pm
This reply has been marked as private.
|
|
KLLASC
|
May 29, 2019 at 9:34 pm
This reply has been marked as private.
|
|
Josh
|
May 29, 2019 at 11:20 pm
I’m sorry I don’t follow what you’re describing as symptoms. When you trash an event, it’s expected that the tickets for that event will be invalid.
|
|
KLLASC
|
May 30, 2019 at 9:07 am
This reply has been marked as private.
|
|
Josh
|
May 30, 2019 at 11:41 am
It appears that someone moved those to the trash. I’ll reply again with a private reply that has the link to that event’s trashed registrations.
|
|
Josh
|
May 30, 2019 at 11:41 am
This reply has been marked as private.
|
|
KLLASC
|
May 31, 2019 at 1:10 am
This reply has been marked as private.
|
|
KLLASC
|
May 31, 2019 at 1:10 am
This reply has been marked as private.
|
|
Tony
|
May 31, 2019 at 1:22 am
Any chance, a system issue caused the “auto” deletion into the trash?
No. There is no auto deletion code that would ‘soft delete’ (trash) registrations.
We have a garbage collection system designed to remove ‘incomplete’ registrations but those registrations firstly don’t meet the criteria to be deleted and secondly wouldn’t be trashed at all, they would be perm deleted if it was that system.
The only way registrations can be trashed is through the admin.
|
