Search Unity

  1. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice
  2. Ever participated in one our Game Jams? Want pointers on your project? Our Evangelists will be available on Friday to give feedback. Come share your games with us!
    Dismiss Notice

MacOS Catalina - Blank error appears with no info.

Discussion in 'OSX' started by turdann, Oct 16, 2019.

  1. turdann

    turdann

    Joined:
    Dec 29, 2012
    Posts:
    33
    Hello,

    After updating from Unity 5.6 to 2017.4 and our OSX to Catalina, it seems we're receiving an empty error in the console. There's no info related to it, double click it doesn't do anything either.

    unnamed.png

    Any way we could check what's going on with this and how to fix it?

    Most of our project is coded in Unityscript and I found this issue which won't be fixed... might it be the very same issue?

    Should I just downgrade to Mojave?
     
    WermHat likes this.
  2. archer1013

    archer1013

    Joined:
    Apr 21, 2015
    Posts:
    1
    We have encountered the same problem. Downgrade to Mojave will not be approved by Apple.
     
    WermHat likes this.
  3. turdann

    turdann

    Joined:
    Dec 29, 2012
    Posts:
    33
    Do you mean to downgrade to Mojave so Apple accepts the update, or that Apple is no longer accepting builds coming from Mojave? (I find the latter unlikely, but you never know.. so better be safe and ask to avoid confusion)
     
  4. ChefCrazy

    ChefCrazy

    Joined:
    Jun 23, 2018
    Posts:
    1
    Xcode updated to the latest would be allright
     
    WermHat likes this.
  5. homenetgames-jacek

    homenetgames-jacek

    Joined:
    Jun 8, 2015
    Posts:
    11
    This blank error happens for us too on Catalina with Unity 2017.4.33f. It happens only for projects with UnityScript (js) files. It works for C#-only projects. I reported a bug to Unity, no response yet.

    I pulled out of the closet my old Mac with macOS 10.13.6 High Sierra and I was I able to build my old project with Unity 2017.4.33f for both iOS and OSX. Then I built iOS project / OSX package on newer Mac with up to date macOS/XCode.
    But that way you need 2 Macs.
     
    Greg_Littlefield and WermHat like this.
  6. turdann

    turdann

    Joined:
    Dec 29, 2012
    Posts:
    33
    I'm actually building the xcode project directly on PC and exporting it to our mac at the moment... :/
     
    WermHat likes this.
  7. booferei

    booferei

    Joined:
    Sep 29, 2016
    Posts:
    14
    Apparently, this Unity bug will not be fixed.

    RESOLUTION NOTE (FIX VERSION 2020.1):
    Won't be fixed until 2017.4 end of life​
     
    WermHat likes this.
  8. strobegen

    strobegen

    Joined:
    May 24, 2012
    Posts:
    8
    got same error with 2017.4.34f1
     
    WermHat likes this.
  9. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    This bug is in 2017.4 LTS. The entire point of the LTS system is to prevent critical, workflow-destroying bugs like this. How in the world is Unity refusing to fix this?
     
    ina likes this.
  10. excalith

    excalith

    Joined:
    Dec 18, 2013
    Posts:
    15
    - Updating OS breaks my project
    - Updating Unity breaks my project
    - I will also break my project to fullfill its destiny

    Well, I would love to hear the reason why they are refusing to fix this issue while LTS support continues
     
    WermHat likes this.
  11. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Does anyone have a workaround?
     
  12. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    Does your project happen to have old .js code in it ? We have seen cases where having old unity script code in the project will result in this issue.
     
    WermHat likes this.
  13. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Thanks for chiming in. Yes, that's exactly the case. Our project makes heavy use of .js which is precisely why we are using 2017.4 LTS. We had been counting on this LTS to carry us through for many more months.

    Our project is inoperable on Apple's current OS. We were under the impression that LTS exists to fix scenarios just like this.
     
    Last edited: Dec 12, 2019
  14. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Is there an explanation for why this doesn't warrant a fix? We would be so grateful for some help with this!
     
    Last edited: Dec 17, 2019
  15. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    I will look into what it will take to resolve this issue for 2017.4 LTS
     
    HonorableDaniel and WermHat like this.
  16. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Thank you so much. As it stands now, all the major 2019 hardware releases — the 16” MBP, the Mac Pro — which can’t be downgraded to Mojave are off the table for anyone who still has projects that rely on .js.

    If you can give .js life on Catalina it will be a huge deal and will likely preserve compatibility until long after the 2017 LTS cycle has ended.
     
    Last edited: Dec 28, 2019
  17. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    May I ask if you have any updates on this? Thank you!
     
  18. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150

    Just getting back from holiday break :D So I shall look into this this week.
     
    WermHat likes this.
  19. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Thank you and welcome back!
     
  20. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Any luck so far? :)
     
  21. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    I will update the thread when I have an update :D
     
    Richardbmth and WermHat like this.
  22. Richardbmth

    Richardbmth

    Joined:
    Mar 5, 2016
    Posts:
    30
    We have the same problem. Our project was fine last year on Unity 2017.4.32. Upgraded to Unity 2017.4.36 last week and the empty console error appeared. Downgraded thinking it was the update and it still has the same problem. Had no idea that it was actually the MacOS update which was the culprit. I think we might be more careful about updating the MacOS from now on :eek:

    Frustratingly we can't just publish from Windows as iOS, as the published files won't build from XCode. Something to do with a plugin I think which causes a FrameworkSecurity error linker error.

    I just hope this won't be low priority as it's makes publishing a maintenance update tricky for us.
     
    WermHat likes this.
  23. DurmusAli

    DurmusAli

    Joined:
    Feb 25, 2014
    Posts:
    4
    Any update? Just upgraded to Catalina this weekend and now I am having the same error.
     
    WermHat likes this.
  24. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    I am working through it :) have not forgotten this.
     
    WermHat likes this.
  25. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    We appreciate your advocacy!
     
  26. DurmusAli

    DurmusAli

    Joined:
    Feb 25, 2014
    Posts:
    4
    Thank you for your works. Is there any estimated time for this? A day, a week, a Month? So we can adjust ourselves according to that.
     
    WermHat likes this.
  27. Greg_Littlefield

    Greg_Littlefield

    Joined:
    Jun 5, 2018
    Posts:
    2
    I just ran into the same problem yesterday, and indeed it was because of JS files.

    I use Unity 2017.3.1 (long story short we're stuck with this version of Unity at work) and yesterday we had to updgrade our mac to Catalina (10.15.2), and Unity would no longer build the project; throwing out and empty error. And indeed it was because of a couple old Javascript files we had in there! We removed those and now it builds fine. (we'll have to rewrite these scripts in C# but that's ok) I'm glad I found this thread, I would never have found that by myself.
    Thanks for the help guys! :)
     
    esg-odeoliveira and WermHat like this.
  28. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
  29. kintz_09

    kintz_09

    Joined:
    Apr 9, 2014
    Posts:
    3
    I am having the same issue on my 2016 Macbook Pro 15". In late December 2019 I built our iOS project without any issues running Unity 2017.4.35f1. In January 2020 I updated my OS to Catalina. Today is the first time I've opened this project since updating the OS and I am now receiving this empty error unable to play or compile. I then upgraded to Unity 2017.4.36.f1 and I have the same issue. Our project is pure C#.
     
    Last edited: Feb 5, 2020
  30. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    Are you sure you don't have any js files in your project? including plugins?
     
  31. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    The Issue Tracker now shows "Planned for 2017.4." Would it be right to assume that it's now a question of when, not if?
     
    Last edited: Feb 14, 2020
  32. gtrcrazynik

    gtrcrazynik

    Joined:
    Dec 21, 2019
    Posts:
    7
    Faced with a similar problem, how to solve it?
     
  33. cosmos0

    cosmos0

    Joined:
    Feb 21, 2020
    Posts:
    2
    I had the same problem.
    My Unity Version is 2017.4.35
    Deleted all the files containing "*.js" from the project and it worked normally.
     
    WermHat likes this.
  34. arslan-arshad-ali-68

    arslan-arshad-ali-68

    Joined:
    Aug 18, 2015
    Posts:
    4
    .JS files are the issue. Unity LTS seems to be joke! Go Back to Mojave or
    convert JS files to .cs or wait for unity to release an update for 2017.4.. Unity and Mac are not getting along so nicely i guess!
     
  35. arslan-arshad-ali-68

    arslan-arshad-ali-68

    Joined:
    Aug 18, 2015
    Posts:
    4
    Yes there should be some intimation
     
  36. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    LTS 2017.4.37f1 came out a week ago with no fix. Hopefully the next one...
     
  37. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Very sorry to bug, but any chance there's a status update on this? 2017 LTS is nearing EOL so we're getting nervous that this might never come to fruition.
     
  38. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    I do apologize I have not lost sight of this :D the main issue here is that boo scripts are not supported any longer, and the reason you get this issue on 10.15 is the boo compiler is 32bit which as you know macOS 10.15 no longer supports :( which is why you get the blank error and stuff doesn't work. We have to figure out how to make this work.
     
    WermHat likes this.
  39. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Sounds very complex! I really appreciate the update. The main thing we're nervous about is the possibility that you might just give up on it. Are you able to confirm that the fix will definitely be arriving to 2017 LTS at some point, even if that time is far down the road?
     
  40. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    @WermHat I have a question what prevents you from migrating these .js scripts to c# ?
     
  41. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    We have hundreds of projects built entirely in .js. Migrating would be insurmountable. Eventually these projects will die, but .js compatibility with 64 bit Mac OS would buy years of additional life.
     
  42. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Looks like we got another LTS 2017 update today, and we're technically past the 2 year mark now. I hope you aren't planning on pulling the plug on 2017 before this fix can ship? :)
     
  43. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    It will be in the next 2017.4 update :)
     
    WermHat likes this.
  44. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    You're a hero!!
     
  45. WermHat

    WermHat

    Joined:
    Jul 13, 2012
    Posts:
    86
    Can anyone please confirm if this made it into the 2017.4 update yesterday? I’m back on Mojave because of the issue so I can’t check.
     
  46. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    It missed that update do to some internal build issue so it will land in the next one! I can assure you it will be in an update before we end support for 2017.4.
     
    WermHat likes this.
  47. SkobbejakGames

    SkobbejakGames

    Joined:
    Jun 3, 2016
    Posts:
    396
    Hi, when is the planned release date for the next 2017.4 LTS release?

    I just got this error now as well after updating to Catalina, have a bunch of bought plugin scripts in .js and cant convert them all to C# in feasible time as I would need to contact each plugin developer about multiple scripts.
     
  48. JuJuCoder

    JuJuCoder

    Joined:
    Dec 10, 2013
    Posts:
    24
    I am interested in this one as well. When the fix is released? or at minimun it should say how to fix it.
     
  49. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    150
    it will be fixed in the next 2017.4 release. With that said as I mentioned above removing js files from your game solves the issue.
     
    ina likes this.
  50. JuJuCoder

    JuJuCoder

    Joined:
    Dec 10, 2013
    Posts:
    24
    We have lots of old assets from asset store. I do not know which files to remove. Do you have any help how to locate those files that are causing this? It could be any .js file?
     
unityunity