In Unity 4.5.0f6, I get an exception building for Windows Store:
Error building Player: NullReferenceException: Object reference not set to an instance of an object
Build Settings:
Windows Store Apps
XAML C# Solution
SDK 8.0
No other checkboxes checked
The above error is the only line I get. Everything was fine in Unity 4.3. Which additional information can I provide to help you with this?
Hey Tomas,
please find attached the editor logs and DxDiag.
1643712–102101–$MetroErrorBuildingPlayer.zip (26.8 KB)
Blind guess, try going to Player Settings, and recreate certificate by click “Create” button.
Nice shot, the certificate was missing indeed! However, the error still persists… New logs attached.
1643737–102108–$MetroErrorBuildingPlayer2.zip (16 KB)
It would be easier to tell what’s happening, if you submit a bug report with your project. Log file doesn’t show any specific issue.
The log shows same NullReferenceException, so do as Kazimieras suggested, submit a bug
I got the same issue. Switching to 8.1 solves it, but that’s not what I want to do (want to support both 8.0 and 8.1).
By the way, I have both VS2012 and VS2013 installed as well as a system that was upgraded from 8.0 to 8.1 (a long time ago) and was able to successfully build everything with Unity 4.3.4.
Found the error: the “Override Background Color” toggle causes it. Disabling it makes the build work as normal.
The fix for this issue is available in a patch “4.5.1p2”. A patch can be found here:
Latest patches: 4.3.7p4: https://unity3d.com/unity/qa/patch-releases?version=4.3 4.5.5p5: http://unity3d.com/unity/qa/patch-releases?version=4.5 4.6.9p4: http://unity3d.com/unity/qa/patch-releases?version=4.6 5.0.3p3:...
Reading time: 48 mins 🕑
Likes: 290 ❤
Hmph, I think that fix will be only available in 4.5.1p3, not 4.5.1p2.
I got the same issue in the lastest Unity 4.6.3
This issue was not related to iOS in any way, I suggest you open a new thread
Apologies, I didn’t notice when I posted this was in the Windows section - so I’ve deleted my post. I’ve since found that 4.6.3p1 has probably fixed my problem, and so far so good.