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
Comments (1)
-
smosh92
May 29, 2018 05:18
but i dont have a mac available. what do i do then? :\
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.