Closed wattsie closed 6 months ago
BTW: I thought I found a workaround...
If I copy vendor/nativephp/php-bin/bin/mac/x86
to vendor/nativephp/php-bin/bin/mac/x64
and try build it works.
But when I launch the app, the window shows, but I get a "500 | SERVER ERROR"
PS: in config/nativephp.php
I have set NATIVEPHP_UPDATER_ENABLED
to false (tried in .env still doesnt disable)
~/tmp/test2 ❯ ./dist/mac/Laravel.app/Contents/MacOS/Laravel ↵ INT
API server started on port 4000
Starting PHP server... /Users/me/tmp/test2/dist/mac/Laravel.app/Contents/Resources/app.asar.unpacked/resources/php/php artisan serve /Users/me/tmp/test2/dist/mac/Laravel.app/Contents/Resources/app.asar.unpacked/resources/app/
Making sure app folders are available
PHP Server started on port: 8100
(node:69696) electron: NSVisualEffectMaterialAppearanceBased has been deprecated and removed as of macOS 10.15.
(Use `Laravel --trace-warnings ...` to show where the warning was created)
Checking for update
Error: Error: net::ERR_NAME_NOT_RESOLVED
at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49935)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
(node:69696) UnhandledPromiseRejectionWarning: Error: net::ERR_NAME_NOT_RESOLVED
at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49935)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
(node:69696) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
I got the same issue on M1 (arm64)
I've the same error here and I opened a PR in order to fix it.
@mpociot As far as I understood, when we compile the php for Mac OS when it's not arm, the binary is the same for the x86 and x64.
Could I come up with a PR for this repository and then we can identify if it isn't arm, we search for a folder "x64_x86", so we don't need to have a duplicated binary in the php-bin repository.
What do you think?
+1
The logic for determining which Mac platform to build for has been improved in recent weeks.
Please run composer update
to get the latest version and try again.
What happened?
Hi all, Sorry to bug, but on creating a fresh laravel install, including latest 0.3.1 and trying to build on x86 mac, it still fails.
Install appears to work no errors now.
However...
Wondering where the
--x64
flag is coming from... shouldnt it be--x86
??The directory
/Users/me/tmp/test1/vendor/nativephp/php-bin/bin/mac/x64
does NOT exist. However the/Users/me/tmp/test1/vendor/nativephp/php-bin/bin/mac/x86
is available...How to reproduce the bug
In a "tmp" directory hanging of home directory (be be sure there are no permission issues)
Package Version
0.3.1
PHP Version
8.1
Laravel Version
10.16.1
Which operating systems does with happen with?
macOS
Notes
Please note, Mac Intel x86 based