Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.0.0f4
Issue ID
677289
Regression
No
Unity Analytics 1.8 not working with WSA 8.1 or WP 8.1
Reproduced on 5.0.0f1, 5.0.0f4;
Repro steps:
1. open project "AsUnityAnalytics.zip";
2. try to build to WSA (8.1 or phone 8.1) platform;
3. errors occur in the console:
Reference Rewriter: Error: type `System.ApplicationException` doesn't exist in target framework. It is referenced from UnityEngine.Cloud.Analytics.dll at System.Void UnityEngine.Cloud.Analytics.TestWWW::setResponse(System.Int32,System.String,System.Byte[],System.String,System.Collections.Generic.Dictionary`2<System.String,System.String>).
UnityEngine.Debug:LogError(Object)
PostProcessMetroPlayer:RunReferenceRewriter(WSASDK, String, String, String, String) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessMetroPlayer.cs:334)
MetroPlugin:RunReferenceRewriter(String, String, String) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/MetroPlugin.cs:148)
PostProcessMetroPlayer:PostProcessSDKSpecific(WSASDK, BuildTarget, BuildOptions, String, String, ProjectImages, LibraryCollection) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessMetroPlayer.cs:890)
PostProcessMetroPlayer:PostProcess(BuildTarget, BuildOptions, String, String, String, String) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessMetroPlayer.cs:597)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment