Multiple Eye Fi cards on a single account login fails.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Add multiple cards to an Eye Fi account.
2.Try to login to set the Eye Fi card key.
3.

What is the expected output? What do you see instead?
I would see all of my cards display in the list but I get an error and a 
request to force close the application.

What version of the product are you using? On what operating system?
1.0.1

Please provide any additional information below.
 Here is the debugger error.

11-02 15:42:15.102: ERROR/AndroidRuntime(4499): Uncaught handler: thread 
Thread-11 exiting due to uncaught exception
11-02 15:42:15.102: ERROR/AndroidRuntime(4499): 
java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
11-02 15:42:15.102: ERROR/AndroidRuntime(4499):     at 
java.util.ArrayList.get(ArrayList.java:353)
11-02 15:42:15.102: ERROR/AndroidRuntime(4499):     at 
com.leshak.eyefidroid.eyefiUploadKeyLoader.getEyeFiCardsList
(eyefiUploadKeyLoader.java:241)
11-02 15:42:15.102: ERROR/AndroidRuntime(4499):     at 
com.leshak.eyefidroid.eyefiUploadKeyLoader.access$1
(eyefiUploadKeyLoader.java:215)
11-02 15:42:15.102: ERROR/AndroidRuntime(4499):     at 
com.leshak.eyefidroid.eyefiUploadKeyLoader$ProgressThread.run
(eyefiUploadKeyLoader.java:208)

Original issue reported on code.google.com by Elder.Su...@gmail.com on 2 Nov 2009 at 9:46

[GoogleCodeExporter]

I also get a force close on login. I deleted one of my 2 cards via my laptop 
and it
still forced close. 

I am running version 1.0.2 on a rooted / patched G1,
(signed-dream_devphone_userdebug-ota-14721, update-cm-4.2.5-signed).

Original comment by fauxs...@gmail.com on 26 Nov 2009 at 10:18

[GoogleCodeExporter]

I updated to Cyanogen 4.2.7.1 and get the same force close issue.  Basically, 
as soon
as the device list payload arrives, it bombs. It gets past the auth stage, 
since bad
user/password combos yields 'user not found' or 'bad password' errors as 
appropriate.

Original comment by fauxs...@gmail.com on 6 Dec 2009 at 4:38

[GoogleCodeExporter]

Here is my Android log with the relevant lines, and the associated stack trace 
section.

Original comment by fauxs...@gmail.com on 6 Dec 2009 at 5:20

Attachments:

• eyefi_log.txt

[GoogleCodeExporter]

Error persists on 1.0.3.

Original comment by fauxs...@gmail.com on 7 Dec 2009 at 7:07

[GoogleCodeExporter]

BUMP!

Original comment by fauxs...@gmail.com on 21 Jan 2010 at 1:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It works, but I needed an AP that wasn't WPA2 Enterprise to connect to for the 
first
time.  I moved to an open AP and took a couple of pictures and transmitted them 
to
the Eye-Fi manager.  After logging back in with Eye-Fi droid it seemed to work.

I also had two cards, so that's not a problem either.

It probably should report up an error message to the user that the wifiUploadKey
couldn't be found and suggest that the user takes a picture using the EyeFi 
upload
manager first.  That would make more sense rather than just dying.

Original comment by rcl...@gmail.com on 29 Mar 2010 at 12:52