Search Issue Tracker
Won't Fix
Votes
4
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.4f1
2019.3.0a1
2020.1.0a1
Issue ID
1192556
Regression
No
NotImplementedException is thrown when setting System.Net.FtpWebRequest.ClientCertificates property
How to reproduce:
1. Open the 'test' scene in the user attached project ("project") using the EnvIronman VM
2. Enter play mode
3. Check the console output
Expected results: No errors are thrown
Actual results: NotImplementedException is thrown
Reproducible with: 2017.4.34f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
Additional notes:
1. Full Error Message:
NotImplementedException: The method or operation is not implemented.
System.Net.FtpWebRequest.set_ClientCertificates (System.Security.Cryptography.X509Certificates.X509CertificateCollection value) (at
<29644300878340d7aabe2467c2459c0d>:0)
(wrapper remoting-invoke-with-check) System.Net.FtpWebRequest:set_ClientCertificates (System.Security.Cryptography.X509Certificates.X509CertificateCollection)
FTPClientCertTest.TryFTPUpload () (at Assets/FTPClientCertTest.cs:45)
FTPClientCertTest.Start () (at Assets/FTPClientCertTest.cs:29)
2. The error occurs with both mono and IL2CPP Scripting Backends, and both .NET 4.x and .NET Standard 2.0 Api Compatibility levels
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
This functionality is not implemented in our current version of Mono. It is implemented in the upstream version of Mono and we will be upgrading our version of Mono in the future which will likely resolve this issue.