Unable to use xdebug on Mac M1

[ralbin]

I have a new macbook with the M1 processor. the xdebug fails to work. Everything else appears to be fine.
I recently uninstalled Wardent and reinstalled it, as I heard a recent PR may have fixed it but so far no luck.
When I cd into /opt/warden and do a git status and git pull origin everything is up to date.

I tried to ensure my Server settings are correct in phpstorm, as per the official Warden docs.

Is there any update to when this may be resolved?

[ralbin]

Something you can check but may not have an issue with

docker compose --version

docker-compose –version

Are they different? If so, remove the brew one

brew remove docker-compose

Check it again

docker compose version

docker-compose --version
They should be the same

Now ensure that your environments are down

warden env down

Then ensure that you shutdown the services
warden svc down

Pull in the new services
warden svc pull

Pull in the new environments
warden env pull

Do the rebuild and recreate steps next and don't forget to use the force recreate ( I believe this was my actual fix )

warden svc up --force-recreate

Fire up your environment once again
warden env up -d --build

That should fix your M1 woes

[erikhansen]

@ralbin I've been using this fork on an M1X MacBook Pro for months now and xdebug is working fine for me. Here are my PhpStorm settings:

I use the Chrome xdebug helper extension to activate xdebug.

[ralbin]

A buddy of mine Preston Choate actually helped me figure it out, I had an older version of this fork and needed to reload things...and I had a fun double install of docker compose. Thanks for replying, I enjoy seeing how we all take care of one another.

[drpayyne]

Glad to see community activity here. Thanks for collaboration, folks! :)