iOS Asset Bundle Backward Compatibility?

[techmage]

So in another thread, a while ago, this answer was posted concerning how AssetBundles retain version compatibility:

Script references are identified by 3 strings when built into an asset bundle.

classname

namespace (Only provided when the script is contained in a .NET dll built outside of Unity)

assembly name (name of the dll when built outside of Unity or )
On PC / Mac / Web:

A TypeTree data structure is used to provide full backwards compatibility. Public variables can arbitrarily be removed / added / moved in the scripts and it will do “the right thing”. (Removed properties are ignored, moved properties are identified by name, Added properties use the default value)

On iOS / Android:

A hash of all serialized script properties is used to detect if the binary data has the same data layout. If it doesn’t match loading the asset bundle fails. This optimization reduces code size and massively improves load times on mobile. If the serialized data layout of builtin classes changes (eg. from 3.4 to 3.5) then the asset bundle is also detected as incompatible and will fail to load.

Joachim Ante,

That was posted around version 3.5 release.

What I want to know is, for Unity 4.0 is this still true? Are iOS Android assetBundles still not backward compatible or has that changed?

[techmage]

I’m bumping this thread because I’d really like to know, is this still true, or has it changed in Unity 4?

[aciang]

Yes it is still an issue in Unity4… :sad::sad::sad::sad::sad:
why unity has to make this is not backward compatibility…

[cheaster]

@aciang

Yes it is still an issue in Unity4… :sad::sad::sad::sad::sad:
why unity has to make this is not backward compatibility…

Can anyone suggest alternative solution to avoid this bad compatibility？