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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment