Describe the bug
Price displays incorrectly in Yen.

Versions
Ray version: n/a
Website: https://myray.app/

To Reproduce
Steps to reproduce the behavior:

1. Visit website
2. Check display. Occurs in both places, top and bottom, in both desktop and mobile sized browser.

Expected behavior
Could it be prettier? It looks kinda awkward 😥.

Screenshots

Desktop (please complete the following information):
Chrome: 87.0.4280.88 (Official Build) (64-bit)
OS: Win10

Additional context
I know it's not major and theres no way you for reasonable check every i18n currency. Just thought I'd point it out. 😀

Hi
Locally it works perfect. But when the code was sent to the server, the site crashes.
I was trying with:
composer require spatie/laravel-ray
first, and then with:
composer require spatie/laravel-ray --dev
with env set to production. Same issue:

[2021-01-07 22:12:30] production.ERROR: is_dir(): open_basedir restriction in effect. File(/usr/home/myaccount) is not within the allowed path(s): (/usr/home/myaccount/domains/mydoma.in/public_html:/tmp:/usr/share:/usr/local/share:/dev:/usr/home/myaccount/domains/mydoma.in/public:/tmp:/usr/share:/usr/local/share:/dev:/usr/local/share/pear:/usr/home/myaccount/domains/mydoma.in:/usr/home/myaccount/domains) {"exception":"[object] (ErrorException(code: 0): is_dir(): open_basedir restriction in effect. File(/usr/home/myaccount) is not within the allowed path(s): (/usr/home/myaccount/domains/mydoma.in/public_html:/tmp:/usr/share:/usr/local/share:/dev:/usr/home/myaccount/domains/mydoma.in/public:/tmp:/usr/share:/usr/local/share:/dev:/usr/local/share/pear:/usr/home/myaccount/domains/mydoma.in:/usr/home/myaccount/domains) at /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php:35)
[stacktrace]
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'is_dir(): open_...', '/usr/home/ekome...', 35, Array)
#1 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(35): is_dir('/usr/home/ekome...')
#2 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(16): Spatie\Ray\Settings\SettingsFactory->searchConfigFiles('/usr/home/ekome...')
#3 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(9): Spatie\Ray\Settings\SettingsFactory->getSettingsFromConfigFile('/usr/home/ekome...')
#4 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(37): Spatie\Ray\Settings\SettingsFactory::createFromConfigFile('/usr/home/ekome...')
#5 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(826): Spatie\LaravelRay\RayServiceProvider->Spatie\LaravelRay\{closure}(Object(Illuminate\Foundation\Application), Array)
#6 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(712): Illuminate\Container\Container->build(Object(Closure))
#7 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(796): Illuminate\Container\Container->resolve('Spatie\\Ray\\Sett...', Array, true)
#8 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(651): Illuminate\Foundation\Application->resolve('Spatie\\Ray\\Sett...', Array)
#9 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(781): Illuminate\Container\Container->make('Spatie\\Ray\\Sett...', Array)
#10 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(119): Illuminate\Foundation\Application->make('Spatie\\Ray\\Sett...', Array)
#11 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(51): app('Spatie\\Ray\\Sett...')
#12 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(25): Spatie\LaravelRay\RayServiceProvider->registerBindings()
#13 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(627): Spatie\LaravelRay\RayServiceProvider->register()
#14 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php(75): Illuminate\Foundation\Application->register(Object(Spatie\LaravelRay\RayServiceProvider))
#15 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(604): Illuminate\Foundation\ProviderRepository->load(Array)
#16 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterProviders.php(17): Illuminate\Foundation\Application->registerConfiguredProviders()
#17 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(230): Illuminate\Foundation\Bootstrap\RegisterProviders->bootstrap(Object(Illuminate\Foundation\Application))
#18 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(152): Illuminate\Foundation\Application->bootstrapWith(Array)
#19 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(136): Illuminate\Foundation\Http\Kernel->bootstrap()
#20 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#21 /usr/home/myaccount/domains/mydoma.in/public/index.php(59): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#22 {main}
"}

Describe the bug

