Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.2.X, 2017.3.X
Won't Fix in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.1f1
Issue ID
910488
Regression
Yes
[UWP] WWW does not read a local file in UWP build when .NET
Steps to reproduce:
1. Open the attached project(localWWW.zip)
2. Open the Assets/localWWW.unity scene
3. Switch platform to Windows Store
4. Go to Pictures, create a folder, create a text file with any content in that folder
5. Update the script in the repro project to point to the text file you just created
6. Build for WSA Universal 10 SDK, Build type - XAML
7. Open Visual Studio solution
8. Update the Package.appxmanifest file capabilities. Add the Pictures library capability, so you can access the file created in step 4
9. Deploy on local machine (Debug)
10. Observe the Output console, both calls to WWW fails
Expected result: WWW should read the local file
Actual result: WWW does not read the local file
Note:
In Editor works fine
Reproduced with: 5.5.1p4, 5.5.3p3, 5.6.1f1, 5.6.1p1, 2017.1.0b5
Not reproduced with: 5.5.1f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
- A memory leak occurs in Play mode when using Direct3D12 Graphics API
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when rendering 60 real-time lights in the far distance
Add comment