Describe the bug
Hello
The core that makes Livecontainer a solid initiative is the access to installed apps data through files app, however by installing ish app the appgroup container (named null) is stored in main livecontainer’s appgroup which is only possible to access through a backup.
Instructions to reproduce
The target’s location from extracted backup:
Payload
Container
Library
Documents
AppPlugins
AppGroups
group.com.Side....R9NW7HXXXX
LiveContainer
Tweaks
Data
Application
AppGroup
(null)
Changing livecontainer’s bundle id and name without urlscheme results in accessible appgroup container in fils app.
On My iPhone / LiveContainerO / Data / AppGroup / (null)
What version of LiveContainer and iOS are you using?
Livecontainer+sidestore 3.6.1 , ios18.6.2
Other info
It’s not confirmed how the (isolate appgroup) toggle in containers may function, an explanation of the option is highly appreciated
edit:
activate isolate appgroup results in LCappgroup folder in the app's data directory in files app
Describe the bug
Hello
The core that makes Livecontainer a solid initiative is the access to installed apps data through files app, however by installing ish app the appgroup container (named null) is stored in main livecontainer’s appgroup which is only possible to access through a backup.
Instructions to reproduce
The target’s location from extracted backup:
Payload
Container
Library
Documents
AppPlugins
AppGroups
group.com.Side....R9NW7HXXXX
LiveContainer
Tweaks
Data
Application
AppGroup
(null)
Changing livecontainer’s bundle id and name without urlscheme results in accessible appgroup container in fils app.
On My iPhone / LiveContainerO / Data / AppGroup / (null)
What version of LiveContainer and iOS are you using?
Livecontainer+sidestore 3.6.1 , ios18.6.2
Other info
It’s not confirmed how the (isolate appgroup) toggle in containers may function, an explanation of the option is highly appreciated
edit:
activate isolate appgroup results in LCappgroup folder in the app's data directory in files app