1. If I double-click the AppImage file multiple times, it opens multiple instances (not sure if you can change that)

2. If I have one instance running, and press the close button, it stays open in the system tray. If I click the system tray icon, it opens a new instance with a second tray icon, while the existing instance is still running somewhere but is no longer reachable. Both try icons show/hide the new instance, unless I close the Ray window, at which point the tray icon(s) now spawn another new instance and icon.

By the way, all the subsequent instances don't receive Ray calls, presumably because the port is already in use by the first (lost) instance.

Also, this is happening with the "Show app" setting set to "On both task bar and system tray". I will try the other options and see if they behave better.

If I change the "Show app" setting to "On task bar", it's basically the same behaviour without the tray icon. If I close the app (either via the X or via Menu > Quit Ray) it still stays running in the background but there is no tray icon or task bar icon to get it back.

What I have just discovered is that Ctrl+Shift+L always seems to bring back the first instance (the lost one that receives all the ray calls)

Versions
Ray version: 1.0.2
spatie/ray package version: 1.0.0
spatie/laravel-ray package version (if applicable):

Desktop (please complete the following information):

• OS: Linux

Additional context
Originally reported by Jess Archer

Describe the bug
I was puzzled today at why the "delete line" shortcut in Sublime stopped working. I realized that I had installed Ray today and it is stealing this shortcut from all applications. CTRL+SHIFT+K is the standard "delete line" shortcut in Sublime, it is also the shortcut to open the browser console in Firefox. This makes it a poor choice for a shortcut.

Versions
Ray version (you can see this in "About Ray"): 1.0.5

Desktop (please complete the following information):

• OS: Linux
• Version 20.10

If this should be filed in a different repository (it's not specifically related to the spatie/ray package) please direct me to the correct location.

In the linux version of the Ray app, clicking the "Menu->About Ray" menu item does not do anything.

Versions:

• Ray app: 1.0.3

Steps to reproduce the behavior:

1. Open the Ray app
2. Click the "Menu" menu item
3. Click the "About Ray" menu item
4. Nothing happens

Expected behavior:

• The expected behavior is the display of version information for the app, such as in a dialog.

Other Information:

• OS: Ubuntu 20.04

The project looks great!

It might be nice to have the ability to output multi-dimension arrays as a table view.

ray()->table([
   [
        'name' => 'John Doe',
        'age' => 25,
        'height' => 178
   ],
   [
        'name' => 'Zoe Smith',
        'age' => 46,
        'height' => 188
   ],
   [
        'name' => 'Jessica Jones',
        'age' => 21,
        'height' => 163
   ],
])

I would be happy to take a look at implementing something if you like the idea?
Edit: I see the ray client is not itself open source so not sure I could implement it but would love to see it anyway! :)

Ed

Hello,

Just downloaded the tool to have a play around with it, I added the following line to a controller class:

ray('hello world!', ['an array'], app());

And it successfully logs to Ray which is great, but it says the line is the actual helpers file for ray, I did update the preferences so it's using VSCode, it should of taken me to my controller class right?

Great job on the tool, am looking forward to using it more often!

Thanks.

Describe the bug
I want to evaluate the product but run into #18.
I'd like to reproduce and provide more info but run into #36

Expected behaviour
Provide a way to get out of this deadlock.

Note
I license purchase is ongoing for me, but that takes time.

Versions
Ray version: 1.0.2
spatie/ray version: 1.1.3
spatie/laravel-ray: 1.1.0
Laravel version: 8.21.0
OS: Windows 10 version 2004 build 19041.685

I am unable to install the package.

PHP 7.4.3
Composer 2.0.1
Laravel Framework 8.11.2

Using version ^1.1 for spatie/laravel-ray
./composer.json has been updated
Running composer update spatie/laravel-ray
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires spatie/laravel-ray ^1.1 -> satisfiable by spatie/laravel-ray[1.1.0].
    - spatie/laravel-ray 1.1.0 requires illuminate/database ^7.0|^8.13 -> found illuminate/database[v7.0.0, ..., 7.x-dev, v8.13.0, ..., 8.x-dev] but it conflicts with another require.


Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Describe the bug
Changing the shortcut key of CMD + Shift + L doesnt save, and always reverts back to that.

