My progress is lost

Code Feedback
1

i am sure i am logging in with the same account please help

2

Hello and welcome to the forum :partying_face:!

I’m sorry you’re having problems :frowning_face:, but where did you lose your progress? Here on Free Code Camp, CodePen, Glitch, etc.

Have you read this thread to see if there is a solution?

3

freecodecamp is where i lost my progress.

4

Which method did you use to register on FreeCodeCamp? Github, Google, Facebook or an email (short code).

5

I used Google to login

6

Is it possible that you’re not logged in? I’m not trying to be rude, but this can happen to everyone (this happens to me sometimes).

Maybe you used a different browser, cleared the storage/cookies or you session may have expired.

Could you confirm that you’re logged in with google? And make sure you’re using the same account you used to register.

7

yes i am sure i logged in with google with multiple browsers.

8

There are two different types of saved progress for Free Code Camp: your profile and your browser cache.

A list of your completed challenges is saved to your account in the FCC database. You can see the list of completed challenges by looking at your public portfolio. With a growing curriculum already over 1,400 lessons and a community of millions of people, FCC does not store every solution to every challenge in its database. When you complete a challenge, there is a modal that gives you the option to download your solution. This gives you the option to save a copy of any solution that you may want to reference later. There are some challenges which are classified as projects required for certifications. Your solutions to those can be viewed on your settings page.

Your in-editor code is saved in your browser’s local storage. Recent in-progress code from the challenge editor is also saved in your local browser cache when you run tests. If you are completing lessons and do not see your recent code, then your local storage has been cleared or something is preventing FCC from writing to your browser’s storage. This could be a browser setting, a privacy extension, or a browser version incompatibility. Especially as you get to more complicated challenges that may take multiple sessions, I strongly recommend saving your in-progress work outside of the browser cache.

This is a good opportunity to learn the ins and outs of your GitHub account, but you can also just save locally or use a service like repl.it which allows for versioning.