Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Each atom update adds a new item to "Open with" #1720

Closed
thedaniel opened this issue Mar 7, 2014 · 62 comments
Closed

Each atom update adds a new item to "Open with" #1720

thedaniel opened this issue Mar 7, 2014 · 62 comments
Labels

Comments

@thedaniel
Copy link
Contributor

support/6be6d1eaa44911e38bd5c0467822a465?page=1

screen shot 2014-03-06 at 4 21 49 pm

@thedaniel thedaniel added the bug label Mar 7, 2014
@thedaniel
Copy link
Contributor Author

I told a user I'd update him when this gets fixed / how to mitigate it, so here's a reference so I don't forget: support/f26cab94a33711e38ba89562ca18aa3b?page=1

@probablycorey
Copy link

@probablycorey
Copy link

Hey Mac Dudes,
Is seeing multiple instances of Atom when you click 'open with' because we are doing wrong with Squirrel?

/cc @dannygreg @jspahrsummers @joshaber

@joshaber
Copy link
Contributor

joshaber commented Mar 7, 2014

It seems totally possible this is Squirrel. Any idea what SHA you're on?

We had a bug where installed updates weren't getting deleted: Squirrel/Squirrel.Mac#95. It was fixed in Squirrel/Squirrel.Mac#103.

/cc @keithduncan

@probablycorey
Copy link

We are on
Squirrel/Squirrel.Mac@c7915326d9e7ca7964f5bf7d83cc6cf4b51793e3so
it should have that PR.

On Fri, Mar 7, 2014 at 12:05 PM, Josh Abernathy notifications@github.comwrote:

It seems totally possible this is Squirrel. Any idea what SHA you're on?

We had a bug where installed updates weren't getting deleted:
Squirrel/Squirrel.Mac#95Squirrel/Squirrel.Mac#95.
It was fixed in Squirrel/Squirrel.Mac#103Squirrel/Squirrel.Mac#103
.

/cc @keithduncan https://github.com/keithduncan

Reply to this email directly or view it on GitHubhttps://github.com//issues/1720#issuecomment-37062377
.

@joshaber
Copy link
Contributor

Hmm, nothing else sticks out then. Can you find where those duplicate copies are?

@probablycorey
Copy link

For me they files were located all over the drive (my fault, not squirrels.) But I can't figure out why the user from the halp ticket was having this problem. I'll scour around for more details.

@dannygreg
Copy link

It's worth noting that Atom is by no means the only sufferer of this. I've considered this a bug in OS X for a while.

@izuzak
Copy link
Contributor

izuzak commented Apr 11, 2014

Users are still reporting this

screen shot 2014-04-11 at 10 41 09 am

@joshaber
Copy link
Contributor

It'd still be interesting to know if there are actually that many copies sitting around, or if Launch Services is just up the butt.

@izuzak
Copy link
Contributor

izuzak commented Apr 11, 2014

It'd still be interesting to know if there are actually that many copies sitting around

That doesn't seem to be the case -- the user sent a list of all files named "atom" on his drive and I see only one Atom app in there..

support/1d4db834c18411e3892d05e3b48dbe89

@probablycorey
Copy link

I also had them run mdfind "kMDItemCFBundleIdentifier == 'com.github.atom'" and the only value returned was /Applications/Atom.app. So I'm stumped on this one.

@jspahrsummers
Copy link

You may want to have them try rebuilding their Launch Services database.

@izuzak
Copy link
Contributor

izuzak commented Apr 29, 2014

Note to self: let users know after this is fixed by posting an update on this forum thread.

@stmcintyre
Copy link

Thanks @jspahrsummers, rebuilding the launch services database and restarting finder has fixed this for me.

@jspahrsummers
Copy link

Great to hear! ✨

@bajabob
Copy link

bajabob commented Aug 7, 2014

screen shot 2014-08-06 at 7 40 17 pm

Yeah.... this is getting out of hand.

@thedaniel
Copy link
Contributor Author

Did this get fixed? Both @tombell and I now only see 129 in our Open With menu.

@ithinkihaveacat
Copy link

Sucks to be you. Me, I'm down to 8, which is basically 1 with a small
rounding error.
On Sep 17, 2014 6:40 PM, "Daniel Hengeveld" notifications@github.com
wrote:

Did this get fixed? Both @tombell https://github.com/tombell and I now
only see 129 in our Open With menu.


Reply to this email directly or view it on GitHub
#1720 (comment).

@jspahrsummers
Copy link

As noted above, this is a LaunchServices issue.

@thedaniel
Copy link
Contributor Author

It's strange that it would 'fix itself' but i guess that's the dark and arcane way of launchservices.

@carstenhag
Copy link

Is this issue actually still relevant? Should probably be closed...

@benogle
Copy link
Contributor

benogle commented Jan 19, 2015

Closing. If anyone still has this issue, please comment!

@benogle benogle closed this as completed Jan 19, 2015
@MarkMurphy
Copy link

