In Brew.php line 187: Unable to determine linked PHP.

[orangeShadow]

I try methods: composer global update, install php 72, brew upgrade, but error repeat and repeat ? what can i do, to run service ? valet version 2.0.8

[donaldallen]

I've had the same problem tonight, and here's what I did to get it running:

brew unlink php && brew link php
brew services restart --all
composer global update
valet start

It would be nice if Valet had some suggestions on what to do when "Unable to determine linked PHP." comes up.

[drbyte]

@donaldallen wrote:

It would be nice if Valet had some suggestions on what to do when "Unable to determine linked PHP." comes up.

Two code references:
https://github.com/laravel/valet/blob/master/cli/Valet/Brew.php#L178-L179
In this one it's looking to ensure that the php binary is linked. So, if you've unlinked all the installed PHP versions, then you'll get that error message.

Next it moves on to verify that the linked php binary is a supported one, per this list:
https://github.com/laravel/valet/blob/master/cli/Valet/Brew.php#L53-L56

[olivernybroe]

Getting some error here, tried to follow my symlink and it looks like this ../Cellar/php/7.2.2_14/bin/php.

Looking at how it matches, it looks for a full path containing one of the supported versions.

The supported php version looks for strings named like this php72, which of course is not in the path.

[scherii]

@Uruloke Should this not be caught by the first item php?

[orangeShadow]

uruloke, Yes, I commented locally this checking, and valet was started, but it is not good decision

[olivernybroe]

@scherii You are right, it should be caught by that, didn't see it. Gotta test this out a little locally and see if I can find an great solution.

[olivernybroe]

After cloning the repo I can't reproduce the error, lol.
If OP or someone else could tell how to reproduce the error, I will gladly try to fix it.

[orangeShadow]

Try brew update php to another version and change link

[olivernybroe]

@orangeShadow Just uninstalled php72 then installed php71, linked to php71, upgraded to php72 and linked to php72, then ran valet start and everything seems to work.

[orangeShadow]

@Uruloke, Can you write your file path and name for php link

[lesaff]

Brew has promoted php7.2 to core, so it is called php now.
https://github.com/laravel/valet/blob/master/cli/Valet/Brew.php#L185 will always throw exception until the logic is revised.

To get mine working, I edited
/Users/<your_username>/.composer/vendor/laravel/valet/cli/Valet/Brew.php
from

return strpos($resolvedPath, "/$version/") !== false;

to

if ($version === 0 || strpos($resolvedPath, "/$version/") !== false) return true;

[Zegnat]

@scherii,

Should this not be caught by the first item php?

You’d think that. But for some reason it didn’t for me on the path ../Cellar/php/7.2.3_2/bin/php… But when I added an item '7.2.3_2' to the array on that line all worked fine. No clue what’s tripping it up there.

[MelMacaluso]

brew unlink php && brew link php
brew services restart --all
composer global update
valet start

That fixes it for me, somehow.

[delino12]

ln -s /usr/local/Cellar/php71/7.1.16_1/bin /usr/local/bin/php

➜ ~ valet install
Stopping nginx...
Installing nginx configuration...
Installing nginx directory...
Updating PHP configuration...
Restarting php@7.1...
Restarting dnsmasq...
Restarting nginx...

[kroko]

wild guess that most people here having the issue only care if it's 7.1+ and thus are fighting an unnecessary fight. if possible just trash all php things from the system with uninstall, doctor, cleanup and just install newest php (currently 7.2) and formula name will be php not php@version, it has been fixed in brew core formula names for some time and install php@version is used only if you explicitly want older php.