Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
1
Found in
2017.3.0f2
Issue ID
979704
Regression
No
Assembly Definition Files Break UWP Build
How to reproduce:
1. Download attached project file and open "TestScene".
2. Change Platform to UWP.
3. Press Build
Expected result: Build finishes successfully
Actual result: When adding Assembly Definition Files to a project, it breaks the ability to do successful UWP builds
Reproduced with: 2017.3.0f3, 2018.1.0b1
--------------
Fixed on: 2017.3.1p2, 2018.1.0b3, 2018.2.0a1
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
- The build size is larger when Models have Animation Type set to Generic
- Error "ArgumentException: Both 'ok' and 'cancel' strings are null or empty" logged when User is trying to create circular dependencies in UI Builder Hierarchy
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
herra_lehtiniemi
Jan 05, 2018 13:52
I noticed that the assembly references that the compiler warned about came from Post Processing Stack 2 (beta). If I removed those files (.asmdef), then Post Processing Stack v2 would not compile anymore (lost of warnings about missing assembly definition files and namespaces).
So for those looking for a workaround with Post Processing Stack v2, just remove the stack (and the related .asmdef files) and it will compile correctly.
I haven't tested with version 1 yet, if it would work better.
herra_lehtiniemi
Jan 05, 2018 13:28
Is there currently any workaround on this?