I'm still having this issue 0.205.0 and 0.207.0 both appear in my "open with.." context menu.

@zaridan
Copy link

zaridan commented Aug 18, 2016

Found this issue while looking for a solution to this annoyance. Confirmed still an issue.

@humanfactors
Copy link

Still affecting Atom 1.99. Please can someone work out what is causing this?

@jakeywan
Copy link

Yup, same issue here. Super annoying.

@vacantgeologist
Copy link

Same here...

@rfreitas
Copy link

rfreitas commented Nov 2, 2016

Still a problem

@caioiglesias
Copy link

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user ; killall Dock

source

@jwfehr
Copy link

jwfehr commented Nov 17, 2016

I am having this issue with atom 1.12.1 1.12.2 and 1.12.3 however I have the ability to open the different versions. ex. I currently have 1.12.1 and 1.12.3 running at the same time. Yet when I search for atom in finder I only get one executable. Any Ideas?

I already rebuilt my launch services database.

@sergiouceda
Copy link

I had the same issue. I uninstalled/reinstalled and it got fixed. I think it could also be related with having the old version icon pinned on the dock. I hope it helps.

@galvax
Copy link

galvax commented Dec 2, 2016

@sergiouceda that solved it for me after reading your comment. Removed, the icon from the dock and everything fixed itself 🎉

@MarkMurphy
Copy link

Confirmed. Removing the icon from the dock also solved it for me. Obviously I don't want to have to do this every time so hopefully this discovery helps someone address this problem.

@wbednarski
Copy link

This issue just showed up for me. I have version 1.12.7. However, when I use the context menu in GitHub for Mac it opens separate Atom version 1.12.5. I uninstalled Atom (removing all library files), and the issue persists. I've also tried to upgrade that strange phantom Atom that is seen only by GitHub Desktop but it fails to update, after the restart, it is still old version 1.12.5.

@theflofly
Copy link

Same problem whereas as don't have the icon pinned in the dock.

@oxbits
Copy link

oxbits commented Jan 15, 2017

USE WITH CAUTION (per @stephendavidsmith below):

If you are having this issue, temporary work around...

In terminal:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

Then Relaunch Finder - hold down alt/option key and right click the Finder icon in the Dock > Relaunch

It worked for me.

:-D

From:
http://www.hongkiat.com/blog/mac-remove-duplicate-right-click-menus/

@mPanasiewicz
Copy link

THX @oxbits It worked for me.

@rameshvr
Copy link

rameshvr commented Feb 6, 2017

emptied the trash, it solved for me. the older version stays in your mac trash. try deleting that.

@stephendavidsmith
Copy link

Use @oxbits solution with a bit of caution - it didn't work for me, but in my case it did mess up some of my file associations

@oxbits
Copy link

oxbits commented Feb 23, 2017

@stephendavidsmith yeah, seemed good at first, but now it does some sort of "search" to determine file associations, and that takes a little longer than it seems it should (but it did get rid of the multiple atoms all appearing at the same time)

@blakeperdue
Copy link

Consistently happens to me over time. I also have zero other apps that have this issue. I realize it may be a Mac issue but would love if Atom could figure out a workaround to this issue :)

@ToddMurphy92
Copy link

In the same boat as @blakeperdue

@blakeperdue
Copy link

I actually noticed this happening with one other app: Skitch. That would imply it is a MacOS issue. However, there's clearly something different in how apps like Skitch and Atom are doing versioning with the OS. Other apps do not show a version number in that Finder context menu, such as Google Chrome, Safari, Adobe CS, VLC.

But, then there are many apps that do list the version number: Affinity Designer, Sketch, Skitch, iBooks, and even xCode! So, I'm at a loss.

I'd love for an easier solution than wiping all the Finder data around apps. It's taking a sledgehammer to the problem. Is there not a more simple way of taking a scalpel and cutting out the old Atom versions from the OS?

@david-ciamberlano
Copy link

I found that after an update, older versions of the App remain in the "~/Library/Caches/com.github.atom.ShipIt/" folder.
Deleting them seems to solve the problem...

@blakeperdue
Copy link

@david-ciamberlano Wow, awesome find. That worked for me!!

@blakeperdue
Copy link

blakeperdue commented Jul 26, 2017

So, deleting the contents of ~/Library/Caches/com.github.atom.ShipIt does fix the Atom issue. But, I tried that with other apps (like Skitch) and it did not work. The ShipIt suffix I'm guessing is an Electron distribution thing as other apps have a similar folder (com.postmanlabs.mac.ShipIt for example).

So, I'm guessing this fix will work for Electron-based apps, but not for other apps like Skitch 😢

@matthewpoer
Copy link

rameshvr commented on Feb 6
emptied the trash, it solved for me. the older version stays in your mac trash. try deleting that

That's dumb. Totally worked.

@lock
Copy link

lock bot commented Mar 30, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests