#Not staying signed in when closing app and opening again

4 messages · Page 1 of 1 (latest)

copper fjord
#

I tend to go to discord alot while playing mobile or watching a YouTube walk through so I close and open the app alot. After this update it fully logs my character out and I have to fully sign in with my two factor authentication. I think this had been brought up a few days ago but no fix seems to be in sight...

pastel epoch
#

This. It's getting unbearable to play. Can we either revert the crappy chatgpt code or get a eta on bug resolution?

warm oracle
#

Tabbing out closes my client even for a few seconds. I tried looking and changing the settings but it happens to all my mobile devices

somber nebula
# warm oracle Tabbing out closes my client even for a few seconds. I tried looking and changin...

This probably won't pertain to OP, but you can often prevent OSRS from closing on Androids by setting the OSRS apps battery usage to "Unrestricted" and also disabling battery saver modes—if any are enabled. This prevents Android from "killing" the app when it is in the background. On iOS, however, this issue is generally unavoidable due to system restrictions.

Android Fixes:
• Unrestricted Battery Usage: Go to Settings > Apps > OSRS > App Battery Usage, and change the setting to Unrestricted.
• Disable Power Saving: Turn off any battery saver or low-power modes, as these restrict background data.
• Lock the App: In your multitasking/recent apps view, some Android versions allow you to "Lock" the app so it doesn't close.
iOS:
• Disable New Renderer: I've seen some players suggest using the old renderer if switching causes instant crashes—although I'm unsure of the process.
• Check Background App Refresh: Ensure Background App Refresh is enabled for OSRS in your iPhone settings. 

If after exhausting all the above suggestions and the app continues to crash, it may be due to a lack of memory (RAM), causing the operating system to force-close the app to free up resources.

Hope this information helps. The first Android step I've listed is what fixed the issue you've described for me.