Closed jungleeToofan closed 5 years ago
Thank you for reporting this. I will take a look and try to have a fix submitted next week (in early January).
I've submitted a fix to the master branch for this. It might be a week or more before I create a new release, however.
It turns out that in 2018.3 the 2.0 Subset is still relevant if you set the Scripting Runtime Version to .NET 3.5 (which is deprecated). New settings were required for the .NET 4.x runtime.
Thanks again for the bug report!
Great! Happy to help :)
On Thu, 3 Jan 2019 at 21:44, Nathaniel Williams notifications@github.com wrote:
I've submitted a fix to the master branch for this. It might be a week or more before I create a new release, however.
It turns out that in 2018.3 the 2.0 Subset is still relevant if you set the Scripting Runtime Version to .NET 3.5 (which is deprecated). New settings were required for the .NET 4.x runtime.
Thanks again for the bug report!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/google/play-instant-unity-plugin/issues/127#issuecomment-451192246, or mute the thread https://github.com/notifications/unsubscribe-auth/ACpKUrLD-TSaF6swwvB9N5Oz05QVx8Keks5u_ixggaJpZM4Zjic9 .
Clicking the 'Update' button in Play Instant Player Settings sets the API compatibility level to .net 4.x