Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Mobile App Issues | Event Espresso - Staging Server
At our first event, the app failed on me. It was totally embarassing… and chaos because I didn’t have a way to check people in except pen and paper. The app logs in fine but I cannot scan because it just spins when it forces me to find an event. No event showed in the Today, nor upcoming or past. I also tried searching and it just spins saying it’s loading – fetching events… So I get on here to search posts before posting and found a post for the problem saying that now there is a NEW HD APP that supposedly replaces this one? Great! So I go out and download it. It won’t let me login. I’m using the same endpoint url and login info from the other app – which allows me to login… But this one gives me a “Sorry, can’t log in 404-not found” error. What do I do?
Did you install the new mobile app API that works with the HD app? You can download it from your account page. The new mobile app API is labeled: JSON API v2.0
There is more information on the new API and app here:
Ok, that worked to allow me in… But I scanned all the tickets as I would have if it had worked that day and all buy one declined saying they were already checked in… They weren’t because I was looking at the attendee list screen at the time. After I scanned them all though, I refreshed and they showed up as attending. So, for future reference, is that a small bug?
This isn’t something I’ve seen where it declines them saying it was already checked in, but they were not checked in. Are you running any caching plugins?
Viewing 3 reply threads
The support post ‘Mobile App Issues’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.