Skip to content

Bug when opening Spotify through nook #182

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

Open
6 of 7 tasks
Hatters97 opened this issue Apr 24, 2025 · 4 comments
Open
6 of 7 tasks

Bug when opening Spotify through nook #182

Hatters97 opened this issue Apr 24, 2025 · 4 comments
Labels
bug Issues reporting wrong behavior

Comments

@Hatters97
Copy link

Problem

I have encountered a problem when opening spotify from the nook. It freezes momentarily ant won't allow the area to be used and clicked to fix the situation. It works after some time but there seems to be a processing issue when opening apps through the nook

Steps to reproduce

Open the Spotify app through Alcove
The nook functions instantly through opening the app

Expected behavior

When opening Spotify through Alcove I thought that this would be instantaneous response rather than freezing and keeping the notch open.

Menu bar affecting apps

No response

Alcove version

1.2.0

Mac/MacBook model

Macbook Air M4

macOS version

15.4.1

macOS Beta

  • Yes

Agreements

  • My title is concise but descriptive and specific.
  • I am on the latest Alcove release.
  • I have searched for existing bug reports.
  • I have read the FAQ.
  • This is not a usage or 'How to' question.
  • This is not a "I didn't receive my license" or a "I want a refund" issue.
@Hatters97 Hatters97 added the bug Issues reporting wrong behavior label Apr 24, 2025
@0x5b62656e5d
Copy link
Collaborator

1.2.0 is not the latest Alcove release. Please check if the bug can be replicated on Alcove v1.2.5.

@Hatters97
Copy link
Author

This was the case, I got the wrong version. This occurred earlier today for me.

@0x5b62656e5d
Copy link
Collaborator

@Hatters97 So there isn't anything wrong with v1.2.5? Or am I misunderstanding something?

@Hatters97
Copy link
Author

Sorry, this occurred on version 1.2.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues reporting wrong behavior
Projects
None yet
Development

No branches or pull requests

2 participants