mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 09:05:53 +03:00
[GH-ISSUE #780] Halide-1.17.3‘s UI is abnormal #701
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#701
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 @Littlechocolate on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/780
Describe the issue
The control bar, which typically appears at the bottom of the screen (including options like timer, flashlight, RAW, etc.), has moved to the top of the screen.
Normal:

LiveContainer:

Instructions to reproduce
From app opening to app closing
Always
What version of LiveContainer and iOS are you using?
LiveContainer version: 3.6.1-release. iOS version: 18.5
Other
No response
@GA251 commented on GitHub (Aug 21, 2025):
I think this issue might be caused by the app thinking that it is on a non-notched device, thereby thinking it’s OK to move the controls to the top? It looks like the bottom gesture bar is also ignored, much like an iPhone with a home button.
If LiveContainer sets the “device boundaries” (variables like if a notch is present or not, how tall is the status bar and gesture bar etc.), its most likely that apps that read these programmatically BEFORE LiveContainer sets them and just assumes that it is a non-notched device, I assume that might be why native views aren’t affected by it, as they might react to the the “device boundaries” changing and move accordingly, and only apps that check such variables once at startup are affected by it.
(I think that my issue #759 also relates to this)
@hugeBlack commented on GitHub (Jan 3, 2026):
It's different from 759. The developer hardcoded the resolution of old devices, so this issue is more similar to #457.