Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.1.0f3
Issue ID
940806
Regression
No
Migrating project from Mac to Windows disallow switching from Android to Standalone
How to reproduce:
1. Create new project on Mac
2. Change Build Setting to Android
3. Open the same project on Windows
4. Try to change Buil Settings to Standalone
Expected result: Unity allows changing Build Settings from Android to Standalone
Actual result: Unity disallow changing Build Settings from Android to Standalone. Appears message: "Standalone Player is not supported in this build. Download a build that supports it".
Reproduced with: 5.6.3f1, 2017.1.0f3, 2017.1.0p3, 2017.2.0b6, 2017.3.0a3
Workaround: Switch to standalone platform on Mac before migrating to Windows
Note: If you don't have installed Android target support, then Unity automatically switch platform to Standalone
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
This appears to be due to keeping the Library folder in tact while moving from mac to windows. This is not supported behavior for more reasons than build-settings getting stuck. If using version control (and thus excluding the Library folder), this issue will not happen.