How to update Firefox when it says already up to date - macos

I am using a mac system with firefox version 52.4.1. I can't update it from About Firefox option because it says up to date. But, as I understand there are newer versions available.

Download the latest installer and reinstall it.

Related

How to update XCode installed from XIP file?

I have installed XCode 9 from XIP file and then moved it to Applications folder and it even shows up in Launchpad. I have the latest version of Sierra with security update also installed but app store doesn't seem to accept that I have it installed (Xcode) and instead of providing up with with the update it's asking me to install XCode 9.1. Is there any solution or I have to download and install the XCode 9.1 version?
There might be a way around to add some var to the path so the app store could detect it as installation form itself and update it right away!

How to upgrade xcode by keeping the previous version?

is there anyway to upgrade latest version of xcode and also keeping the previous version? Like I'll upgrade my xcode from version 8.3 to version 9.0, how can I also keep the version 8.3 in my mac? will duplicate do the job done? I'm on mac-os sierra.
The Xcode copy that was downloaded from the AppStore is always managed by the AppStore app; even if you move the bundle to a different location (folder), the next time you download Xcode from the store it will be overwritten.
You should always keep the "managed" (purchased) version up to date, and download any necessary older versions from Apple's developer website (log in needed).
In your particular case:
Update the store version from 8.3 to 9.0 (through the AppStore app)
Download the xip installer for 8.3 from Apple's Developer website, and install (for example) in /Applications/Xcode_old/Xcode.app (to avoid filename collision with Xcode 9, residing in Applications/Xcode.app)

How can I update monodevelop3.0.6 and retain mono3.0.3 in OSX?

Xamarin update reverts my mono version to 2.10.9. I don't want that as I need mono >= 3.0. F# projects will not load under mono 2.10.9. I explain more below. The issue is made more pointed as I would like to update monodevelop but not mono but I cannot choose which Xamarin updates to install. [I tried the update in the hope it would notice that my current version of mono is higher; but indeed it removed mono3.0.3 and f# 3.0 and my f# projects no longer load]
Am I missing something there? Is there a way of managing updates besides manual download and install as it seems autoupdate is broken for me? I've now reverted the update: is there a way of using my existing monodevelop, or is it necessary to reinstall it too (the same problem remains even after installing mono 3.0.3)?
My current setup appears to work:
Running mono 3.0.3 mre (beta) and monodevelop 3.0.6 on OSX Snow Leopard.
Why the dependence on mono 3.0.3? Because I need fsharpbinding for my projects and in the latest monodevelop that requires f# 3.0 and that (on osx at least) requires mono 3.0.3. I've looked at other so/sx questions but they relate to earlier versions of mono/develop.
The issue is made more pointed as I would like to update monodevelop but not mono but I cannot choose which Xamarin updates to install.
The Update dialog doesn't seem to allow you to choose a particular package to update. Regarding auto-removing Mono runtimes, it is a known bug which has been reported here.
Am I missing something there? Is there a way of managing updates besides manual download and install as it seems autoupdate is broken for me?
I usually do manual update: download the latest MonoDevelop and overwrite the old one in Applications folder. It needs a few clicks but is safer to do. I also do similarly for FSharpBinding: go to Add-in Manager --> F# Language Binding and click Update.
I've now reverted the update: is there a way of using my existing monodevelop, or is it necessary to reinstall it too (the same problem remains even after installing mono 3.0.3)?
Assume that autoupdate gives you a new MonoDevelop and erases Mono 3.0.3. After reinstalling Mono 3.0.3, you need to set Preferences --> .NET runtimes --> Mono 3.0.3 as default and possibly remove and install FSharpBinding again. You don't have to reinstall MonoDevelop once more.
That said, be cautious with autoupdate feature. Unless you are sure that all updates (Mono, MonoDevelop, FSharpBinding) are correct, don't do it.

Difficulty in uninstalling older phonegap versions

How do i uninstall an already existing version of phonegap(1.3,1.8) because i want to install the new 2.0 and it does'nt get installed without uninstalling older versions. The folder structure of my older version 1.8 does'nt have uninstall option.
Any suggestions are welcome.Thanks.
Cordova 2.0 onwards doesn't really have an 'installer' so you should be perfectly fine to leave your 1.3 if you like.
They only recommend uninstalling old versions if you are not going to use it so that the project template is removed from XCode. If you don't care about that you can leave the old version.
Just follow the upgrade steps from http://docs.phonegap.com/en/2.1.0/guide_upgrading_index.md.html#Upgrading%20Guides to start using 2.1 (which is now out and you should use)

Finding incompatibility in Firefox addon

I have an custom addon developed for our workplace (using the add-on SDK) that was originally developed for FF4.
When FF5 came out all I had to do was rebuild the XPI. FF6 was able to use the same XPI.
Now I'm trying to get it running in FF7, and it's not working. I get a "this add-on is not compatible with Firefox 7" when trying to install it.
I've read this blog post:
http://blog.mozilla.com/addons/2011/07/19/firefox-7-compat-looking-to-8/
And from what I can tell none of the changes affect my add-on.
Also running this validation test
https://addons.mozilla.org/en-US/developers/addon/validate
Yields no errors or warnings.
Any clue on how to find out what makes FF7 think it incompatible?
You should use the newest version of the Add-on SDK to rebuild your add-on. Right now, the latest version you get offered on the SDK download page is Add-on SDK 1.1, released on September 13th. It will mark add-ons compatible with everything up to Firefox 8.0a1. You are most likely using an older version, e.g. Add-on SDK 1.0 would only mark add-ons as compatible with Firefox 7.0a1.

Resources