Versions
Version 1.0.4 (1.0.4)

To Reproduce
Steps to reproduce the behavior:

1. Go to Ray > Preferences
2. Change the shortcut last letter (ie L)
3. Try using new shortcut (doesnt work, still using old one)
4. Close the app
5. Re-open the app (not saved)

Expected behavior
Saved and working

Desktop (please complete the following information):

• OS: macOS
• Version 10.15.7

When i installed spatie/laravel-ray local it works fine.
But when i push to git and pull on the server i get following error.
Target class [cache] does not exist.

Versions
Latest

You can use composer show to get the version numbers of:

• spatie/laravel-ray package version (if applicable): 1.1.0

PHP version:
7.4

To Reproduce
Steps to reproduce the behavior:

1. Install spatie/laravel-ray (locally)
2. Test locally -> works perfect
3. git add , git commit, git push
4. On staging server, git pull
5. Reload website: Target class [cache] does not exist

Desktop (please complete the following information):

• OS: macOS Catalina
• Version: version 10.15.7

Additional context
Is it the intention to only install ray locally?

No matter where I put ray() the listed file is always helpers.php:21.

I'm using the composer package: "spatie/ray": "^1.0"

I'm using ray in wp-content/plugins/some-plugin/src/Course/Catalog/CoursesView.php:89

When I click on a source file file path in Ray, it wants to look for an app in Microsoft Store.

What do I need to do to register the protocol so it opens the correct file in PhpStorm?

Versions
Ray version: 1.0.2.0
spatie/laravel-ray package version (if applicable): 1.1.0
Laravel version (if applicable): 8

Desktop (please complete the following information):

• OS: Windows 10

Describe the bug
The font size used by Ray is smaller than what I use on my OS, making it a bit hard to read

Versions
Ray version (you can see this in "About Ray"): 1.0.3

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.2.0
• spatie/laravel-ray package version (if applicable):

PHP version: 7.4.9
Laravel version (if applicable):

To Reproduce
Steps to reproduce the behavior:

1. Launch ray
2. Look at the font size

Expected behavior
Same font size than my other gnome applications

Actual behavior
The font size is smaller than what most of my applications use (12pt). It looks like the font size in most of Ray UX is like 8/10pt
Generally speaking, the colors are also off compared to my OS

Desktop (please complete the following information):

• OS: Ubuntu
• Version [e.g. 22] 20.10

Additional context

• Being able to adjust the font size in the preferences if getting it from the OS is hard would be a workaround.
• The menu items seem to have the right font sizes, it's the main Ray pane that has smaller font sizes.

Screenshots

Describe the bug
There are still a lot of projects that are incompatible with composer v2 (e.g. Magento) and the composer-runtime-api:2,0 is unavailable there.
It would be really helpful to be able to use this package with composer v1

Versions
1.2.0

PHP version:
7.4.10

To Reproduce
composer require spatie/ray --dev

Expected behavior
Allow ray to install

Desktop (please complete the following information):

• OS: macOS
• Version: 11.0.1 Big sur

In my case, when using
ray($variable1, $variable2)
the location of that statement is not displayed,
...\vendor\spatie\ray\src\helpers.php:16
is displayed instead.

Any plans to add SSH connector ?

Describe the bug

I have installed a fresh Laravel application using laravel new foo, I then added some MySQL config in the .env file and created a database called ray, I then added one user manually using TablePlus, and then from within the default web.php route file added the following :-

I also installed the composer package using composer require spatie/ray

I did NOT install the laravel package, as the documentation said I should install this or that ...

Route::get('/', function () {
    ray()->showQueries();

    $users = User::all();

    ray()->showQueries();

    return view('welcome', [
        'users' => $users
    ]);
});

This causes an error when attempting to load the page :

BadMethodCallException
Method showQueries does not exist.

Versions
Ray 1.0.8

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.5.0
• spatie/laravel-ray package version (if applicable): Not installed this package yet, I am however wondering if these methods are part of this package, the documentation said "install ray OR laravel ray"

