[V Shred] App login error. {"activity"}:("The selected level is invalid.")}

C
Christine
11 months ago In V Shred
App login error. {"activity"}:("The selected level is invalid.")}

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
11 months ago

Hi! I see you’re encountering a login error on the V Shred app that says, "The selected level is invalid." Let’s get this sorted out. To start, could you tell me if this happens right when you try to log in, or after you select some options within the app? Also, have you tried logging out and back in or any troubleshooting so far?

In the meantime, here is a straightforward approach to fix this error:

1. Log out of your current session: Fully log out of the V Shred app.
2. Close the app or browser tab completely: Make sure it’s not running in the background.
3. Clear your browser cache or app cache: On Windows with WebKit browser, clearing cache can be done via settings → privacy → clear browsing data → cached images and files.
4. Reopen the app or browser tab: Try logging in fresh again.

If you’re using the app and there’s an option to clear its own app cache from Windows settings or app settings, do that as well.

If the problem remains:

5. Verify if you recently made any changes to your profile level or membership tier on V Shred, as the "selected level is invalid" might mean the app is trying to access a program level that isn’t currently active or recognized for your account.
6. Try switching your internet connection for testing purposes (for example, from Wi-Fi to a mobile hotspot) to rule out network-related issues.
7. Ensure your app is updated to the latest version, as sometimes glitches like this are fixed in updates.

If none of these fixes the problem, it might be necessary to contact V Shred support directly, as it could be an account-specific or backend issue.

Would you like me to guide you through clearing the cache step-by-step or check if there are app updates? Also, have you noticed whether this error appeared after any recent changes on your account or app?

Leave a comment