🐞 Delayed gesture availability after login

Open
  • Is something wrong?
#1,196 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop, performance

Research direction

The payload names no files or tests, so start by reproducing the delay: reboot, log in, and time how long gesture-based window movement takes to respond compared with keyboard and trackpad actions. Look for where gesture handling starts up relative to the other controls during launch. Done means gestures respond right after login, with the timing confirmed on the development build.

Written by the indexing model from the issue text.

Description

Bug
Bug Description

As someone who reboots their Mac frequently, I've noticed that after logging in, Loop gestures take significantly longer to become available than other Loop controls. Since I encountered this behavior on a daily basis, it has become quite noticeable. Keyboard + trackpad actions are ready almost immediately, while gesture-based window movement remains unavailable for some time before it starts responding.

I'm not sure if this is expected or specific to my system, but I wanted to report it in case it's an unknown issue or something that could be optimized :)

Affected Scope

Performance

Steps to Reproduce
  1. Restart the Mac.
  2. Log in to macOS.
  3. Immediately attempt to move or position a window using Loop gestures.
  4. Compare the behavior with Loop's keyboard + trackpad controls during the same period after login.
Reproducibility

Always

Expected vs Actual Behavior

Loop gestures should be available immediately after login, similarly to other Loop controls.

Screen Recordings / Screenshots

No response

Severity

Minor (limited impact)

macOS Version

macOS 27.2

Loop Version

Version 🧪 1.4.3 (1783)

Did You Try the Development Build?

Yes

Additional Context

No response

Final Checks
  • My issue is written in English.
  • My issue title is descriptive.
  • This is a single bug (multiple bugs should be reported individually).
  • I have looked to see if this is a duplicate of another bug report.
  • I can help with further investigation.
  • I can help with developing a fix for this issue.
Dominant language
Swift
Stars
11.9k
Forks
287
Avg merge
17h 7m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mrkai77/Loop

All issues in mrkai77/Loop

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.