PHP version:
Laravel version (if applicable): latest 8.21.0

To Reproduce
Steps to reproduce the behavior:
Add the code above to the web.php as the main route and try to dump out the queies

Expected behavior
To dump the queries back to ray and to not throw an exception

Screenshots

I have this issue for Linux

chmod u+x Ray-1.0.7.AppImage 

./Ray-1.0.7.AppImage 
[16587:0110/102645.411569:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Ray-1.o4uaju/chrome-sandbox is owned by root and has mode 4755.
Trappe pour point d'arrêt et de trace

sylvain@mini:~$ cat /etc/os-release

PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Describe the bug
On mac, cmd+w doesn't close the window.

In #33, cmd+h was added to hide the window. Great! But now cmd+w does nothing.

Versions
Ray version: 1.0.5

To Reproduce

1. Press cmd+w

Expected behavior
The window should disappear.

Desktop:

• OS: macOS
• Version: 11.1

Additional context
Ray is rad.

Describe the bug
Ray seems not be running at http://localhost:23517

Request takes time to process and fails to this message. If in this time I open ray app, everything works just fine.

Happening on Windows 10 with laragon.

Versions
Ray version: 1.0.2.0
spatie/ray package version: 1.1.3
spatie/laravel-ray package version (if applicable): 1.1
Laravel version (if applicable): 8.12
Media Library Pro version: N/A

To Reproduce
Steps to reproduce the behavior:

1. Create a new laravel app
2. Install laravel-ray package
3. Add one ray() statement in web.php
4. Quit ray Windows App
5. Open laravel default home route.

Expected behavior
As this is an optional developer tool, if ray app is not running, Laravel application should run just fine without considering ray helper just like it runs in prpduction.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Version 10

Additional context
Add any other context about the problem here.

https://twitter.com/divspace/status/1347239949330878464

Describe the bug
Clicking on a file logged in Ray doesn't open the text editor (in my case Sublime)

Versions
Ray version (you can see this in "About Ray"): 1.0.3

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.2.0
• spatie/laravel-ray package version (if applicable):

PHP version: 7.4.9
Laravel version (if applicable):

To Reproduce
Steps to reproduce the behavior:

1. Log someting
2. Click on the file name logged in the application

Expected behavior
The file is opened at the line indicated by Ray in the text editor I chose in preferences (Sublime)

Actual behavior
Nothing happens

Desktop (please complete the following information):

• OS: Ubuntu
• Version [e.g. 22] 20.10

Additional context
Tested in the trial version.

Describe the bug
When using "Menu > Quit Ray" the Ray itself is closed, but its processes (5 so far) are still present and not killed.
When you quit Ray and try to uninstall it (to reinstall) - the Uninstall Tool that I use for this purpose says me that Ray is running in the background and whether I want to kill all the processes.

Versions
Ray version (you can see this in "About Ray"): 1.0.3

PHP version: 7.4

To Reproduce
Steps to reproduce the behavior:

1. Instrall Ray on Windows 10
2. Quit Ray
3. Observe all the Ray processes in the Task Manager.

Expected behavior

When quiting all processes should be killed.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Pro, 20H2

Describe the bug
When running trial mode and nothing appears in the app, it is not clear if this is due to the 10 log items limit.

Versions
Ray version: 1.0.2
spatie/ray version: 1.1.3
spatie/laravel-ray: 1.1.0
Laravel version: 8.21.0

To Reproduce
Run my php code with ray() statements
Look at ray app window.
Window displays:
Trial mode allows for up to 10 lig items. Learn more...
Click 'Learn more...'
Click 'continue in trial mode'
Nothing happens while running php code with ray() statements.
It is not clear if this is due to the 10 log items limit.

Expected behavior
Debug information appears or app tells me that the trial license is over its 10 log items limit, then I am not proposed to continue in trial mode.

I could see something after auto upgrading the app from 1.0.1 to 1.0.2 though, so I suspect nothing appears because the 10 log items limit has been reached, but how do I know for shure this is the reason Freek?

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Version: 2004 build 19041.685

Describe the bug
There is no icon provided by Ray for the system to use it in the Dock

Versions
Ray version (you can see this in "About Ray"): 1.0.3

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.2.0
• spatie/laravel-ray package version (if applicable):

PHP version: 7.4.9
Laravel version (if applicable):

To Reproduce
Steps to reproduce the behavior:

1. Launch ray
2. Look at the dock

Expected behavior
Ray has an icon in the dock

Actual behavior
Ray is displayed as a blank space in the dock

Desktop (please complete the following information):

• OS: Ubuntu
• Version [e.g. 22] 20.10

Additional context
Tested in the trial version.

Screenshots

Describe the bug
Keyboard shortcuts do not work with accented symbols. Tested using: ö Ö Ä ä
Toggle visibility from anywhere
Clear Ray from anywhere

Versions

• Ray application version: 1.0.5.0
• spatie/ray package version: 1.3.2
• spatie/laravel-ray package version (if applicable):
  PHP version: 7.4
  Laravel version (if applicable): 8.20.1

Steps to Reproduce

1. Open up Ray application
2. Go to Preferences
3. Set the keyboard shortcuts to accented symbols
4. Close preferences (to apply changes)
5. Try to use the shortcuts

Expected behavior
Ray should notify and filter out accented symbols for keyboard shortcuts or support them (preferred).

Desktop
Edition: Windows 10 Pro
Version: 20H2
OS build: 19042.685
Experience: Windows Feature Experience Pack 120.2212.551.0

Describe the bug
If you running phpunit/pestphp eg via Github Actions ray might not be installed which will cause the issue that tests will run endless. (happend to me and costs me 2 hours of github action time)

Versions
Ray version (you can see this in "About Ray"): 1.0.0

• spatie/laravel-ray package version: ^1.1

PHP version:
Laravel version (if applicable): 8

To Reproduce
Steps to reproduce the behavior:

1. Add ray to a laravel project
2. Add ray.php to project with flag active is true
3. Add github action where you run the tests
   => Test didn't fail but run endless. (if phpunit isn't setup to fail early)

