Errors with arrays as constructor parameters about parceler HOT 8 CLOSED

Robolectric, at least the version Parceler is using, doesn't deal with the int or byte arrays at all. Im hopeful that the next release will allow these tests to go through. Does this fail in the emulator or an actual device? If so I can look at it in depth this evening.

from parceler.

Okay, I am unsure how I managed to close the issue - that was not on purpose.

But yes, I can reproduce this both on a real device and in the emulator. For what it's worth, here is my test application:

https://gist.github.com/ahem/e8472dc653bddb30de0e

from parceler.

I can say how many times I've almost or actually hit that close button on accident.

Excellent. I'll look at this soon and issue a fix.

from parceler.

What version are you using?

from parceler.

I have only tested with 0.2.8, but the problem may be in earlier versions also.

from parceler.

@ahem , Looks like the problem was the ordering of arrays/collections vs single values. Arrays and collections need to be stored in intermediate values whereas single values can be put into the constructor directly. This was causing an ordering problem if arrays/collections showed up in the constructor after single values. The fix was to ensure the ordering by storing the single values in intermediate values as well. I've deployed this fix under 0.2.9-SNAPSHOT and I'm willing to push a release out if it works for you. Let me know.

from parceler.

Yes, I can confirm that the issue is fixed in 0.2.9-SNAPSHOT. Thank you for the quick fix again :-)

from parceler.

Just released under 0.2.9. Thanks again for reporting the issue!

from parceler.