Backups stopped being made on Dropbox since Dec 2024 - check yours

Guys, I discovered this by pure accident, as Metagrid Pro has no Dropbox configuration of any kind. It appeared my backups stopped appearing on Dropbox starting from Dec 2024. Not sure, whether this is due to a password change (if there was any, I can’t recall that) or something else, but it just happened.

Check your Dropbox, if you use it for backupping, so that you avoid surprises in the future. Greetings!

Drop Box has stopped working here. If I try and upload anything to it I get stuck on the progress screen with no way of cancelling it except quitting MGP. I have 1.5 GB free in Drop Box. and Wi-Fi switched on.

That’s the same for me, MGP is not able to finish a backup since the end of 2024, it doesn’t matter if it’s on Dropbox or iCloud, MGP will just close itself while trying to do the backup (hey @JTB I’m a step ahead of you, I don’t have to force quit MGP he does it itself :rofl:)

The only way I can back up my profiles is to back up every one of them one by one, so I usually back up the profile whenever I make a change to it

1 Like

Dropbox works fine here - I use it every day - but I have such a massive collection of grids (from keeping old prototypes and betas and so on) that sometimes it struggles with the size when doing backups. Good reason for me to do housekeeping.

MetaGrid Pro never sends backups to Dropbox in the background. The only time a file goes there is when you explicitly choose Dropbox as the provider during export. At that point, the app uses the official Dropbox framework. It either uploads the file successfully, or it fails and shows you an error. There is no way for files to vanish silently, and there is no “automatic” Dropbox syncing.

If you don’t see your files in Dropbox, here are the most common reasons:

  • Different Dropbox account – MetaGrid Pro may be linked to a different Dropbox account than the one you’re checking (for example, work vs personal). In that case the files are still exported, but they show up only in the linked account’s /Apps/MetaGrid Pro folder.

  • Authorization expired – if you changed your Dropbox password or there was a security reset, Dropbox authorization can expire. In that case, MGP can’t upload until you re-authorize.

  • Access revoked – if MetaGrid Pro’s access was removed in Dropbox settings, uploads won’t work until you grant access again.

  • Storage full – if your Dropbox account has no free space left, new uploads will be blocked.

  • Wrong export target – if Dropbox wasn’t selected in the export flow, backups will be created locally or to iCloud instead.

  • Folder confusion – MetaGrid Pro always saves files to /Apps/MetaGrid Pro inside Dropbox, not in Documents or Downloads.

:white_check_mark: Quick steps to check:

  1. Make sure you’re logged into the correct Dropbox account.

  2. Try exporting again — if authorization has expired, Dropbox will prompt you to log in and re-link MetaGrid Pro.

  3. Double-check that you actually select Dropbox in the export flow, not Local or iCloud.

  4. Look specifically in the /Apps/MetaGrid Pro folder in Dropbox.

  5. Confirm your Dropbox account still has free space.

Once MetaGrid Pro is re-authorized with Dropbox, new backups will appear again in the correct folder.

Some of you reported crashes when exporting very large backups in MetaGrid Pro. Here’s what’s happening:

MetaGrid Pro stores a lot of information — profiles, workspaces, grids, icons, macros, etc. When you try to export everything in one file, the system has to load and serialize all of that data in memory. On iPads (and also on Macs via Catalyst) Apple enforces strict per-app memory limits. If the backup grows too large, the system simply kills the app during the process — which shows up as a crash.

We’ve explored many approaches to work around this, but unfortunately there is no reliable way to bypass those memory limits. It’s a hard restriction set by iOS/macOS, not something MetaGrid Pro can override.

:backhand_index_pointing_right: Best practice

The safest way to avoid this is to export smaller pieces of your setup — for example, individual profiles instead of the entire user space in one go. Each export will be smaller, run faster, and won’t hit memory limits. You can later re-import them as needed.

Your content remains safe — it’s just a matter of packaging it in manageable chunks so the export doesn’t exceed the system limits.

Thanks for clarification. I was 100% sure, that Metagrid Pro, when asking for a scheduled backup at launch, does it, using my Dropbox. If that’s not the case - where are they landing? I did them regularly and I swear - can’t see them either on Dropbox nor iCloud. My manual backups show only on iCloud, never on Dropbox, while I have full access to Dropbox on both my iPads. Anyway, I’m happy to have all my grids alive!

Would it be possibile to implement a Batch Profile Backup function in MGP? What I mean with this is that the user would activate this command, will be asked which profiles to backup (with an handy select all switch) and then MGP will proceed to backup the first of the selected profiles, than exit the backup process, wait a few seconds, than backing up the secondo profile and so on. In this way the user could have a complete backup of every single profile as separate files without having to do it manually one by one. A batch import could be useful too