Visual Studio Code on Mac Sierra 10.12.5 - visual-studio-code

I am using a Mac OS Sierra 10.12.5 (16F73)- Macbook Pro touch pad. I have tried running Visual Studio Code to no avail. Nothing happens, no error message, nothing. It just won't start. I have read articles or using Mac Archive Utility to unzip the downloaded zip file, i still can't get it to run. Has anyone got a solution to this?
Many thanks!

I'm also using Mac OS 10.12.5 with a Macbook Pro and recently installed vscode.
Try to redownload the file or maybe restart your computer, you shouldn't have any problems with the installation.

Related

VS Code Window not responding Mac OS 10.14.6

I get an error popup "The window is not responding" at startup.
Asks to close, wait or reopen. Nothing seems to happen after, just the same windows pops up.
This started after I rebooted the computer after first install. I was able to write some practice files but now it wont go past this window.
Ive tried uninstalling using Appcleaner, deleting everything, clean OS install as well.
Running Mac OS 10.14.6 Mojave on an Intel MBP
Please help, I'm just getting started with this.

Mac M1 chip machine, Mac OS BigSur Version 11.5.1 having problem with eclipse app. Its not opening after restarting machine

I Installed eclipse on my new mac m1 chip machine, It was working fine until I restart my machine. After restart the machine, the eclipse app is not opening also no error is shown in the display..
I am trying to open the app in terminal I am getting the following error
rosetta error: /var/db/oah/223263137464320_223263137464320/27e2cf6e452a44ee1a3ccc20e0409d562f65d18f27dd9ff3ebd552b78e52a4e3/eclipse.aot: attachment of code signature supplement failed: 3 Trace/BPT trap: 5
the solution giving in this is to upgrade the OS, but I already upgraded to the new OS version.
I can't find a solution anywhere, even in Apple forum sites
I faced a similar issue today. In my case, I'm using Anypoint Studio, which is built on top of Eclipse 4.19. After updating the OS, it worked again.

Unity 2019.3.3f1 crashes under Mac OSX Catalina and Mojave

I'm trying to run a github repo that can found in here. with Unity 2019.3.3f1 . Which works fine on Windows10 but instantly crashes on Mac OS Mojave and Catalina. This is the first time that I've came across a Unity error like this, any ideas would really helpful :))
Error message: link
This error persists since Unity 2019.3.0 and is still there in the latest version (2019.3.13). So we are unable to upgrade and have to stick with Unity 2019.2.21. We will consider switching to the Unreal Engine for our next project.

Visual Studio Code Won't Run on Mac 10.8.5

I just downloaded a fresh copy of VSCode-darwin.zip from https://code.visualstudio.com/, upzipped, dragged to my Applications directory, and tried to run it. After the initial "Verifying Visual Studio App" window ran, the dock icon bounced a few times then vanished and the app didn't load. Subsequent attempts yielded the same result. Anyone else experience this? Any known conflicts or dependencies for 10.8.5?
VS Code does not support Mac OS X 10.8 and below. We have a dependency to Electron and updated recently which caused this.

android emulator launch failed. emulator64-arm : BAD CPU Type in executable

Yesterday I decided to start developing Android in my mac (Snow Leopard 10.6.8) 32-bit.
Everything was ok, i also imported my workspace which i worked in Linux for months. I open a project and compiles perfectly.
When i try to run the project it gives me this error :
"...android/sdk/tools/emulator64-arm : BAD CPU Type in executable"
I am using eclipse juno for mobile developers and downloaded the latest android sdk for mac
It looks like a 32-bit 64-bit issue. But i couldnt solve it yet.
Anyone had the same issue ?
I already found the problem.
Under the directory, android-sdk/tools/, i deleted every executable related to 64-bit system. Those files are :
emulator64-arm , emulator64-x86 etc.
Then relaunch the project and now it is working like a charm.
Hopefully this helps to anyone who suffers from the same issue.