I have the following implementation of a Parcelable
class:
public class DemoModel implements Parcelable {
private String para1;
private
Yes it does. Order of write variables is up to you and you can do it as you want, but you must read them in that same exact order. It will give you runtime crash if order will be different.
Why? Mechanism is blind, so it trust you to get it in right order.
Mostly for performance benefits, because it don't have to search for a specific element.
You can see in Parcelable
interface, that it creates array with size of a number of elements you put in parcel.
public interface Creator<T> {
/**
* Create a new array of the Parcelable class.
*
* @param size Size of the array.
* @return Returns an array of the Parcelable class, with every entry
* initialized to null.
*/
public T[] newArray(int size);
}
According to this source:
One very important thing to pay close attention to is the order that you write and read your values to and from the Parcel. They need to match up in both cases.
It's caused by the way parcelable is implemented by its creators