Posted: February 24, 2013 at 11:39 pm
|
Hi there, The iPad app is giving me an error, the iphone app is working perfectly and the same credentials. error: “Sorry, cant log in” 404-not-found Please help. |
|
Hi Daniel, Thanks for bringing this to our attention, I dont have an iPad, so I will pass this question onto one of the support staff with one to see if they can see any issues. |
Hi Daniel, It’s my understanding that the iPhone app uses Espresso Services not the API, so they are different things… we’ll keep you updated. |
|
|
ok… it would be great if there were some instructions on how to use this iPad app then. And install the API. |
The API is still in Beta (pre-release) so we’re working on some of the documentation. Here is the API documentation: https://eventespresso.com/wiki/api-addon/ Here is some info though that might help: https://eventespresso.com/2013/02/announcing-the-new-event-espresso-api-addon/ https://eventespresso.com/2013/02/announcing-the-new-event-espresso-ipad-app/ |
|
Hi Daniel, Right now, the new API that works with the iPad app can be downloaded in the pre-release section of your account page. You’ll see a checkbox below the standard Downloads section that will allow you to opt-in to the pre-releases. Once you download the new API, which is labeled “Event Espresso API v2.0.0.B”, you can install it via your WordPress plugin manager just like any other Event Espresso add-on. |
|
|
I just downloaded the API and the iPad app and also can not log in “bad URL”. The old iPhone app still works. |
We are still working out aspects of the documentation. Once the new api is installed, you will see new menu item under the Event Espresso admin menu. You will need to adjust the api settings there. |
|
|
The API was installed and I even tried changing the “Allow Public API Access” to allow, but still got the error. “API Time Out After” set to one hour. |
Hey guys, I updated the documentation that explains how to install the API addon. |
|
|
Seth, Just checking what is the endpoint, it was the domain root directory, but that is not working and I have tried the directory where the plugin is located too? |
Should be the domain for the website. Eg.: mywebsite.com or http://www.mywebsite.com. If you want, send me the url and login creds via email and I will see if I can login. |
|
|
Seth, you should have received the login creds for tagpartyrecon.com |
It looks like the api is installed corectly on your site, but something might be misconfigured in the api settings. Take a look at this url on your site: http://tagpartyrecon.com/espresso-api/v1/events/public |
|
|
Seth. the directory http://tagpartyrecon.com/espresso-api/ does not exist on the site. |
|
Seth, Got your screen picture, nice but I still get “Sorry, can’t log in bad URL”. What did you do to get it to work? |
This is what I used to login: If you like, you can try testing with our test drive website. Enter this as the Event Espresso Endpoint: Login ID: myespresso |
|
|
The mystery deepens. I have repeated the various logins numerous times now with the same results. When I deliberately use an incorrect login or password I get the error telling me I have one or other wrong. |
Do you have times and dates entered for all your events? |
|
|
Yes, most of them are reoccurring events. Also it looks like I can login and not get the bad URL error if I change my user name by removing the space. The events all show on the old app and I still can login using that even with the space between my user names. Seth your login credentials are still good and you should be able to see the events and the error using your login. |
Peter, Can you please check your error logs? It looks like the API is timing out on your server. |
|
Or maybe running out of database memory: |
|
|
Working with my hosting company because there are no error logs!! I have increased the database memory and now get the errors: “No Events The request timed out.” and “…(Cocoa error 3840)” on upcoming events. I also get the error “No Events Para event_start with value 2011-07027 10:00AM:00 is not of allowed type datetime” when selecting past events. I have gone into the database and changed the time to 24hr from AM/PM in a the very early events that used that format. I can now see the oldest past 50 events, which are all deleted events that I do not want to see. I still have the bad URL when I use a two name login, but fortunately the old app still works. Can I increase the time out to get this to work, or is it a call to the database error where my host limits the number of calls (same issue as the Calendar)? |
|
Hostgater tell me there are no error logs since there are no errors being generated…they tell me it is the app that has a problem and timing out. |
K. I’ll pass this info on to the app and api developers. |
|
Not sure how this is a problem with the app, since you were able to login to our sandbox server and pull up events just fine. I am wondering if there is something wrong with your event data. This is the response I got back from the iOS developer, regarding the Cocoa error 3840: This is an error spit out from the JSON deserializer. Basically the JSON is either malformed it the response we are getting back is returning something other than JSON. In this case, the response is zero-length. No JSON body was returned. Definitely a server problem. I’m adding code to the next release to explicitly check for this and report a more human readable error. I will test the new code against this broken server. |
|
|
Seth, Looks like I am getting caught in between, app developers and isp host, though as you point out it could well be my event data, which is considerably greater in number than the test sites 4 today, 44 upcoming and 33 past events and no ongoing events. What I can state factually is the following: One other thing on the new iPad app on the demo site I could not work out how to redeem a ticket manually – how do you do this? |
Hi Peter, Sorry. I was mainly addressing the issues with the server in my response above. We are aware of the issue with the limitation of 50 events. It was kind of planned that way, for the first round of the app, because we are well aware that some people have hundreds, or even thousands, of events, but their [shared] servers and the app may not be able to handle the amount of data output/input, without some kind of caching in the JSON API, which we don’t exactly have nailed down at the moment. I have tested the app and the json api on our [dedicated] server, with 600+ events and 2000+ attendees. It’s a little slow, depending on the traffic to our site, but I haven’t been able to crash the app or the api yet. I will have our API developer look into the issue with the deleted events issue. To manually check in attendees you will need to click on an attendees name on the attendees name, then click the “Check-in” button in the top right corner of the page. Here is more info: https://eventespresso.com/wiki/mobile-apps/#ipadmanualcheck I am still working on #5. |
|
|
Thanks Seth. I found the “check-in”. 50 past and 50 upcoming events will be enough providing they are the last 50 and the next 50 respectively. I had one other thought, that should be looked at; I have ongoing events that do not have start and end dates, or times, and do not show in the today screen, though they do show on the iPhone app. |
|
Seth, “Todays” 7 events were accessible on the iPad app, but I did note some other items that need to be looked at: |
Hi Peter, I created a ticket for the developer to look into this. |
|
RE: “1) Price option…” yes this was a bug in the API. Even though the members addon wasn’t active, members prices are actually still saved in the DB, and were getting returned instead of the normal prices. |
|
The support post ‘ipad app not logging in’ 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.