Expected behavior
Should not run in testing mode or should not block github actions.

Describe the bug

When trying to install the app shows the screenshot attached below.

Versions
Ray version (you can see this in "About Ray"): 1.0.4

To Reproduce
Steps to reproduce the behavior:

1. Make a clean installation of a new version of the app

Expected behavior

There should be no security-related notifications from Windows when launching the app.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Pro, 20H2

Describe the bug
ParseError
syntax error, unexpected '=>' (T_DOUBLE_ARROW), expecting ',' or ')'

Versions
Ray version: 1.0.8 (1.0.8)

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.5.0
• spatie/laravel-ray package version (if applicable): 1.3.4

PHP version:
Laravel version (if applicable): PHP 7.4.14

To Reproduce
On a fresh Laravel
COMPOSER_MEMORY_LIMIT=-1 composer require spatie/laravel-ray
memory_limit

The homepage gives this error:
ParseError
syntax error, unexpected '=>' (T_DOUBLE_ARROW), expecting ',' or ')'

Screenshots

Desktop (please complete the following information):

• OS: macOS
• Version: 10.14.6

Instructions on where to find license key after purchase could be clearer.

I had someone purchase a license for me. He used his credit card but my email adress.

I received a mail with the invoice, but no instructions on where to find the license key.
The ray app also gave no hint.
I figured out it is here: https://spatie.be/products/ray
It would be nice if the instructions in the app and the purchase mail mentioned where to find the license key.

