Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Brackets won't resume with corrupted state.json #7817

Closed
mubaidr opened this issue May 11, 2014 · 7 comments
Closed

Brackets won't resume with corrupted state.json #7817

mubaidr opened this issue May 11, 2014 · 7 comments

Comments

@mubaidr
Copy link

mubaidr commented May 11, 2014

Steps to reproduce:
Open a solution/project.
Close brackets
Start brackets

Expected:
Brackets will have opened last project.

Actual:
Brackets open the default project.

Is this a bug or this is not implemented yet?

@RaymondLim
Copy link
Contributor

@mubaidr Are you on Linux? It should work on Mac and Windows. If not, then which version of Brackets?

@mubaidr
Copy link
Author

mubaidr commented May 11, 2014

Oops, sorry. Forgot to mention that i am on Windows and using Brackets Sprint 38

Is there anyway to debug why this is happening?

@mubaidr
Copy link
Author

mubaidr commented May 11, 2014

Issue fixed. state.json was corrupted. Deleted it, now everything works fine.

@mubaidr mubaidr closed this as completed May 11, 2014
@peterflynn
Copy link
Member

@dangoor Even though state.json isn't supposed to be hand-edited, I wonder if we should have a user-visible error message when it's corrupt anyway, similar to the UI we already show for user-scope prefs?

@mubaidr
Copy link
Author

mubaidr commented May 13, 2014

I don't think any preferences are required.
-Just check if state.json is OK when brackets load
-if it is not; show a warning to user and reset it to default state
-restart brackets

@peterflynn
Copy link
Member

Yes, that's what I was referring to.

@dangoor dangoor changed the title Brackets won't resume from last state Brackets won't resume with corrupted state.json May 14, 2014
@dangoor dangoor self-assigned this May 14, 2014
@dangoor
Copy link
Contributor

dangoor commented May 14, 2014

Yes, I think it makes sense to display the same sort of dialog for state.json on the chance that someone hand-edited state.json. I'm reopening this issue with an updated subject.

I'm calling this low priority, since this should not be a common occurrence.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants