-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Dusk in a built app? #11
Comments
@ekandreas Same issue, did you figured out any work around? |
No |
@nunomaduro Any idea? |
Not more than avoid using a compiled zero. |
It's the same issue that I got into when laravel-zero/laravel-zero#193 (comment) I have no idea right now. Isn't Dusk executing another process, other than the main one? And therefore a different setting for the file and port should be configured? Regarding this https://www.php.net/manual/en/phar.using.intro.php |
@nunomaduro any update on this? I have the same issue on a fresh LZ installation. |
@clarkeash No. Fell free to debug this and update the docs or the code accordingly. |
I have same this issue when try to run console-dusk in a Laravel built app (not Laravel Zero) on production server. Can anyone help this? |
I have been knocking my head against the desk trying to solve this one! Just managed to get it working... I resolved it by explicitly defining the I have overridden the Chrome driver with my own class. This class contains...
To override the Chrome driver I had to first override the manager class
Then apply this inside my AppServiceProvider class - make sure this provider is loaded after
|
When using laravel-console-dusk inside a compiled zero app this error is catched:
The text was updated successfully, but these errors were encountered: