Skip to main content
Solved

MacOS silicon version bug

  • June 18, 2023
  • 2 replies
  • 36 views

oliver.morris
Contributor
Forum|alt.badge.img+14

Trying to install on my mac, silicon version. Have uninstalled one version completely. New version still has the same bug.

 

When loading a package, going to database connections etc:

 

Failed to install web service '/Users/xxx/Library/Caches/Safe Software/FME/Packages/23319-macosx-aarch64/PackageFiles/safe-lab.genai/web_services/OpenAI.xml'. Reason: Unable to read from file '/Users/xxx/Library/Caches/Safe Software/FME/fme_publicKey.fmeks', No such file or directory (Code 2)

 

I checked for the folder and it doesnt exist.

 

Best answer by nampreetatsafe

Hi @oliver.morris​ !  I see you've posted on the FME Hub too.  I know it was suggested that you open up a support case with us, but I don't see one in our system.  I'll try to share some findings here.  Our team managed to fix the cause of the issue which should no longer occur in the latest build.  However, if you encountered the problem in a previous build it may persist even when installing a new build of FME.  To fix this you can either run the following command:

  • requires admin access (the same as installing FME does) and 
  • changes the ownership of everything in the Safe Software folder back to the proper user
sudo chown -R "$USER:" ~/Library/Caches/Safe\ Software/

...or if you want to reinstall FME, ensure the ~/Library/Caches/Safe\ Software  is deleted before trying to install it again.

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

nampreetatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • 383 replies
  • Best Answer
  • June 28, 2023

Hi @oliver.morris​ !  I see you've posted on the FME Hub too.  I know it was suggested that you open up a support case with us, but I don't see one in our system.  I'll try to share some findings here.  Our team managed to fix the cause of the issue which should no longer occur in the latest build.  However, if you encountered the problem in a previous build it may persist even when installing a new build of FME.  To fix this you can either run the following command:

  • requires admin access (the same as installing FME does) and 
  • changes the ownership of everything in the Safe Software folder back to the proper user
sudo chown -R "$USER:" ~/Library/Caches/Safe\ Software/

...or if you want to reinstall FME, ensure the ~/Library/Caches/Safe\ Software  is deleted before trying to install it again.

 


oliver.morris
Contributor
Forum|alt.badge.img+14
  • Author
  • Contributor
  • 176 replies
  • June 28, 2023

Hi @oliver.morris​ !  I see you've posted on the FME Hub too.  I know it was suggested that you open up a support case with us, but I don't see one in our system.  I'll try to share some findings here.  Our team managed to fix the cause of the issue which should no longer occur in the latest build.  However, if you encountered the problem in a previous build it may persist even when installing a new build of FME.  To fix this you can either run the following command:

  • requires admin access (the same as installing FME does) and 
  • changes the ownership of everything in the Safe Software folder back to the proper user
sudo chown -R "$USER:" ~/Library/Caches/Safe\ Software/

...or if you want to reinstall FME, ensure the ~/Library/Caches/Safe\ Software  is deleted before trying to install it again.

 

@nampreetatsafe​ thank you for you help, ran this script and now all it good on my mac. Thank you, I look forward to giving FME on silicon a real spin.🚀