Search Unity

  1. Click here to see what's on sale for the "Best of Super Sale" on the Asset Store
    Dismiss Notice
  2. 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

2017.3 Fatal ERROR!

Discussion in 'Editor & General Support' started by renman3000, Dec 22, 2017.

  1. renman3000

    renman3000

    Joined:
    Nov 7, 2011
    Posts:
    6,534
    Hi
    I just updated to 2017.3, and tried to open up a project, but got a fatal error.

    Pop up window states:
    Code (csharp):
    1. Opening file /Users/myname/Library/Unity/cache/packages/packages.unity.com/com.unity.analytics@2.0.13/UnityEngine.Analytics.dll.meta: Permission denied
    Clearly it has to do with analytics@2.0.13.

    Not sure what to do. Re installing, 2017.2.


    Lesson, never update at the end of a major project.
     
    Last edited: Dec 22, 2017
  2. renman3000

    renman3000

    Joined:
    Nov 7, 2011
    Posts:
    6,534
    So, I just (2 hours later) re installed 2017.2, and I get the exact same error!!!!

     
  3. renman3000

    renman3000

    Joined:
    Nov 7, 2011
    Posts:
    6,534
    UPDATE:
    Ok, so I seemed to have got it working. Not sure if this is the fix, but instead of opening one of my projects for the virgin run, I created a new one, the opened one of mine (this is in older 2017.2).

    Thanks
    Any info would be helpful.
    Cheers
     
  4. zero_equals_zero

    zero_equals_zero

    Joined:
    Jun 7, 2014
    Posts:
    89
    I installed unity 2017.3 yesterday on my Pc and it worked fine.
    Opened my project there. without a hitch.

    I just installed 2017.3 on my mac and get the same error as shown above.
    Creating a clean new project works though.

    Opening an existing one doesn't. Even if it's 2017.3
     
  5. orb

    orb

    Joined:
    Nov 24, 2010
    Posts:
    2,960
    I got the same error, but not as a popup - it just showed in red in the console. Exited and opened Unity and the same project again, and everything was fine. Happens to every project made in earlier versions of the engine, but no harm seems to have befallen the assets.
     
  6. HyperNerd

    HyperNerd

    Joined:
    Jul 11, 2012
    Posts:
    1
    Same here - Had to completely roll back even my cache files in library from Time Machine to get back to working projects. Not cool...
     
  7. zero_equals_zero

    zero_equals_zero

    Joined:
    Jun 7, 2014
    Posts:
    89
    Nothing works here, I even completely uninstalled Unity, rebooted, installed again.rebooted.
    opening a new project works. An old one does't :(
     
  8. avorobjev

    avorobjev

    Joined:
    Apr 3, 2014
    Posts:
    8
    I had same error after update... On the first opening of the project there was error "Opening file ...packages.unity.com/com.unity.analytics@2.0.13/UnityEngine.Analytics.dll.meta: Permission denied", the second time it opened normally
     
  9. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    5,310
  10. zero_equals_zero

    zero_equals_zero

    Joined:
    Jun 7, 2014
    Posts:
    89
    I've tried the patch yeah.

    Nothing works.
    The old project was made 2 days ago on Pc with unity 2017.3
    It worked perfectly on my macbook.
    Then I updated my mac's unity instalment to 2017.3 and this happened.

    The only thing that works is opening projects below 2017.3: for example 2017.1 or even .2 of unity 5.5 open perfectly.
    Except 2017.3

    What does work is to create a new project, move the scripts and prefabs over.
    It's mainly a script heavy prototype project but still....

    I guess i'll have to manually push things over to a newly created project because this is too weird for me.

    Edit:
    Manually copy all items to a new project worked for me. i now can open the project I was working on. It's tedious but I have no work lost.
    I still have the other project that I created on PC a few days ago. I'll check if I can open that later this week.

    Still not sure what causes this, even I removed all previous trails of any unity installation (using appcleaner) My guess is because the project I started was 2017.3.0f3 while this installation is 2017.3.0p1 I guess there's an issue between the f & the p. But I have no idea how relevant it is.
     
    Last edited: Dec 23, 2017
  11. ExSprites

    ExSprites

    Joined:
    Nov 8, 2016
    Posts:
    1
    For your reference, here's my case, and how I fixed it.

    I just updated to macOS High Sierra 10.13.1.
    Then updated to Unity 2017. When I first open my project from version 5.6, it was successfully converted to 2017.
    Later day, once I opened my project again, I got the dialog that showing

    Opening file /Users/myname/Library/Unity/cache/packages/packages.unity.com/com.unity.analytics@2.0.13/UnityEngine.Analytics.dll.meta: Permission denied​

    When looking at the directory /Users/myname/Library/Unity/cache/packages/packages.unity.com/com.unity.analytics@2.0.13/, it showed that meta files there having only read-permission.

    -r--r--r-- 1 user group 709 Dec 6 09:07 UnityEngine.Analytics.dll.meta

    My solution is to add write permission to them using this command:

    chmod +x *.meta

    Then my project can be opened as normal.
     
    mikolajewskip, aliens9889 and Peter77 like this.
  12. UnityTester33

    UnityTester33

    Joined:
    Dec 17, 2016
    Posts:
    7
    what helps me:
    - try open/error/quit/try open/error/quit/type open - finally open!
     
    Deleted User and Divunity like this.
  13. quijibo

    quijibo

    Joined:
    Aug 19, 2016
    Posts:
    1
    I as able to get around this by removing the cache location from disk entirely.

    sudo rm -rf ~/Library/Unity/cache/packages/packages.unity.com/com.unity.analytics@2.0.13
     
  14. akasurreal

    akasurreal

    Joined:
    Jul 17, 2009
    Posts:
    440
    This works but the proper command is:

    chmod +w *.meta
     
    elenzil, Nicolas1212 and RPGia like this.
  15. huhund

    huhund

    Joined:
    Aug 14, 2014
    Posts:
    8
    Same issue here. I'm on mac 10.12.6. Reopening project works. :/
     
  16. Divunity

    Divunity

    Joined:
    Dec 29, 2016
    Posts:
    6
    You are the boss !!!! .................. :D
    Worked 100%
     
    UnityTester33 and Deleted User like this.
  17. Rithy-Jim

    Rithy-Jim

    Joined:
    Nov 10, 2012
    Posts:
    18
    I solve this problem by changing permission of the folder "packages.unity.com" to read & write and apply to enclosed items.
     
    jerry2157 and TORT60091 like this.
  18. TORT60091

    TORT60091

    Joined:
    Jun 30, 2017
    Posts:
    1
    It's work. Get Info > Sharing&Permissions. (for mac users)
     
    Last edited: Jan 12, 2018
    jerry2157 and bunnyboom like this.
  19. Nicolas1212

    Nicolas1212

    Joined:
    Dec 18, 2014
    Posts:
    139
  20. arfish

    arfish

    Joined:
    Jan 28, 2017
    Posts:
    275
    IMO version 2017.3.0f3 should never had been made public available. It have introduced so many weird errors.
    First it can´t load the same version of Streaming Assets Bundles in the Editor as in the builds.

    Builds for Android, and launched on Android 8.0 renders the objects wrong if the Bundle was built with a previous version of Unity, like version 2017.2. On the other hand, if you try to load bundles build with 2017.3, it´s own Editor crashes with fatal error. This is however not reproduced on all Asset bundles, some very small ones can work, others not. But the not working ones are at least consistent not working.

    There are no logged build errors what so ever, neither on the Asset Bundles, nor on none of the builds. It just fails on run.

    And when the app at last loads and run smoothly on Android 8.0, then it fails when launched on earlier version of Android phones, like 6.0.

    And there are nearly impossible to make the Editor connect and debug the code while it´s running on the device. If I´m lucky, the Editor can connect to the device once, but it can never reconnect again without a complete relaunch of the Editor.

    I´m not a big fan of downgrading to earlier versions but with 2017.3 I´m running out of options.

    This is on macOS 10.12.6 and Android Studio 2.3, as well as Windows 10.
     
    Last edited: Jan 16, 2018
  21. bunnyboom

    bunnyboom

    Joined:
    Sep 17, 2015
    Posts:
    3
    It 's ok!!!!

    Thank you very much...
     
  22. SinoSD

    SinoSD

    Joined:
    Jun 29, 2017
    Posts:
    1
    I've had the same issue, the way I resolved it was to delete the library folder that is part of the Unity project. When you open scene again Unity will re-create the library folder.
     
unityunity