koobas.hobune.stream
Unity 2017.3.1f1 crash after Developer Tools on Mac request access
I am currently developing an app that uses firebase 4.5.0 API with user authentication and unity store subscription for iOS and Android. We've also installed JWT library with VS for security issues. After some implementation, this window started appearing frequently with the message "Developer Tools Access needs to take control of another process for debugging to continue." :
The thing is:
1.If I cancel Unity Crashes and every time I open Unity again and it needs to compile a change in script, this window appear again.
2.If I continue, every time I need to compile Unity crashes.
When we open Unity again, it is compiled and we can test, but it is painfull to crash unity every single time we change something in code.
Unfortunately, I couldn't solve it yet, I'm developing now in windows because of that, and only using the XCode build for mac.
It is still happening time to time, but not as frequent as it was. I cannot say that the workaround below fixed the issue, but it does ease the pain a lot!
What I did:
Update Catalina to latest
Uninstall all apps you use with Unity - including Unity Hub
Reinstall all apps back again (if possible, use the latest stable Unity release - just in case)
I think this is kind of a workaround to set required permissions properly after updating Catalina
I think the issue is related to new Catalina update requiring more permissions for safety and did not consider already installed apps in a proper way - having trouble with even Adobe suite even after reinstalling them. Catalina is garbage for me right now.
Currently I am using:
$$anonymous$$acOS Catalina 10.15.3
Unity 2019.3.0f6
I'm having the same issue, for me it is 100% of the time as soon as I click Continue. I just updated to Catalina when this was happening, never had an issue before. I'm using 2018.4.18f1 which I installed fresh, however, I did not reinstall hub, so I will try that next. If that doesn't work, I'll try to update to 2019 unity and see if that helps. For what it's work, if I don't give it access (just leave the window up), I can still run my game, but I guess I can't debug this way? I'll update if anything changes, but wanted to post it here with my info so Unity can take a look.
$$anonymous$$acOS Catalina 10.15.3 $$anonymous$$acBook Pro (Retina, $$anonymous$$id 2012) 2.3 GHz Quad-Core Intel Core i7 16 GB 1600 $$anonymous$$Hz DDR3 NVIDIA GeForce GT 650$$anonymous$$ 1 GB Unity: 2018.4.18f1
Open the Terminal (Mac) and type:
sudo /usr/sbin/DevToolsSecurity --enable
Done! This solved the issue for me.
I've noticed that all the instances of this freeze (crash) happened while I was using Animation window. Note that I do not use Animation window 80% of the time.
@ameer418 Same here! I've noticed every time I'm using the Animator Window it freezes (crashes) my Unity. I can't even edit my Blend Trees or anything without it crashing Unity.
I've enabled Developer mode in my Ter$$anonymous$$al($$anonymous$$ac) and it still crashes.
Hey, it looked like it solved the issue, but actually it produces another problem for me. https://stackoverflow.com/questions/62152562/enabling-developer-tools-access-crashes-unity-and-activity-monitor
It is still happening time to time, but not as frequent as it was. I cannot say that the workaround below fixed the issue, but it does ease the pain a lot!
What I did:
Update Catalina to latest
Uninstall all apps you use with Unity - including Unity Hub
Reinstall all apps back again (if possible, use the latest stable Unity release - just in case)
I think this is kind of a workaround to set required permissions properly after updating Catalina
I think the issue is related to new Catalina update requiring more permissions for safety and did not consider already installed apps in a proper way - having trouble with even Adobe suite even after reinstalling them. Catalina is garbage for me right now.
Currently I am using:
MacOS Catalina 10.15.3
Unity 2019.3.0f6
This is happening frequently in Catalina (10.15.3) with Unity 2019.3of6. Worse, the hangup is so bad that force quit doesn't do anything. The app icon goes away but the app itself stays open. Would love to figure out how to avoid this. There's no obvious set of behaviors triggering it.
OS: MacOS Catalina 10.15.3 CPU: 2.5
GHz Quad Core Intel i7
Graphics : AMD + Radeon R9 M370X 2 GB + Intel Iris Pro 1536 MB
UPDATE: Guys, I'm not gonna copy and paste here the whole thing since it's very long, but here's the link to the stackoverflow with my question and my answer. Maybe it will help you somehow.
------- Old version of this message:
Hey guys, I'm facing the same issue.
I'm facing the Developer Tools problem since yesterday. I use:
Unity (several different versions, e.g. 2018.4.23),
Jetbrains Rider (updated today to 2020.1.3, yesterday 2020.1.2)
macOS Catalina 10.15.5
I was refactoring some stuff and Developer Tools asked me for the access: Developer Tools Access needs to take control of another process for debugging to continue. Enter your password to allow this...
Since then, two things are happening.
If Developer Tools Access is enabled (also tried doing this through sudo /usr/sbin/DevToolsSecurity --enable command) nearly every time when I'm changing something in code, Unity stops working (loading wheel present) and I can't turn its application off. I tried using Activity Monitor, it doesn't show any activities. I can only see the loading wheel.
I even tried killing the Unity process through kill unitypid, it "kills" the process since it's not present on the processes list, but I still can see it on my desktop, being just as down as before.
Checking Unity logs, I can see it stops on:
Begin MonoManager ReloadAssembly
custom-attrs.c:1250: (null)
assembly:/Applications/Unity/Hub/Editor/2018.4.17f1/Unity.app/Contents/Managed/UnityEngine/UnityEngine.CoreModule.dll type:UnityException member:(null) signature:<none>
Stacktrace:
Native stacktrace:
0 libmonobdwgc-2.0.dylib 0x00000001460b4976 mono_handle_native_crash + 242
If Developer Tools Access is disabled, the application asks me a few times to enable it. After pressing Cancel a few times, Unity crashes and turns off and gives me the ability to send log error to Apple with the exception:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
Don't really know what to do. I tried updating Rider, Catalina, installing a new Unity version.
Your help would be much appreciated!
That's weird, I've had this problem in different Unity versions on $$anonymous$$ac but I always use the sudo /usr/sbin/DevToolsSecurity --enablesolution, and it works, maybe this is stacked with a different problem?
For me, enabling devtools through command always locks the Unity even kill command does not work and all I could do is to restart OS. For this reason, I prefer cancelling the permisson, which only crashes Unity to desktop ins$$anonymous$$d.
After many tests I think the reason may be I'm using external repositories in my project, I'm checking it now. @excalith do you also do it?
Hey there, haven't tested it with external repositories with Catalina yet. But before Catalina, I have used submodules with several Unity projects without an issue. In my case, it is completely random. Happens while compiling, happens while modifying components through inspector, even happens when the app is idle. Struggled with this just 1 month before our release - it was not fun :D
Tried Rider, VSCode and just to test it out used Sublime with only syntax highlighting. It seems it is also not related to any IDE or text editor. Still happening with Unity 2019.3
I have contacted with Unity for this and reported as much data as I can provide them yet they could not reproduce this behaviour on their end. However, I do believe it is caused by $$anonymous$$acOS permissions if you updated your OS ins$$anonymous$$d of a clean install. One of my colleagues did a clean install and it is working flawless for him. I only managed to reduce the issue happening from "within a few $$anonymous$$utes" to "a few times in a week" by my answer above and it seems it did not work for you either.
Also, tried to reach Apple for this issue and they said that they have eased OS migration pain a little for major apps and Unity was not one of them so they could not help since it seems like an issue from Unity.
For this reason, I give up trying to find the cause or find a way to fix the issue at least I can live with a few crashes a week. Good luck to you!
I'm in the same situation as you are. Nothing seems to work. It has gotten so bad that I can't even use the Animator Controller without it crashing my Unity.
$$anonymous$$y case is actually complicated. I'm having some external repositories, code packages. When I'm using them as code packages, everything works normal. But when I download their repositories, everything crashes (just like I posted). $$anonymous$$y temporary solution is to use their repositories on the first place. I hope it's not too complicated, that's just how out architecture works.
But, funny thing, it works normally for me in Unity 2019.3 when a lot of people complains it doesn't work for them on this Unity version. I hope Unity will take a look at the Animator Controller. I used the same computer and configuration on April doing LD46 game, Unity 2018.4.17, and Animator Controller worked normally for me then.
Hi again @fullerfusion , I thought maybe you'll be interested in what happened in my case since the last time we talked.
I'm not gonna copy and paste here the whole thing since it's long, but here's the link to the stackoverflow with my answer. $$anonymous$$aybe it will help you somehow.
I had the same issue, I removed external dependency manager along with firebase, magically it is not asking for developer tools access. Do you have anything listed above?
Hey, I've just posted my answer with a stackoverflow link, maybe it will help you as well. https://stackoverflow.com/questions/62152562/enabling-developer-tools-access-crashes-unity-and-activity-monitor/62408952#62408952
I too, had this happen many times. It's up to the point where I save my work every 5 minutes or so, because it might just happen at any time. Very, very frustrating to use Unity at the moment. Reinstalled both the hub and Unity, but no change so far.
Model: 27-inch, 2017
MacOS Catalina 10.15.3
CPU 3,4GHZ Quad-Core Intel i5
Mem: 40 GB 2400 Mhz DDR4
Graphics: Radeon Pro 570 4GB
Unity Version: 2019.3.3f1
Hello Boaike, have you tried my fix recommendations above? I have already contacted with Unity Devs regarding this problem and they are having trouble reproducing it. However, I can tell you that with the steps above I have $$anonymous$$imized that issue into once-in-a-week from once in a half hour. Hope that helps!
Hi! Yeah I already did all your steps, but it still happens quite a lot. $$anonymous$$aybe once every 2 hours :/ I can't really tell what triggers it, either, then I'd know how to avoid it! If I can find some kind of pattern I'll report back, but for now I just send crash reports every time it happens.
Thanks for reaching out though! :)
