-
-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symlink bug on app boot-up #250
Comments
I have this issue as well. I noticed that if I don't run the command After running the command and then building the application, the error is gone, and I haven't seen any other errors on my logs regarding this issue. It seems like the default storage location is not set in the native app without running the command and so it looks for it in the wrong place. |
@EPuigdemont I will try that whenever I have to update the application! |
@EPuigdemont I have tried this today and it changed the error to: |
Interesting! I've not come across this. I'll look into it |
@simonhamp I experienced the same error yesterday. For me |
@KirillDakhnyuk Are you on Mac or Linux? |
@simonhamp Mac M1, Laravel 10, PHP 8.1, Node 20.6.1. |
@KirillDakhnyuk Is it blocking your app from running? When and where do you see the error? |
@simonhamp actually it did not. I see the error inside |
What happened?
I have made a NativePHP app which works great. Inside the application I added logging of the errors to a private slack channel, to keep tracks of errors.
When testing the app I came accross the error
symlink(): Argument #1 ($target) must be of type string, array given
, but my application still worked so ignored it for some time.But the errors keeps coming back so I looked into it a bit and found out it happens everytime the
storage:link
command is ran, if I'm correct that will be run on every startup of the application.It lucky doesn't bother the working of the application, but still wanted to address this here in case I can do something about it or that it actually is a bug.
How to reproduce the bug
Haven't had time too try it on a new project, but I think it happens on every build app. Or at least on Mac and Linux :)
Package Version
0.4.0
PHP Version
8.2
Laravel Version
10.25
Node Version
21.5
Which operating systems does with happen with?
macOS, Linux
Notes
No response
The text was updated successfully, but these errors were encountered: