mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 17:15:50 +03:00
[GH-ISSUE #524] [BUG] physical keyboard does not work with multitask #474
Labels
No labels
bug
compatibility
enhancement
multitasking
pull-request
safe area
status: broken
status: usable
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LiveContainer#474
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dragonplus8 on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/524
Describe the bug
Having multitask in either native window or virtual window does not work with a physical keyboard or a trackpad gestures
Instructions to reproduce
What version of LiveContainer are you using?
Version 3.4.57-Release (multitask/a967d83)
Other info
The physical keyboard I am using is a keyboard magic
@dragonplus8 commented on GitHub (May 29, 2025):
Turns out trackpads 2 finger drag does work but is flipped so to scroll horizontally you actually scroll vertically and to scroll vertically you have to scroll horizontally, unsure if I should make this a separate report
@khanhduytran0 commented on GitHub (May 29, 2025):
Is it flipped if you rotate it upside down?
@dragonplus8 commented on GitHub (May 29, 2025):
Actually sorry please just ignore the trackpad not working as it only seems to happen in some apps but most others seem to work fine
Also the scrolling does work normally if the app is in either portrait mode but is flipped in either of the horizontal orientations
@khanhduytran0 commented on GitHub (May 31, 2025):
Unfortunately, keyboard input issue is currently unfixable. We also tried Apple’s own Swift Playgrounds which used the same set of private API but it had the same issue most of the time.
Since then @hugeBlack has submitted feedback to Apple regarding Swift Playground, so we need to wait until Apple fixes it.
Worst case is it could be a stock bug in SpringBoard which would require updating iOS to fix it.