Thomas Heigl

Hi @chrisr3. Could you create a minimal reproducer (ideally a unit test) for the issue you are facing? I'm open to adding a flag to `CollectionSerializer`, but there might be...

OK thanks! I quickly glanced over the code: Do you really need to globally override Kryo's behavior? Or would it be enough to create a custom serializer that uses `writeResolve/readReplace`...

So you are serializing arbitrary classes in your case and have no control over which classes are serialized? We could add a flag to `CollectionSerializer` that disables the optimization, but...

Can you try this: ```addDefaultSerializer(Collection.class, MyCollectionSerializer.class);``` I'm not 100% sure about the ordering of serializers right now, but this might work.

Default serializers registered after the built-in serializers should take priority. I just did a quick test and it looks like `MyCollectionSerializer` is chosen over `CollectionSerializer`. Please give it a try.

> Yes, I agree. However, I have now discovered that my example code is actually testing the ObjectArraySerializer and not the CollectionSerializer 🤦. It looks like both of these default...

OK, this looks like a dead end. It seems that in order to support your use case, we would indeed need some configuration options for both `CollectionSerializer` and `ObjectArraySerializer`. Then...

> There doesn't seem to be a unique "point of contact" for all new serializers, so I'd likely also need to modify these functions I just took another quick look...

We ran into a similar issue today. Our app is not a pure SPA and we do full-page navigation from time to time. Every time this happens, `platform.ready()` is fired...

@jennantilla: Please let me know if you need more information. This issue is important to us and we can provide additional info if needed.