Exception when build after updating on new version

[Zed]

Hi.
I updated my client API from 1.5.5.0 to 1.6.0.2 and server API from 2.9 to 2.10. Using library from Release/Unity folder.
But when i build on Android, i got exception:

TypeLoadException: A type load exception has occurred.
I/Unity (29068): at Sfs2X.SmartFox..ctor () [0x00000] in <filename unknown>:0

on 1.5.5.0 and 2.9 working fine.
Where problem can be?

[Lapo]

Hi,
you're getting the problem when building the project or later when you're trying to run on the device?

Thanks

[Zed]

Hi,
you're getting the problem when building the project or later when you're trying to run on the device?

Thanks

got error message when run on device

[Lapo]

What device is it? What OS version?
Does the problem appear running on other Android devices?

thanks

[Lapo]

Also can you please post a screenshot of the advanced build settings? (stripping level etc...)

thanks

[Zed]

Also can you please post a screenshot of the advanced build settings? (stripping level etc...)
thanks

Added screenshot to attachment

Edited:
Using Unity version:
4.6.0f3

[Bax]

Try setting the API compatibility to .NET 2.0 instead of .NET 2.0 Subset.
It that still doesn't work, I suggest to give a try to the SFS2X C# API v1.5.7 available on this page: http://www.smartfoxserver.com/download/sfs2x#p=client

[Zed]

Try setting the API compatibility to .NET 2.0 instead of .NET 2.0 Subset.
It that still doesn't work, I suggest to give a try to the SFS2X C# API v1.5.7 available on this page: http://www.smartfoxserver.com/download/sfs2x#p=client

I tryed switch NET 2.0 Subset to NET 2.0, but result is same.

Is client version 1.5.7 capable with server version 2.10?
Requierments say: SmartFoxServer 2X v2.0.1 up to v2.9.2
or i have to use server version 2.9.0 ?

[Zed]

and one more question:
i got memory spikes in dashboard even if i disable extension in zone: (in attachment)
is it normal? or where problem can be?

[Lapo]

Hi,
the API 1.5.7 will work with any version, including SFS 2X 2.10 with the exclusion of the TLS encryption, which is only supported by API 1.6.x

The memory "spikes" are perfectly normal, yes. They are actually small fluctuations (a few MBs) more than spikes

cheers