Search Issue Tracker
Not Reproducible
Votes
1
Found in
2017.2.0f3
Issue ID
958868
Regression
No
[.NET 4.6] "No valid name for platform: 11" error is thrown when Facebook SDK is imported and scripting version set to 4.6
To reproduce:
1. Open project attached by QA
2. Open "Main" scene
3. Make sure that Scripting Runtime Version is set to experimental (4.6)
4. Check the console
Expected result: There shouldn't be any errors in the console
Actual:
No valid name for platform: 11
UnityEditor.PluginImporter:GetCompatibleWithPlatform(BuildTarget)
Google.FileMetadataByVersion:EnableMostRecentPlugins()
Google.FileMetadataSet:EnableMostRecentPlugins()
Google.VersionHandler:UpdateVersionedAssets(Boolean)
Google.VersionHandler:.cctor()
Facebook.Unity.Editor.AndroidSupportLibraryResolver:setupDependencies()
Facebook.Unity.Editor.AndroidSupportLibraryResolver:.cctor()
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes()
Reproduced with: 2017.1.2p1, 2017.2.0f3, 2017.3.0b5, 2018.1.0a1
OS: Windows 10
Not reproducible on macOS 10.12.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment