Hi Simon, could you see if you still have this problem in the most recent build? Thanks.

from android.

Hmmm, I got a force close after viewing a photo then switching to the
Add photo tab.

So I have cleared all the app data, and uninstalled and then
reinstalled it, and have been more successful:

This prompted me to sign in when I tried to add a photo.

I notice that it upper-cased the S in my username (and that is great
to see working on the caption field by the way - thanks). I'm not sure
if its right to do that though for the username field - but in fact it
doesn't matter and does not need changing because internally we always
lowercase the username anyway, for consistency.

I notice that the text on the AB tab has a missing 'be':
"Turn-by-turn route information will shown here oncce a route is planned."

I successfully uploaded a photo and yes I got the X.

Apart from that it all seems to work now - here's the route I planned:
http://cambridge.cyclestreets.net/journey/1531893/

(There's an action me to find out why this is not included on
/journeys/mine/ on the html site.)

How can I found out the journey number of the route?

Many thanks, shall be putting it to more use soon.

Simon

On 24 January 2012 17:36, Jez Higgins
[email protected]
wrote:

Hi Simon, could you see if you still have this problem in the most recent build? Thanks.

---

Reply to this email directly or view it on GitHub:
#43 (comment)

Simon

Simon Nuttall
100 Thoday Street
Cambridge
CB1 3AX
01223 500902
+44 1223 500902

from android.

I'll try to reproduce the force close, but I'm not confident.

Pleased the X is showing.

The journey number is shown on the itinerary screen. Could also add it the map view if you wanted.

from android.

On 24 January 2012 18:23, Jez Higgins
[email protected]
wrote:

I'll try to reproduce the force close, but I'm not confident.

I appreciate that is difficult to try to reproduce. Maybe its because
I completely removed the old version that it worked this time. I'll
report again if it comes back.

Pleased the X is showing.

Yes - reassuring. Will try to do more live testing tomorrow out on the
streets with geolocated photos.

The journey number is shown on the itinerary screen.  Could also add it the map view if you wanted.

Ah, yes, so it is. No I don't think the map view really needs it too.

---

Reply to this email directly or view it on GitHub:
#43 (comment)

from android.

On 24/01/2012 18:10, si-the-pie wrote:

Apart from that it all seems to work now - here's the route I planned:
http://cambridge.cyclestreets.net/journey/1531893/

(There's an action me to find out why this is not included on
/journeys/mine/ on the html site.)

Well, we're not passing anything to api/journey.xml that would identify
the user, so you've got nothing to join it up with. If there's
something I should be doing at the android end, do you want to open a
seperate ticket.

Jez

from android.

On 24/01/2012 18:28, si-the-pie wrote:

On 24 January 2012 18:23, Jez Higgins
[email protected]
wrote:

I'll try to reproduce the force close, but I'm not confident.

I appreciate that is difficult to try to reproduce. Maybe its because
I completely removed the old version that it worked this time.

That's certainly why it did work. In Android apps we do an awful lot of
squirreling state away when the app loses focus, so that we can restore
it again later. In the photoupload I've changed what that is, so it was
probably failing to restore properly. The difficulty in reproducing it
that it might be related to your particular state. Might not be. I'll
have a go anyway.

Jez

from android.

On 24 January 2012 22:06, Jez Higgins
[email protected]
wrote:

On 24/01/2012 18:10, si-the-pie wrote:

Apart from that it all seems to work now - here's the route I planned:
http://cambridge.cyclestreets.net/journey/1531893/

(There's an action me to find out why this is not included on
/journeys/mine/ on the html site.)

Well, we're not passing anything to api/journey.xml that would identify
the user, so you've got nothing to join it up with.  If there's
something I should be doing at the android end, do you want to open a
seperate ticket.

#44

Jez

---

Reply to this email directly or view it on GitHub:
#43 (comment)

Simon

Simon Nuttall
100 Thoday Street
Cambridge
CB1 3AX
01223 500902
+44 1223 500902

from android.