Search Issue Tracker

Active

Votes

5

Found in

5.3.6p6

Issue ID

837810

Regression

No

[OSX] Enabling UnityPurchasing on Mac standalone causes builds to hang when quitting them

IAP

-

When closing an OSX build after calling UnityPurchasing.Initialize(), the build doesn't close immediately, but stays in the Dock for around 10 seconds and sometimes even has to be terminated to exit.

Steps to reproduce:
1) Open the attached project.
2) Build And Run on on OSX.
3) When the build launched, press Command+Q.

Expected result: the app quits immediately.
Actual result: the app hangs for ~10 seconds before exiting.

Commenting out the UnityPurchasing.Initialize() call makes the issue go away.

Reproduced on:
5.5.0b7, 5.4.1p4, 5.3.6p7, 4.7.2f1

Tested with macOS 10.12 and OSX 10.11.6.

Comments (4)

  1. 1dbaae787b795d67af7ebbfd0bf5553a?d=mm

    UNSH

    Dec 09, 2018 21:40

    Still a problem in unity 2018.2.14f1

  2. A9ddb895d80d87467bb0893bee49a25b?d=mm

    sidebolt

    Nov 06, 2017 16:47

    The solution posted below by Gerold_Meisinger works in 2017.1.2

  3. A9ddb895d80d87467bb0893bee49a25b?d=mm

    sidebolt

    Nov 06, 2017 16:45

    This is still a problem in 2017.1.2

  4. 173610c61fbcaeaf583f9411390e5113?d=mm

    Gerold_Meisinger

    Feb 01, 2017 08:51

    We worked around this issue in 5.3.6f1 by calling:
    #if UNITY_STANDALONE_OSX
    System.Diagnostics.Process.GetCurrentProcess().Kill();
    #endif
    but this no longer works in 5.5.0p3.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.