Hello I have a mistake that tells me that I didn't install spatie/laravel-ray when it's a good installation can you help me? Thanks (I'm on windows 10)
https://flareapp.io/share/17Dn1GXm#F12

Every macOS application I can think of uses cmd + H to let users hide the current window.
When wondering why this was not working in Ray, I discovered that it uses cmd + W instead.

This is not only surprising but also a bit ‘frightening’ when considering muscle memory, because cmd + W is the standard shortcut to close tabs or windows in macOS applications.

Versions
Ray version: 1.0.2
spatie/ray package version: 1.1.0

Desktop:

• OS: macOS
• Version 10.14

Describe the bug
The moment I set the "Show App" setting to "On system tray" nothing happened, but next time I launched it didn't work at all.
Had to completely remove all files related to Ray manually because reinstalling didn't help either (From \AppData\Local\ray-updater and \AppData\Roaming\Ray) and installing fresh again. Using the normal unistaller from the app doesn't resolve the issue.

Versions
Ray version: 1.0.2.0
spatie/ray package version:
spatie/laravel-ray package version (if applicable):
Laravel version (if applicable):
Media Library Pro version:

To Reproduce
Steps to reproduce the behavior:

1. Go to Preferences
2. Click on Show App
3. Choose On system tray
4. Close Ray
5. Open again

Expected behavior
The app should have opened just fine, but got stuck in a default Electron window.

Screenshots
No screenshot available because I already managed to do a full reinstall and got it working again.

Desktop (please complete the following information):

• OS: Windows 10 Home
• Version 20H2

Additional context
Add any other context about the problem here.

Describe the bug
No matter which editor I choose, I always get to see this popup when I click a link in Ray.

Strangely it doesn't allow me to "pick from existing installed programmes". Only referred to the Microsoft store, where I cannot find the apps (that I already have installed)

Versions
Ray version: 1.0.8.0

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.5.0
• spatie/laravel-ray package version (if applicable): 1.3.4

PHP version: 7.4
Laravel version (if applicable): 7.30.1

To Reproduce
Steps to reproduce the behavior:

1. Send data to Ray
2. Click on the file link at the bottom of a ray message (to go to editor)
3. See error

Expected behavior
Being able to link the link to my IDE

Screenshots
See above

Desktop (please complete the following information):

• OS: Windows 10
• Version 10.0.19042

Describe the bug

If open_basedir restrictions are in effect and Ray does not find a ray.php in allowed directories, it'll keep "digging up" until its is_dir() call is made on a forbidden directory. In my case, it goes above /srv/www to call is_dir('/srv') which triggers this warning:

Warning: is_dir(): open_basedir restriction in effect. File(/srv) is not within the allowed path(s): (/srv/www/:/tmp) in /srv/www/example.com/current/web/app/themes/sage10/vendor/spatie/ray/src/Settings/SettingsFactory.php on line 35

Versions
Ray version (you can see this in "About Ray"):

1.3.2 (spatie/ray)

PHP version:

7.4.6

Laravel version (if applicable):

Not using Laravel.

To Reproduce

1. Set open_basedir restriction
2. Do not place a ray.php under that directory
3. Call ray()
4. PHP Warning triggered

Expected behavior

No warnings. ray.php is optional according to the documentation.

Describe the bug
Not able to reach context menu in the left top. (worked with any other app)
Not able to go to settings in any way
No app icon in the menubar

Versions
Ray version: 1.0.2
spatie/ray package version:
spatie/laravel-ray package version (if applicable):
Laravel version (if applicable):
Media Library Pro version:

To Reproduce
Steps to reproduce the behavior:

1. Go to preferences
2. Set "Show App" to "On Menubar"
3. Close settings

Expected behavior
Icon added to menubar I guess?!?
Just the normal mac context menu, shown when focused (was visable before changing this setting)

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS Big Sur
• Version 11.0.1

Additional context
When the auto update came, I had a change to go the the tips page. There was a link to the config on the "Tips" page, so I could set it back to "On Dock"

While I download ray app for Linux version using this link. https://spatie.be/products/ray/download/linux/latest it downloads a binary file which is not executed in ubuntu 20.04

The link to "Configure Ray if needed" under the Getting Started section returns a 404

After running this command in my terminal composer require spatie/laravel-ray --dev It shows some error like this..

λ composer require spatie/laravel-ray --dev
Using version ^1.0 for spatie/laravel-ray
./composer.json has been updated
Running composer update spatie/laravel-ray
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - spatie/laravel-ray 1.0.0 requires spatie/ray dev-master -> satisfiable by spatie/ray[dev-master].
    - spatie/laravel-ray 1.0.1 requires spatie/ray ^1.0 -> satisfiable by spatie/ray[1.0.0, 1.0.1].
    - spatie/ray[dev-master, 1.0.0, ..., 1.0.1] require symfony/console ^4.2|^5.2 -> found symfony/console[v4.2.0-BETA1, ..., 4.4.x-dev, v5.2.0-BETA1, ..., 5.x-dev] but the package is fixed to v5.1.8 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires spatie/laravel-ray ^1.0 -> satisfiable by spatie/laravel-ray[1.0.0, 1.0.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

What should I have to do...?

Is this a feature or a bug? :)

Describe the bug
When a notification payload is displayed by Ray, clicking the "view" button does not do anything.

Versions

• spatie/ray package version: 1.3.7
• Ray app version: 1.0.7
• PHP version: 7.4.13

Sample Code

ray()->notify('hello world');

To Reproduce

1. Run the sample code
2. Click on 'view' in the notification that is displayed
3. Nothing happens

Expected behavior
Expected behavior is that clicking the "view" in the notification will open the Ray window and display/highlight the message.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu (XFCE window manager)
• Version: 20.04

Describe the bug
When refreshing the browser on a page that has a ray call, the window focus automatically switches to the Ray window rather than staying in the browser. I don't know if this is intentional (it very well might be) but it would be great to have the ability to turn this off and keep window focus in the browser. I usually just need to look at Ray (on 2nd monitor) and don't need it to be focused.

Also, thanks for this awesome little app!

Versions
1.0.1

To Reproduce
Steps to reproduce the behavior:

1. Add ray('Test') to PHP file.
2. Refresh browser.

Desktop (please complete the following information):

• macOS 11

Describe the bug

The license is not activated and I can't find a way to retry to add it.

Versions
Ray version (you can see this in "About Ray"): 1.0.8

To Reproduce
Steps to reproduce the behavior:

When the App was launched for the first time, there was a window asking for the license.
I pasted the license there.

Now, at the bottom fn the main Ray window it says I am on the trial mode and on the https://spatie.be/products/ray#purchases
it says the license has not been activated.

When I click on Help -> Manage License ... it redirects me to the Ray website.

Desktop (please complete the following information):

• OS: Ubuntu 20.04.1 LTS
• Version [e.g. 22]

I'm talking about these arrows 🔻:

I'm using Ray 1.0.1 on Windows 10.

Any plans to support Windows?

So far only Mac and Linux in plans, which makes Windows users a bit sad.

Describe the bug

When the app is set to be displayed in Tray and you close the app (using the default Windows close button in app window) - it goes to the tray.

When you right click the tray icon to see the options, I see these: Preferences, Hide Ray, Exit Ray.

Only Exit Ray works fine.
Preferences option doesn't open app preferences, and for some reason, I have Hide Ray while Ray is already hidden for me.

It works only if Ray is opened and displayed to a user.

"Show app" option is set to "On both task bar and system tray".

Versions
Ray: 1.0.4.0

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Pro, 20H2

Describe the bug
I run
composer require spatie/laravel-ray
but when I try to debug using
ray()->showQueries();
I get that error

Versions
1.0.8

You can use composer show to get the version numbers of:
spatie/ray 1.5.2
spatie/laravel-ray 1.3.4

PHP version: 7.4
Laravel version 8

Desktop (please complete the following information):

• OS: macOS
• Version latest

Additional context
Laravel is running inside a Parallels VM with Ubuntu, I have modified the host setting to point to the Mac IP

Describe the bug
The unexpected null is printed before the caller's name.

Versions
Ray version (you can see this in "About Ray"): 1.0.8

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.3.7
• spatie/wordpress-ray plugin version: 1.0.0

PHP version: 8.0

To Reproduce
Place ray()->caller(); inside the function and check the Ray output. In my case, it's a simple namespaced function.

Expected behavior
Print caller name without a null.

Screenshots

Desktop (please complete the following information):

• OS: macOS
• Version 10.14.6

P.S. Thanks for the amazing app.