You should now be good to go and can now debug your functions. We can then check that the Azure Storage Emulator is running again by checking the status and we can see IsRunning is now True: If you see IsRunning as False like above then you’re going to need to initialize and start the Azure Storage Emulator by running the commands below: To check if it’s started, run the command below: iOS or Android You bet React Native No sweat Windows Certainly. I resorted to the classic turn it off and on again and that still didn’t fix it.Įventually, it occurred to me to check that the Azure Storage Emulator was started and I found that it wasn’t. App Center analyzes your code to suggest a build configuration. I found that all services were started and that even with the firewall disabled, I still had the issue.

I figured that this may be a firewall issue or a problem with one of the services that wasn’t started so I tried to eliminate those causes. I figured I’d write up the solution for the next person who has this problem. : No connection could be made because the target machine actively refused it.”Īfter a Google search, I didn’t find much on the error message.

: No connection could be made because the target machine actively refused it. “The listener for function 'MyFunction' was unable to start. When debugging one of my Azure Functions in Visual Studio 2017, I got the error below:

Azure storage emulator for mac