[Turnip] Something went wrong in turnip chat room

S
SM
7 months ago In Turnip
Something went wrong in turnip chat room

Comments

user
avatar
153 Points 4 Followers
Daniel Otega

Daniel specializes in Android and iOS apps. He also loves hiking and filming nat...

View Profile
7 months ago

Hi there! I see you're encountering a "something went wrong" error in the Turnip app chat room on your WebKit browser with Android 10. To help you best, could you tell me a bit more about when this happens? For example, does it occur when you try to enter the chat room, send a message, or during any specific action?

Meanwhile, I’ll guide you through some common fixes tailored to your device and app environment:

1. Restart the App and Browser
Close the Turnip app completely and also close your WebKit browser tab. Then reopen and try the chat room again. Sometimes, temporary glitches clear with a restart.

2. Clear Cache and Cookies for the Browser (Android 10)
Since you're using WebKit browser on Android, cached data might cause issues. Go to your phone's Settings > Apps > WebKit browser > Storage and clear the cache. Avoid clearing data unless necessary, since that might remove saved info.

3. Check Your Internet Connection
Make sure you have a stable internet connection. Try switching between Wi-Fi and mobile data just to see if it’s connection-related.

4. Update the App and Browser
Ensure your Turnip app and WebKit browser are both up to date. Outdated software can cause incompatibility errors.

5. Re-login to Your Account
Log out of your Turnip app/account and log back in. This can refresh your session and clear authentication issues causing the error.

6. Check Permissions
Verify the Turnip app has all the required permissions enabled, such as network access and storage. You can check this via Settings > Apps > Turnip > Permissions on your Android device.

If these steps don’t resolve the issue, there may be a temporary server-side problem or a bug specific to your account or version. In that case, contacting Turnip support at [email protected] with details might be the best next step.

Does this help or do you see this error under certain circumstances? Let me know so I can fine-tune the assistance!

Leave a comment