The app suddenly crashes from the initial load for some users.

[Islam1]

I have a problem with some of my apps and some of their users. The loading of the app doesn't complete until the bar is about three-quarters full. After that, the app completely exits the app sheet and redirects to the phone's background.
What is the reason for this?

For further clarification: Two of my apps work well for some users, but this problem occurs for others. One of the users experiencing this problem tested the app on a tablet and found that the problem had disappeared, but it only occurred on his phone. He has a strong internet connection and the phone's RAM, processor, and storage capabilities are good. His phone also works well with the rest of my apps.

[bonameblisto]

Try using a new framework. I had similar problems on Android devices. After switching to a new framework, no problems.

[Islam1]

Thank you, but unfortunately, the problem still exists.

[James_McFarlane]

Having the same issue with several users and multiple apps.

[PauloExpert · Accepted solution]

Thanks for the detailed explanation, Based on your description, here’s a breakdown of what could be causing the issue, along with some steps to troubleshoot and resolve it.

✅ Summary of the Issue

Some AppSheet apps crash or exit unexpectedly during loading (~75% progress).

Only happens on certain phones, not on tablets or other devices.

The affected phones have good hardware and internet.

Other AppSheet apps on the same phone work fine.

🔍 Likely Causes

1. App Memory Usage or Complexity

If the app has large datasets, many images/files, or heavy expressions, it may consume more RAM or CPU during loading.

Some phones (even high-end ones) aggressively terminate apps using background resource optimization techniques.

2. Android Version or OEM Software Behavior

Some Android phones (especially Xiaomi, Huawei, Samsung with aggressive background policies) kill apps that use too much RAM during loading.

If the tablet has a different OS version or manufacturer, that might explain the difference.

3. Corrupt Local Cache or AppSheet App Installation

Cached data or a corrupted installation can cause crashes during loading.

Especially if the app was updated recently or if offline sync is enabled.

4. Permissions or Device Settings

Battery optimization, permission restrictions, or custom ROMs can interfere with loading.

🛠️ Troubleshooting Steps

Ask the affected users to try the following (especially the one whose phone crashes):

1. Clear Cache and App Data

Go to Settings > Apps > AppSheet > Storage.

Tap Clear Cache and Clear Data.

Reopen the app and sign in again.

2. Uninstall and Reinstall AppSheet

Uninstall the AppSheet app completely.

Restart the phone.

Reinstall AppSheet from the Play Store.

3. Disable Battery Optimization

Go to Settings > Battery > Battery Optimization.

Find AppSheet and set it to Not Optimized.

4. Check App Permissions

Go to Settings > Apps > AppSheet > Permissions.

Make sure all necessary permissions are granted (especially for storage, location, camera).

5. Enable App Logging (Optional)

In the AppSheet editor, go to Manage > Monitor > Performance Profile.

Enable "Performance monitoring" to check for issues during loading.

6. Use a Lightweight Test Copy

Create a copy of the app with:

Only the base functionality

No images or sync-heavy data

Share that with the user. If it works, the issue is likely data size or complexity.

💡 Suggestions for Long-Term Fixes

Optimize App Load Time:

Reduce the size of initial sync data (e.g., only load this week’s data).

Use security filters to load only relevant rows per user.

Remove unused columns or reduce virtual columns that are recalculated often.

Avoid Heavy Initial Loads:

Break apps into modules if you have too much in one.

Delay sync-heavy actions until after the app loads (e.g., on-demand sync).

[Islam1]

Thank you very much for your sufficient and comprehensive response. I will accept it as a solution to the problem and work on it during the coming period.