Hi there! I see that you’re having trouble logging into the Discogs app on your Samsung A16 running Android 10. Just to make sure I understand, you uninstalled and reinstalled the app, then logged in, but the app immediately returns you to the login screen again—is that correct?
A few quick questions to clarify: - Are you entering your login credentials manually each time? - Have you tried resetting your password recently? - Do you notice any error messages or prompts about cookies or permissions when you try logging in?
Meanwhile, here are some step-by-step solutions to try, tailored for your device and OS:
1. Clear app cache and data: - Go to Settings > Apps > Discogs. - Tap Storage. - First, hit Clear Cache, then Clear Data (this will log you out). - After that, open the app and try logging in again.
2. Check app permissions: - In the same App info screen, open Permissions. - Make sure the app has necessary permissions like storage and network access.
3. Check for system updates: - Go to Settings > Software update and see if any updates are available for your Samsung A16 or Android 10 version.
4. Try logging in via a web browser on your phone: - Open your browser and go to Discogs.com. - Log in there to confirm your credentials are accepted. - If login works on the browser, there might be an app-specific issue.
5. Disable battery optimization for Discogs app: - Go to Settings > Apps > Discogs > Battery. - Ensure the app is not restricted or optimized in a way that affects background processes.
If these don’t help, you might be encountering a known login glitch some other users have reported, where the app cycles back to the login screen despite valid credentials. A workaround some community members mentioned is to log in through a link in an official Discogs email (e.g., a notification or want list email) which can authenticate the session. Alternatively, try updating or reinstalling the app once more after a few hours in case it’s a server-side issue being resolved.
Please let me know if you’ve already tried any of these or if you want me to walk you through any step! Are you satisfied with the solution I provided so far?
Comments
Grace Wilson
Grace coordinates cross-functional teams to deliver software on time. She’s also...
Followed by
Hi there! I see that you’re having trouble logging into the Discogs app on your Samsung A16 running Android 10. Just to make sure I understand, you uninstalled and reinstalled the app, then logged in, but the app immediately returns you to the login screen again—is that correct?
A few quick questions to clarify:
- Are you entering your login credentials manually each time?
- Have you tried resetting your password recently?
- Do you notice any error messages or prompts about cookies or permissions when you try logging in?
Meanwhile, here are some step-by-step solutions to try, tailored for your device and OS:
1. Clear app cache and data:
- Go to Settings > Apps > Discogs.
- Tap Storage.
- First, hit Clear Cache, then Clear Data (this will log you out).
- After that, open the app and try logging in again.
2. Check app permissions:
- In the same App info screen, open Permissions.
- Make sure the app has necessary permissions like storage and network access.
3. Check for system updates:
- Go to Settings > Software update and see if any updates are available for your Samsung A16 or Android 10 version.
4. Try logging in via a web browser on your phone:
- Open your browser and go to Discogs.com.
- Log in there to confirm your credentials are accepted.
- If login works on the browser, there might be an app-specific issue.
5. Disable battery optimization for Discogs app:
- Go to Settings > Apps > Discogs > Battery.
- Ensure the app is not restricted or optimized in a way that affects background processes.
If these don’t help, you might be encountering a known login glitch some other users have reported, where the app cycles back to the login screen despite valid credentials. A workaround some community members mentioned is to log in through a link in an official Discogs email (e.g., a notification or want list email) which can authenticate the session. Alternatively, try updating or reinstalling the app once more after a few hours in case it’s a server-side issue being resolved.
Please let me know if you’ve already tried any of these or if you want me to walk you through any step! Are you satisfied with the solution I provided so far?