IOS Filesystem is a disaster waiting to happen.
IOS Filesystem is a disaster waiting to happen.
Your iPhone 7 runs a jailbroken version with a terminal setup. It's built on macOS, which itself is based on BSD and Darwin (version 19.4.0). The filesystem resembles UNIX, though it's hidden deep within. After logging in as root or using the mobile password, you can explore directories and see how commands work—apt is used for package management, including installing Python. A Python script you moved was copied successfully, but when viewing it through the Files app, nothing appears. The folder labeled `/Containers` seems to be empty despite containing one item. This behavior is unusual and may relate to how the filesystem is structured or accessed. If you need further clarification, consider checking logs or using a different terminal method.
It seems the challenge lies in adapting an old Unix foundation with modern tools you’re not used to. Apple has a history of relying on outdated technologies, which led to complications and even company struggles. The original 68k operating system was built in a complex language meant for education, not real-world use, causing many issues. It’s likely they realized the mistake after it nearly caused their downfall. Understanding containers might help clarify the situation.
I almost missed mentioning them—I hadn’t seen containers before, though I was aware of their use in iOS. Surprisingly, the "Files" app included a file manager, which would have been great.
Containers - isolates applications and their documents to prevent access from other apps. Files - there are two storage spots per app: one backed up to iCloud and another not. The underlying system might use Unix, but the file structure goes beyond the core OS and is tailored by Apple.
It's not possible for app 1 to retrieve anything directly from app 2. The only solution is to open app 2, click "share," and choose app 1, after which the system copies the file into app 1's documents folders. With recent iOS updates, you can also save files in "files" from app 1 and view them in app 2. This is why iOS isn't ideal for traditional use—it leads to many duplicates and versions when working across multiple apps.
It seems the options for backing up iCloud files are consolidated into a single folder, and the settings related to backup or iOS13 are managed through the app itself.