I’m having repeated problems with the Magis App, including random crashes and features not loading correctly on my phone. I’ve tried reinstalling and updating, but nothing has fixed it. Can anyone explain what might be causing this and suggest practical steps to get the Magis App working smoothly again?
Had similar issues with Magis on Android a few weeks ago. Random crashes, blank screens, some features refusing to load. Here is what helped, step by step.
-
Check app and OS versions
• Go to your phone Settings → Apps → Magis → App details in store
• Make sure you are on the latest public version
• Then check your OS version. Some older Android/iOS builds have known compat bugs with newer SDKs -
Fully clear data, not only reinstall
Uninstall does not always wipe cached config.
On Android:
• Settings → Apps → Magis → Storage → Clear cache
• Then Clear data
• Force stop
• Then uninstall
• Reboot phone
• Reinstall from Play Store or App Store -
Turn off battery and performance optimizations
Battery killers often kill Magis in the background.
On Android:
• Settings → Apps → Magis → Battery
Set it to “Unrestricted” or “No restrictions”
• If you have vendor tools like MIUI, OneUI, EMUI, OxygenOS, check their “App battery management” and whitelist Magis
On iOS: avoid Low Power Mode when you see the worst behavior and see if it changes -
Check storage and network
• Make sure you have at least 1–2 GB free space. Low storage often leads to partial downloads and corrupt caches
• Try on a different network, like switch WiFi to mobile data. Some ISPs or DNS filters break API calls
• If you use a VPN, disable it and test -
Turn off VPNs, ad blockers, DNS filters
• Tools like Blokada, AdGuard, NextDNS, Pi-hole, or “Private DNS” on Android can block Magis endpoints
• Disable them, then open Magis and see if features load -
Log out and log back in
• Inside the app, log out
• Force stop the app
• Open it and log in again
Sometimes token refresh fails and you get stuck in a half-logged-in state -
Check for known issues
If Magis has:
• A status page
• A Twitter/X support account
• A Discord or subreddit
Search “Magis crash”, “Magis not loading” with your phone model and OS.
Sometimes there is a specific bug like “Magis 3.4 + Android 14 on Samsung devices”. -
Collect basic info for support
If nothing changes, gather:
• Phone model and exact OS version
• Magis version number
• Steps to trigger the crash (e.g. “Tap on Profile → Settings → App freezes”)
• Screenshot of any error message
Then send it through the in-app support (if it opens) or their email/website. The more concrete your steps, the faster they can reproduce it.
Quick tests to narrow cause:
• Test on another phone on the same account.
If second phone works, problem is your device config.
• Test another account on your phone.
If other account works, problem is your account data on their server.
If you share your device model, OS version, and Magis version, someone here might spot a pattern.
Couple more angles to look at that @mikeappsreviewer didn’t really dig into:
- Pattern of the crashes
Try to notice if it’s always:
- After Magis has been in the background a while
- When you open a specific tab (profile, messages, “discover,” etc.)
- Right after a notification tap
If you can say “it always dies when I tap X,” that usually means a specific in‑app module / API is broken for your account, not just your device.
- Account-level corruption
You mentioned reinstalling and updating, so if the same account still glitches, test this combo:
- Log out of your current Magis account
- Create or borrow a second account
- Use the app for a bit the exact same way
If the new account works fine on the same phone, the problem is probably on Magis’s backend tied to your original account data. At that point, only support can really fix it. When you contact them, say explicitly “New test account on same device is stable; only my main account crashes on [screen X].”
- Device-specific stuff people skip
- If you’re on Android and using “clone apps” / dual apps, don’t run Magis in cloned mode. Those envs are notorious for random crashes.
- Turn off any “floating window” helpers, screen recorders, auto-tappers, or overlay apps temporarily. Overlays can cause UI libraries to crash, especially on certain OEM skins.
- If you use accessibility tools (password managers, automation like Tasker, button remappers), try disabling them for a bit and see if Magis still dies.
- Corrupt WebView / system components
Some apps like Magis use WebView or Chrome internally. Try:
- Update Android System WebView (or Chrome) from Play Store
- Clear cache for Android System WebView
On iOS, if you’re on a very old minor version, updating to the latest point release can quietly fix embedded web stuff.
- “Features not loading” vs full app crash
Those might be two separate issues:
- Features not loading = network / API / adblock / VPN / DNS problems (as @mikeappsreviewer covered)
- Random crashes = memory / device / account / Magis bug
So test offline mode: - Turn on airplane mode
- Open Magis
If it still crashes fast offline, that’s more an app/device bug than network blocking.
- What to send to support so they actually investigate
Since you already tried reinstalling, when you contact them, don’t just say “it crashes.” Include:
- Phone model & OS version
- Exact Magis version
- “Crashes after ~X seconds on [screen name]”
- Rough time & timezone when it crashed so they can match logs
- Mention any VPN, DNS, or security apps you use
Also explicitly tell them you’ve already reinstalled, cleared cache/data, and tried another network. That usually moves the ticket past the copy‑paste script stage.
- Quick sanity check on another device
If you can log into Magis on any other phone or tablet:
- If it behaves the same, that screams “account/server issue.”
- If it’s fine there, your main phone’s environment is the likely problem, not the app itself.
If you want to post your device model, OS version, and which screen in Magis is the main trouble spot, people here can probably guess whether this is a known combo that’s just buggy right now or something weird on your setup.
Couple of extra angles that build on what @mike34 and @mikeappsreviewer already covered, without rehashing their checklists.
- Ignore “just reinstall” advice for now
You already did that. If the Magis App is still crashing in the same spots after a clean reinstall plus data wipe, you are probably not dealing with a simple cache glitch. Treat it as either:
- a bug in the current build for your device/OS, or
- a backend / account issue.
- Look for a specific app build problem
Both replies focused a lot on your device, but sometimes the app version itself is the culprit. If Magis has a “version history” or “what’s new” section in the store, check whether:
- A lot of recent reviews mention crashes on your phone model or OS version.
- The last update was very recent and mentions big changes (UI overhaul, new feed, new messaging).
If so, you might actually want to avoid the latest version temporarily if your platform lets you:
- On Android, some stores let you install an earlier version or opt into a beta that fixes the bug.
- If you are on a beta, consider leaving the beta and going back to stable.
- Try to isolate a graphics / rendering issue
Magis App could be choking on specific UI elements. To test this:
- Turn off any system-wide “force dark mode” or color filters.
- Reduce animation or disable fancy transitions in system settings.
- If your device has a “high refresh rate” option, set it back to standard for a bit.
If crashes stop or change in frequency, it points at a rendering bug with how Magis draws certain views.
- Storage integrity, not just free space
Everyone says “free up space,” but:
- Run your phone’s built-in storage check or file system scan if available.
- If you store Magis data on SD card, move it back to internal storage. External cards cause weird, intermittent read errors that look like random crashes.
- Background sync & notifications
Magis App might crash around push notifications or background sync:
- Temporarily disable Magis notifications in system settings and inside the app (if you can get that far).
- See if the “random” crashes line up with times you normally receive alerts.
If crashes drop with notifications off, mention that clearly when you contact support. That points to a push / deep link bug.
- Heat and throttling
This is overlooked a lot:
- Use Magis for a session while the phone is cool, without charging, in a normal environment.
- Then try while charging or when the phone is hot (gaming before opening Magis).
If crashes spike only when the device is warm or charging, Magis might be hitting a race condition when the CPU/GPU gets throttled. Not something you can “fix” yourself, but very valuable detail for support.
- Event timing for support logs
When you finally reach out to Magis support, in addition to the device + OS + Magis version that the others suggested, add:
- 2 or 3 exact crash timestamps with timezone, like “Crashes at ~14:52 and 14:59 on Feb 1, local time.”
That makes it much easier for their engineers to pull your logs from the backend without guessing.
- Pros & cons of sticking with the Magis App right now
Pros:
- If it works on another device or test account, your data and general ecosystem are probably fine.
- Issues that are reproducible on specific screens are typically fixable in a short app update.
- Strong chance that once the offending module is patched, performance will be normal without you changing phones or accounts.
Cons:
- If this is an account-level data bug, you are stuck until Magis support touches your case.
- If the crash is tied to your exact device/OS combo, you might sit through a few releases before they nail it.
- You may lose trust in reliability if it keeps dying during important flows (payments, uploads, live features).
- Quick compare with what @mike34 and @mikeappsreviewer suggested
- They leaned hard into battery/VPN/cleanup/network. Those are valid and often fix things.
- I would not spend too long tweaking every battery and DNS setting if you can prove the same account crashes on multiple networks and works fine on a different account or device. At that point, the network is almost certainly not the root cause.
If you can share:
- Device model
- OS major/minor version
- Rough description like “Magis App dies as soon as I open [screen name] or tap [button]”
people here can usually guess whether you’ve hit a known regression in the current Magis App build or if it smells more like your specific account data got messed up.