Not opening in Atom 1.12.0

[nahuelhds]

Hi after upgrading to Atom 1.12.0 the package doesn't browse through my saved FTP connections neither to my latest opened files.

I'm on Windows 10 64 bits. Atom 1.12.0, as said.

Thanks for such a great package

[jcase069]

I'm having this problem too, on Mac OS X Sierra.

[chrizonix]

I'm also having this problem on Atom 1.12.0. Win7. When opening the hosts I only see the hour glass.

[tlygnersjo]

I'm also having this problem (nothing happens when I'm opening "browse hosts" on MacOS Sierra. What could be the problem? @sveale

[jeffaustin81]

I am having the same issue. Here is a screenshot with the console errors.

[tlygnersjo]

I solved it by clicking on the red bug icon in the bottom right corner of atom and "rebuild" (can't remember what was rebuilt but some package remote-edit had as a dependency).

[jeffaustin81]

I actually don't have a red "bug" icon showing. Is there another way to run "rebuild"?

[tlygnersjo]

@jeffaustin81 Ok, a while ago my remote-edit appended strange data to the end of my remoteEdit.json. Have you checked that remoteEdit.json actually is a valid json array?

[jeffaustin81]

Yeah I ran it through a json validator On Mon, Nov 14, 2016 at 11:03 AM Tony [email protected] wrote:

@jeffaustin81 https://github.com/jeffaustin81 Ok, a while ago my remote-edit appended strange data to the end of my remoteEdit.json. Have you checked that remoteEdit.json actually is a valid json array?

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/sveale/remote-edit/issues/206#issuecomment-260428854, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzSFNtk7iMPXhiLl8EZ_Q-6z0HIg3FCks5q-LCLgaJpZM4Ku2Q4 .

[civersen]

Same issue here. As jeffaustin81's screenshot suggests, doesn't look like it can find the 'remoteEdit.json' file (maybe the ~ expansion isn't happening?)

As a workaround, setting the 'Default path to serialize remoteEdit data' path in the remote-edit settings page to the full path (eg, 'C:/Users/accountName/.atom/remoteEdit.json') and restarting Atom worked for me.

[nahuelhds]

I've deleted my remoteEdit.json today and I've created a new FTP connection for testing purposes. The remoteEdit.json is not created anymore and I still not seeting my connections, not even the one I've just created... I think that the package just crashes with the new version of Atom

[jeffaustin81]

@civersen That worked for me! Thanks

[melankh]

Same problem with Atom 1.12.7 on Win10 and remote-edit 1.8.24

@civersen's workaround works for me. Thanks a lot !

[dmase44]

I've had the same issue since the 1.12.0 update thru 1.12.4 and downgraded to 1.11.2 and it works fine. Some how, the upgrade 1.12.7 got past me. I figured it had to do w/ a path issue getting the blank host window. I did get the remote browse to work by going into the remote-edit setting and entered in the full path to the remoteEdit.json file: C:\Users\myname\.atom\remoteEdit.json to replace the default entry ~\.atom\remoteEdit.json. It now works as it should. Also I keep a backup of the remoteEdit.json file to replace the new one when these issues arise so I don't have to go through adding all the hosts again. Hope this helps.

[d4rkd0s]

I am still having this issue, what is the status of this? Is the fix to simply downgrade Atom on Windows 10?