Skip to content
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

Launcher Explore Icon is not working #951

Closed
2 tasks done
krishnaavril opened this issue Oct 11, 2024 · 2 comments
Closed
2 tasks done

Launcher Explore Icon is not working #951

krishnaavril opened this issue Oct 11, 2024 · 2 comments
Labels
type: bug Something isn't working

Comments

@krishnaavril
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

https://gyazo.com/dca48f74171699ad4f428a56a72667cd

Explore Icon is showing an error

Expected Behavior:

When clicked it should open the explorer in windows 10

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

In the launcher choose any task and hit explore at the bottom pane

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

No response

@krishnaavril krishnaavril added the type: bug Something isn't working label Oct 11, 2024
@BigRoy
Copy link
Collaborator

BigRoy commented Oct 11, 2024

@krishnaavril I have a feeling this is also due to something with that Priority attribute you had and the issue with your server update to 1.5.0 that now brought its own priority attribute to the table?

It works fine for me in server 1.5.0+ with latest ayon-core. So would need some more details about your configuration to detect why this may be failing.

@krishnaavril
Copy link
Author

Yes it is the priority attribute, it's not a bug, sorry and thanks
Working fine in 1.4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants