[GH-ISSUE #1077] [Compatibility] File directory picker with MeloNX disables the open button #951

New issue

Closed

opened 2026-03-03 15:37:32 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 15:37:32 +03:00

Owner

Originally created by @EnderRobber101 on GitHub (Jan 10, 2026).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1077

Describe the issue

On the latest nightly commit github.com/LiveContainer/LiveContainer@3c2228f278
along with melonx 2.2
The folder picker has the open button disabled (despite all combinations of legacy and modern fix file picker toggles) as shown below

However this is not the case of a direct sideload

Instructions to reproduce

Install sidestore + livecontainer from https://github.com/LiveContainer/LiveContainer/actions/runs/20824866990
install MeloNX to it (version 2.2)
Run the ram entitlement app
Run melonx and follow normal installation steps
click add rom directories
There is the bug

What version of LiveContainer and iOS are you using?

iOS 26.1 Livecontainer 3.6.60

Verify steps

I downloaded LiveContainer from releases / actions section or LiveContainer's AltStore source.
I have the latest LiveContainer.
I installed LiveContainer through AltStore/SideStore/TrollStore or I'm confident that I signed LiveContainer correctly with all required entitlements.
I have tried to sideload the app normally through free sideloaders and I did not encounter the same problem

The name, version the app having issues

MeloNX Version 2.2

Crash Log

No response

Other

Note: I am not sure if this is a melonx or livecontainer bug so i am placing it here for now. If this a melonx bug, sorry for the inconvenience, and thank you.

Originally created by @EnderRobber101 on GitHub (Jan 10, 2026). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1077 ### Describe the issue On the latest nightly commit https://github.com/LiveContainer/LiveContainer/commit/3c2228f2784fe5ebe9219639e82d026549588ac9 along with melonx 2.2 The folder picker has the open button disabled (despite all combinations of legacy and modern fix file picker toggles) as shown below <img width="1206" height="1889" alt="Image" src="https://github.com/user-attachments/assets/608869ed-dc1f-4cda-b040-e7da28f30699" /> However this is not the case of a direct sideload <img width="1206" height="1935" alt="Image" src="https://github.com/user-attachments/assets/81aa74e8-58df-4fe5-9ff4-5697c173aa73" /> ### Instructions to reproduce 1. Install sidestore + livecontainer from https://github.com/LiveContainer/LiveContainer/actions/runs/20824866990 2. install MeloNX to it (version 2.2) 3. Run the ram entitlement app 4. Run melonx and follow normal installation steps 5. click add rom directories 6. There is the bug ### What version of LiveContainer and iOS are you using? iOS 26.1 Livecontainer 3.6.60 ### Verify steps - [x] I downloaded LiveContainer from releases / actions section or LiveContainer's AltStore source. - [x] I have the latest LiveContainer. - [x] I installed LiveContainer through AltStore/SideStore/TrollStore or I'm confident that I signed LiveContainer correctly with all required entitlements. - [x] I have tried to sideload the app normally through **free** sideloaders and I **did not** encounter the same problem ### The name, version the app having issues MeloNX Version 2.2 ### Crash Log _No response_ ### Other Note: I am not sure if this is a melonx or livecontainer bug so i am placing it here for now. If this a melonx bug, sorry for the inconvenience, and thank you.

kerem

2026-03-03 15:37:32 +03:00

closed this issue
added the
compatibility
label

kerem commented

2026-03-03 15:37:33 +03:00

Author

Owner

@hugeBlack commented on GitHub (Jan 10, 2026):

MeloNX side issue. They applied a problematic tweak when running inside LiveContainer which results in this issue. MeloNX developers are already aware of this issue.

@hugeBlack commented on GitHub (Jan 10, 2026): MeloNX side issue. They applied a problematic tweak when running inside LiveContainer which results in this issue. MeloNX developers are already aware of this issue.