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

[BUG] Airdrop broken and adds watermark #286

Open
1 task done
Ibrty opened this issue Jan 10, 2025 · 2 comments
Open
1 task done

[BUG] Airdrop broken and adds watermark #286

Ibrty opened this issue Jan 10, 2025 · 2 comments
Labels
bug Something isn't working unconfirmed

Comments

@Ibrty
Copy link

Ibrty commented Jan 10, 2025

Describe the bug
A clear and concise description of what the bug is.

Currently, when trying to to use the Boring Notch Airdrop feature, the second you select a device to send the file to, the window disappears and leaves a watermark on the screen that can only be removed by quitting and relaunching Boring Notch. It also doesn't actually send the airdrop to the device you click on.

To Reproduce
Steps to reproduce the behavior:

  1. Drag a file into the airdrop section
  2. Click on your desired device
  3. See error

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

Instead of disappearing and not sending, properly airdrop the file to the selected device and then close without leaving a watermark.

UPDATE

While replicating this bug a couple more times for the screen recording, airdrop started to work without issues so this might be an intermittent bug but a bug none the less

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

Untitled1.mov

Additional context
Add any other context about the problem here. Mentioning what version are you using.

Checks

  • I haven't found any duplicates with my issue.
@Ibrty Ibrty added bug Something isn't working unconfirmed labels Jan 10, 2025
@amygdalios
Copy link

Had the same issue earlier today. I'll try to open a pull request my self but it doubt I'll manage to fix it.

@amygdalios
Copy link

UPDATE: I think the bug is due to the app being a background process, macOS will treat is as a daemon and this will have conflicts with foreground updates like airdrop returning this warning "CGError -606" on the console. My solution to the issue would be to move the app to the foreground temporarily for airdrop and then move it back to the background. Haven't found a way to do it yet, just posting so that if someone sees this, it might help them.

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

No branches or pull requests

2 participants