I’m running into recurring problems with the Mast App, including crashes and features not working as expected. I’ve tried basic troubleshooting like reinstalling and clearing cache, but nothing has fixed it. Can someone explain what might be causing this and suggest reliable steps to get the Mast App working smoothly again?
I hit similar issues with Mast a while back. Crashes, broken features, random weirdness. Here is what helped, step by step.
-
Confirm app and OS versions
• Update Mast to the latest version from the App Store.
• Check your iOS / iPadOS version. Mast tends to behave better on the latest major version.
• If you run a beta OS, expect more crashes. Note them, but also try on a non beta device if you have one. -
Check the specific server you use
Mast is only the client. Your Mastodon server handles timelines, notifications, etc.
• Try logging in to the same account in a browser and see if things work there.
• Try logging in to a different Mastodon client app, like Ivory, Ice Cubes, or the official Mastodon app.
If problems show up in multiple apps, your server or account might be the problem rather than Mast. -
Reset Mast’s local data more aggressively
You said you reinstalled and cleared cache, but try this pattern:
• Delete Mast from the device.
• Restart the device.
• Go to Settings > General > iPhone Storage > Mast (if it still shows) and remove leftover data.
• Reinstall Mast from the App Store.
• Add only one account at first. Use it for a while before adding others. -
Narrow down what triggers the crash
Try to notice patterns, even rough ones. For example:
• Crashes when opening a certain tab, like Notifications or DMs.
• Crashes after you tap a specific type of media, such as GIFs or videos.
• Crashes when switching between multiple accounts.
• Features like boosts or bookmarks not working only on one account.
If you can get a repeatable set of steps, note it down. -
Check content filters and preferences
Some Mast issues come from odd combinations of settings.
• On your Mastodon account in a browser, go to Preferences > Filters, and disable or simplify filters for a bit.
• Check media settings like “Always show media” or “Auto play videos”. Turn off auto play and see if stability improves.
• If you use a lot of lists, try disabling them from Mast or using fewer at first. -
Try logging into a different account in Mast
• Create a throwaway account on a different server, like mastodon.social.
• Add that fresh account in Mast and test.
If the new account works fine, the problem ties more to your main server or account data. -
Capture logs or crash info for the dev
The Mast dev is quite responsive when given detail. To help them:
• Take screenshots of any error messages.
• Write the exact steps before a crash, like “Open app > tap Notifications > scroll fast > crash”.
• Note app version, iOS version, device model, and server name.
Then send all of that through:
• Mast’s built in feedback option if it has one in Settings.
• The App Store support link in Mast’s listing.
• The project’s GitHub or official site, if listed.
- Workaround while you wait on a fix
Until there is a fix that sticks, you can:
• Use Mast for some tasks, and another app for the stuff that tends to crash Mast.
• Turn off background refresh for Mast in iOS Settings. Some people report fewer crashes after that.
• Avoid heavy operations like pulling a huge timeline history or mass following from Mast.
If you share your device model, iOS version, Mast version, and your server name, people here can compare with their setups and tell you if they see the same bugs. That tends to speed up getting an actual fix instead of random guessing.
I’m gonna come at this from a slightly different angle than @viajeroceleste, since you’ve already done the “good citizen” troubleshooting.
At some point, you have to treat Mast like what it is: a single-dev-ish, relatively young, Mastodon client that will absolutely fall apart in weird edge cases. So instead of trying to “fix” it, think in terms of “contain” it.
A few things to try that aren’t just reinstall / cache / OS version:
-
Strip your Mastodon account settings down to bare bones
Not just filters like they mentioned, but everything that adds complexity:- Temporarily turn off all custom CSS / themes if your instance offers it.
- Disable all third‑party integrations or bots that touch your account (cross‑posters, bridge services, etc.).
- If you’ve pinned a ton of lists or use complicated notification rules, simplify them for a day or two.
Sometimes the app chokes on volume or complexity of account metadata more than on the timeline itself.
-
Check “weird” parts of your profile data
I’ve seen Mast clients crash because of:- Super long bios with a lot of links or Unicode.
- Packed profile fields with strange formatting.
- Alt text on certain pinned media being oddly encoded.
Try: - Shorten bio.
- Remove fancy characters / weird emojis.
- Unpin and repin media, or remove pinned posts entirely for a test.
It sounds dumb, but malformed or heavy profile data can trip up parsing in some clients.
-
Look at your follows / blocks / mutes volume
If you’ve been around for a while:- Massive block lists, especially imported ones, can cause certain views to misbehave.
- Huge numbers of followed accounts across many servers can slow or crash views that try to “summarize” your graph.
As a test, export your block/mute lists, then temporarily prune them in the web UI and see if Mast behaves better. If it does, that’s a strong hint the app just doesn’t handle that scale well.
-
Identify views that are probably just bugged and stop using them
Instead of chasing every crash:- If Notifications kills the app 8/10 times, turn off some notification types in the web UI and treat that tab as “broken” for now.
- If DMs or Local timeline blow up, use those only in the browser or another app.
It’s not a “fix,” but it’ll keep you semi‑sane while waiting for the dev to catch up.
-
Be brutally specific when reporting, and don’t sugarcoat it
Where I’ll mildly disagree with @viajeroceleste: vague “here’s what helped” is fine for us, but devs need your worst, most annoying, hyper‑detailed repro. For example:- “Fresh install, first launch, add account from [server], open Notifications, pull to refresh, scroll fast, crash.”
- “Tapping any toot with quote counts > 100 crashes. Same toot is fine in Ivory and web.”
Cut out anything that isn’t a repeatable step and let the dev know you compared with another client on the same server.
-
Assume at least one of your issues is just an upstream Mastodon thing
Features “not working” can be:- Your instance is on an older Mastodon version and the app expects new API behavior.
- Some endpoints are rate limited or disabled by your admin.
Ask your instance admin if: - They block certain API calls.
- They recently upgraded Mastodon and if there are known mobile‑client bugs.
If admins say, “yeah, we’ve had trouble with X in third‑party apps,” that’s your answer: it’s not you, not Mast, it’s the server.
-
Hard pivot strategy
If the app is interfering with you actually using Mastodon:- Pick one “primary” client that is rock solid (even if less pretty).
- Keep Mast as a “secondary” client for the stuff it does uniquely well, and only open it for that.
- If you can map out “these two features crash it reliably,” just don’t use them there.
Sounds like giving up, but honestly, life’s too short to spend another weekend chasing logs for a free app.
If you’re up for it, post specifics: device model, iOS version, Mast version, your instance, and exactly which views/actions blow up. With that, people can say “yep, happens here too” or “nope, works fine,” which at least tells you if you’re dealing with a personal cursed-account situation or a common bug.