Burrow
A tunnel down to something buried
That is what a burrow is, and it is the whole job. Your app's data container sits on a device you own, a cable away, and getting one file out of it should not be the hard part of your day.
It started with one file. I needed to test a case on a real iPhone, and that meant replacing a single file in Application Support. One file.
On the Simulator that is five seconds. Open Finder, drag it in, done. On a real
device it was already painful: download the entire container as an
.xcappdata bundle, edit the one file, upload the whole thing back.
Then Xcode 26 broke even that. Container download simply fails now, which leaves
devicectl and hand typed UDIDs, bundle IDs and long paths while a
deadline sits on your chest.
So I built Burrow. Browse your app's container on a real iPhone, pull a file, replace it, delete it, edit it in place, and watch it refresh live as your app writes.
Now it is five seconds on a real device too. It is free, and it will stay free. I built it because I needed it, and I use it every day.
I also make Chwilio, the native macOS SQLite editor I built to load extensions the way I always wanted. Point it at an FTS tokenizer, a virtual table or a custom function, and it preflights the load, scopes it to the databases you choose, and tells you exactly what happened.
The two fit together: pull a database off a device with Burrow, open it in Chwilio, drop it back when you are done.
The agent half of Burrow is open source at github.com/SNNafi/BurrowAgent, so you can read exactly what runs inside your app before you add it.
Tell me what broke
Bug reports, feature requests, or a device and app combination Burrow does not handle properly. I read everything.