Page 1 of 1

Evil gnome, Jelly Bean and mobilepickphoto

Posted: Wed Dec 12, 2012 1:18 am
by cusingerBUSCw5N
I've just posted an email to tech support. Mobilepickphoto, which was working so nicely on Ice Cream Sandwich operating system for androids is failing on Jelly Bean.

If you take a picture, it won't display the picture on the device. I am trying to ftp it and when it ftp's it is empty...

Anyway, I will post their response, but in the meantime, it support my theory that an evil gnome inhabits my app. :twisted:

Re: Evil gnome, Jelly Bean and mobilepickphoto

Posted: Wed Dec 12, 2012 5:54 pm
by cusingerBUSCw5N
The evil gnome is winning so far... I thought that by feeding it meat, it would be happy, but instead, it just got stronger and tougher!


Tech support has confirmed the problem of mobilepickphoto with Jelly Bean and I have reported it as a bug.

Also, I am having difficulty accessing pictures that are copied from a mobile device, stored on a server, and then accessed by the mobile device. These pictures come up blank. But the image is actually being stored on the server (I can see the file size) and if I access the same picture on my laptop, the image appears. Also confirmed by tech support.

I reported that as a second bug.

Re: Evil gnome, Jelly Bean and mobilepickphoto

Posted: Sun Jan 06, 2013 11:21 pm
by hill180
I just ran into the mobilePickPhoto bug, where you can take the picture, but you can't "ok" it.

Have you gotten a work around, or has this bug been closed?

Re: Evil gnome, Jelly Bean and mobilepickphoto

Posted: Fri Jan 18, 2013 4:48 pm
by cusingerBUSCw5N
Just got confirmation from RunRev - it is a bug and will be fixed in the next release. No workaround. Mobilepickphoto on Jelly Bean does not work.

Re: Evil gnome, Jelly Bean and mobilepickphoto

Posted: Thu Feb 07, 2013 1:09 pm
by larryGAab48
Heya Gang, I'm bumping this in the hope that we can get this fix included in the current 5.5.3 build. I was in contact with Support and one of the guys suggested adding a comment to the existing bug report requesting this fix for 5.5.3 instead of the targeted 6.0. I would encourage and other Android developers that need this fix to contact support in order to add to the request.

best,
Laurence