Search Issue Tracker
By Design
Votes
0
Found in
5.4.0b5
Issue ID
769512
Regression
No
Force Single Instance works only when launching app file but you can still open new instance via Contents/MacOS/appname
Force Single Instance works only when launching app file but you can still open new instance via Contents/MacOS/appname
1. What happened
Force Single Instance works only when launching appname.app file but you can still open new instance via appnema.app/Contents/MacOS/appname
2. How we can reproduce it using the example you attached
1. Set "Force Single Instance" in Player Settings for Standalone.
2. Build & Run the app.
3. If you click on app again - it will show current running window as expected.
4. If you go to and run appname.app/Content/MacOS/appname it will open new instance.
RESOLUTION: By design: appname.app/Content/MacOS/appname is not end-user visible path, so opening it directly is not supported.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment