question

7 Comments
Brendan Vanous said on Thu, 09 October 2014 at 6:24 PM

What we've found is that there are certain compatibility issues on iOS with the Full version of .Net 2.0. Changing the compile settings in Unity from full .Net to .Net 2.0 Subset resolves these issues.

We will update the PlayFab C# SDK at a later date to ensure that we've accounted for the underlying compatibility issues.

---

fuddi said on Wed, 10 December 2014 at 8:00 AM

Hey,

We also have this issue and it is very annoying that our game on iOS cannot login with PlayFab.

Have you solved it and updated the PlayFab C# SDK or when do you plan to do it?

Best Regards

-Jesper

---

Brendan Vanous said on Wed, 10 December 2014 at 8:33 AM

Hi Jesper,

Because there's an easy workaround (use .Net 2.0 Subset) and no one has stated that .Net 2.0 Full is needed, we haven't prioritized this work. If you must have .Net 2.0 Full, can you provide specifics on what aspects of it are required?

Brendan

---

fuddi said on Wed, 10 December 2014 at 8:46 AM

Hi Brendan

OK I will try it out. We have some SQLite plugin which didn't work with .Net 2.0 Subnet, but we will try to use another.

Thanks for the quick reply :-)

-Jesper

---

Brendan Vanous said on Wed, 10 December 2014 at 2:55 PM

Sounds good. Could you also let us know what the specifics are on the plugin (basically, the name)?

Thanks,

Brendan

---

fuddi said on Thu, 11 December 2014 at 2:52 AM

Sure.

The plugin was SQLiter (https://www.assetstore.unity3d.com/en/#!/content/20660). When trying to build the Unity project with .NET 2.0 Subnet, we got these errors... see log file.

Thanks

-Jesper

---

Brendan Vanous said on Thu, 11 December 2014 at 3:33 PM

Thanks, Jesper. As it turns out, one of our engineers jumped on this ahead of schedule and checked in an update to our Unity SDK which accounts for the issue on iOS. If you grab the latest version, you shouldn't run into this anymore.

Brendan