Hi,
The app usually works fine, but sometimes if I leave it in the background for a few hours and then open it again, the whole interface turns white (icons too) and it crashes.
It’s happened to me on a few Samsung phones already. I reached out to support but didn’t get much help.
Has anyone else run into this? Any tips on how to fix it?
Thanks!
Hi @fgtv…
I’m experiencing exactly the same behavior in my application.
In my case, the app works normally during active use. The issue appears when I leave it in the background for several hours (for example, 4–9 hours or more) and then open it again.
When returning to the app:
The interface is visually displayed, but the bottom bar colors change unexpectedly.
Some links stop working.
The bottom bar buttons (generated by the platform itself) do not respond.
In some cases, the screen turns completely white before crashing.
I have also received reports from users on both iOS and Android experiencing the same behavior, so this is clearly not limited to a single device.
It is important to note that the application is not native; it operates as a WebView that first loads the AppMySite environment and then renders the web pages. When even the bottom bar created by the platform itself becomes unresponsive, it is difficult to attribute the issue solely to the client’s server. Suggesting that this is only a server-side problem shifts responsibility away from the app framework.
Support has indicated that it might be an issue with my server and suggested that users simply force-close the app and reopen it when it happens. However, this does not seem to be an appropriate solution from a user experience perspective, especially considering that the behavior occurs after several hours of inactivity — which is completely normal in real-world mobile app usage.
If I had known this kind of instability could occur under normal usage conditions, I would not have contracted the service.
Based on the observed pattern, this appears more consistent with a WebView restoration issue after being suspended in the background rather than a server or content-related failure.
I am sharing this because it clearly does not seem to be an isolated case and may require a deeper review of how the app lifecycle is being handled.
Please let me know if you’ve managed to resolve it.
HI @appdeveloper , thanks for your reply.
I haven’t been able to fix it: I’ve tried many options and, to rule out my website/server or any external content, I even created a custom app with no links to any website, using only the platform’s features. Even so, when the app stays idle or in the background for a while (hours), when coming back it gets stuck (sometimes showing a white screen).
Based on these tests, it seems more related to the app’s lifecycle and how the WebView is restored when returning from the background, rather than the content being loaded.
Please let us know if you’ve been able to resolve it.
@fgtv and @appdeveloper
Hey there!
Thanks for sharing your detailed observations with the community.
However, it’s important to clarify that keeping a mobile app open in the background for extended periods such as 8–9 hours for testing purposes is generally not considered a supported usage scenario on mobile platforms.
Both iOS and Android manage apps very aggressively when they remain idle in the background for long durations. During this time, several things can happen at the operating system level, such as:
The app may be automatically terminated by the system to free memory.
The app may remain suspended in the background.
When reopened after a long idle period, the app may restore partially or behave unexpectedly due to OS-level memory and lifecycle management.
This behavior is part of standard mobile OS design and does not necessarily indicate a problem with the app framework itself.
In practical day-to-day usage, when users return to an app after long inactivity, the system typically reloads or refreshes the application state. For the most stable experience, our recommendation is to close (kill) the app completely and relaunch it fresh before using it again if it has remained inactive for many hours.
Additionally, the behavior you described can sometimes be influenced by other factors such as:
WebView caching behavior
Device storage availability
Individual device settings or battery optimization rules
Device-specific memory management
Since these variables differ across devices and environments, the experience may vary from one user to another.
We appreciate you raising this here, as discussions like this help clarify platform behaviors for everyone in the community.
@Nancy_AppMySite ,
Thank you for your reply and for the clarity in your explanation about how mobile operating systems handle background apps. I understand that resource management varies depending on the operating system and device, and I agree that there are multiple factors involved.
However, I would like to point out that I have tested numerous apps under similar conditions, and none of them exhibit this kind of blocking or crashing behavior when reopening the app after several hours in the background. It’s true that the issue doesn’t occur if I fully close the app before reopening it, but from a user experience standpoint, most users typically do not do this.
For this reason, it would be very valuable if you could consider exploring and implementing improvements in this area, so that the app’s behavior remains stable and user-friendly even after long periods of inactivity. I’m confident that this would significantly enhance the experience for all users of the platform.
Thank you for your attention and for the ongoing dialogue focused on improving the product.
@fgtv
Thank you for your thoughtful response and for sharing your testing experience in detail. We truly appreciate the time you’ve taken to explain the situation and provide constructive feedback.
We have noted your suggestion as a feature improvement request and have passed it along to our technical team for consideration in future updates. Feedback like yours helps us better understand real user scenarios and identify areas where the platform can continue to improve.
Thank you again for your valuable feedback and for contributing to the community discussion. We appreciate your input and your continued support of the platform.
Hi @Nancy_AppMySite ,
I’ve actually had this exact same problem. Users were getting blank white screens and buttons on startup, which only fixed itself if they completely closed and restarted the app.
It got to the point where I just unpublished it—it’s way too hard to explain that workaround to every single user. AppMySite is an awesome platform overall, but it would be amazing if you could add a feature to force-close or reload the app automatically to prevent this.
Hey @Carom
If you are referring to the behavior where the app shows a blank or white screen after being left idle for several hours (typically 5–9 hours) and then reopened, please note that this has already been forwarded as a feature improvement request. We have shared this feedback with our technical team for consideration in future updates.
However, if this issue was occurring frequently without the app being left idle for long periods, that would not be expected behavior.
In that case, we recommend reaching out to our support team directly through the dedicated support channels with details about your app and the steps to reproduce the issue. Our team will be happy to investigate and assist you further.