It does not work on Microsoft Windows

[HenriMorlaye]

I guess it's not a priority, just to make sure it's recorded somewhere.

** (FunctionClauseError) no function clause matching in Mix.Appsignal.Helper.map_arch/1
mix_helpers.exs:103: Mix.Appsignal.Helper.map_arch('win32')

To do

@tombruijn: AppSignal team, see my comment for a to do list: #36 (comment)

[arjan]

@thijsc is windows supported at all for Appsignal?

[thijsc]

No, and we're not planning Windows support. The integration should work without breaking anything though. In Ruby there are empty implementations of every method if the extension is not loaded.

[tombruijn]

As mentioned before and in our documentation (http://docs.appsignal.com/support/operating-systems.html#microsoft-windows) we currently have no plans to support Windows because we don't hear a lot from people that use it. But let us know when you do use it so we know if there's a lot of demand for it.

Making sure you can run AppSignal on a non-supported architecture without it crashing the app will be handled in #89

Closing

[HenriMorlaye]

Hi, it does not work on Bash For Windows either (Ubuntu 16.04 shipped with Windows 10 Creators Update). Elixir and Phoenix work fine though.
The error:

[error] Error loading NIF, AppSignal integration disabled!
Failed to load NIF library: '/mnt/c/blablabla/_build/dev/lib/appsignal/priv/appsignal_extension.so: cannot enable executable stack as shared object requires: Invalid argument'
Is your operating system (x86_64-unknown-linux-gnu) supported?

[arjan]

Bash for Windows is still windows, under the hood, I think.

[HenriMorlaye]

Yes, very deep down, but it basically enables native Linux ELF64 binaries to run on Windows without any VM. Both Erlang's and Elixir's ubuntu packages do build and work on it. Bash On Windows is a major argument for linux or mac users switching to Windows 10. They keep developping on an almost normal Ubuntu subsystem without running a VM.

[spapas]

This is an old issue however I'd like to know if appsignal spports Window 10 now. And if it still doesn't support Window I'ld like to know why is that?

[shairyar]

We don't support it because there's not a lot of demand for it that we've seen. Most people won't use windows in their production apps, are you using windows on your production server?

You can give the windows subsystem for Linux a try.

[spapas]

Hello @shairyar thanks for replying.

No of course we don't use windows on production. However I'm using windows as my dev system and I'd really like to be able to debug the appsignal integration with my app. I haven't tested it in WSL yet because comment #36 (comment) says that it doesn't work, do you think that something may have changed? (I don't use WSL normally)

TIA

[shairyar]

That comment is from 2017, I am not sure if it's still broken but we will take a look and see. If it is broken we will fix it.

[tombruijn]

Let's test the Elixir integration on WSL on a virtual windows machine. If anything breaks, let's fix it. Do remember to install the correct build packages for linux in WSL. https://docs.appsignal.com/support/operating-systems.html

To do

• Set up windows virtual machine: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
• Research difference between the "Windows Subsystem for Linux" (WSL) and "Bash for Windows". Are they the same under the hood? Is "Bash for Windows" still a thing?
• Set up emulation that was reported as not working
• Document the installation steps needed to set up a test machine with the reported broken environment
• Test AppSignal for Elixir on the emulation that was reported as broken
• Document how it doesn't work as a comment in this issue
• If you have an immediate fix, send in a PR with the fix. Do not spend more than half a day on this.