Anyone using Skye Business Webapp (!!) with Safari 12 (on Sierra, HighSierra/Mojave?). With Safari 12 it won't work here anymore...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacOS Mojave - App Compatibility
- Thread starter Apple_Robert
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
How did u managed to make it work? For me it's crashing always... and I don't know what to do to it...
I had Lightroom 6 (now at version 6.14) installed since Sierra on my MBP 15" (2015 no dGPU). I upgraded to HS, then to Mojave DP since version 1, just to test Lightroom. It worked without any noticeable problem for me. This is important to me as this is the last retail version of Lightroom, and Mojave will probably be the last version to support it (I got the same warning as with 32 bit apps).
Enigmo 2, and most other from Pangea Software, now crash upon launch.. Any idea why? Contains i386 binaries.
EDIT:
Turns out to be Carbon related..
EDIT:
Turns out to be Carbon related..
Last edited:
As they say, Lightroom 'just works' for me. And that is on 2 Macs, one of which I updated to the beta and the other was a clean install of the beta (and my apps). You will need to look in console logs for errors when you start Lightroom.
Interesting. It crashes on launch for me, every single time. I emailed them and they replied that they are "working on Mojave compatibility". They also extended my subscription by three months, so clearly they are aware that something's not right and that they need to make some kind of amends.
I only found this post: https://communities.vmware.com/message/2798926#2798926
I'm very curious as well! Hopefully someone can confirm this. I won't be upgrading before, since I need it for work
I just installed macOS Mojave this afternoon without difficulty, but found that two of my apps needed updating as a result. They are Printopia (to v3.0.12) and anyTrans (to v7.0.1). All of the other apps that I have had already been updated to newer versions prior to my upgrading to Mojave.
I would say that my biggest issue in migrating from macOS High Sierra to macOS Mojave has been the password manager, 1Password. In macOS Mojave, Apple has made certain changes to its operating system that resulted in the "browser extensions" used by many password managers to become inoperable. I didn’t know this at the time I chose to upgrade to Mojave but have since learned that these changes have resulted in such dynamic changes to 1Password that its developer created a new type of browser extension that he has dubbed the “1Password X project”. Basically, what I had to do was to upgrade my version of 1Password to v7.2 (the one designed for Mojave), throw out my existing “works with High Sierra” (Google) Chrome browser extension, and replace it with a new "1Password X" browser extension. The 1Password v7.2 upgrade was made somewhat difficult because even though I had purchased my copy of 1Password through the App Store, the v7.2 version of 1Password has yet to be posted there (as of this writing) and must be downloaded instead from the vendor’s (agilebits) web site, URL: https://app-updates.agilebits.com/product_history/OPM7. The new v7.2 browser's "1Password X" browser extension is already available in the Chrome Web Store.
With the new software in hand, you upgrade your existing copy of 1Password (I had v7.1.2 previously) and swap out your existing browser extension for the "1Password X" one. Once this is done, you’ll find that 1Password now works differently in the Chrome browser. When needing to fill in a password at any given website, instead of clicking on the browser extension icon (in the extension tray) to fill in the password as before, the 1Password icon actually appears on the web page where the password needs to go. You click on that icon, your login password choices appear, and you select one which, in turn, supplies the password to the web page’s password field. One of the casualties of this approach you will likely notice is that you will now need to press the Return key to submit your Password choice to the web page. In the past, the old 1Password browser extension offered an “auto submit” feature which supplied the password and automatically submitted it to the web page and the new "1Password X" extension, which is a stand-alone program unto itself, does not. It is my understanding that because of the underlying programming changes made to macOS within Mojave, the addition of an “auto submit” feature is no modest undertaking for the developer and therefore does not exist presently.
This is not just a Chrome issue with 1Password. It exists also with the Safari and Firefox web browsers as well. When you first launch Safari, after upgrading to Mojave, and go to use 1Password, Safari then tells you upfront that you need a new browser extension that is only available from its Safari Extensions collection. This is a very straight-forward process and easily accomplished.
With Firefox, the process of upgrading is much the same as that for Google Chrome with the only real difference being the you’ll find the new "1Password X" browser extension in the Firefox Manage Add-Ons section of the browser rather than the Chrome Web Store.
All this change takes some getting used to, but other than the loss of the “auto submit” feature, I found that this new version of 1Password pretty much worked the same as the previous one.
Also, I just discovered that if you are using a Logitech keyboard, you should update your Logitech Options application. While working with Excel and Evernote, I discovered that the keyboard shortcuts for Copy and Paste had been remapped from Cmd+C and Cmd+V to Ctrl-C and Ctrl+V (as a result of my upgrading to macOS Mojave). I checked my copy of the Logitech Options app and found that an updated version was available. So I updated and now the keyboard mapping is correct again. Thank you Logitech!
I would say that my biggest issue in migrating from macOS High Sierra to macOS Mojave has been the password manager, 1Password. In macOS Mojave, Apple has made certain changes to its operating system that resulted in the "browser extensions" used by many password managers to become inoperable. I didn’t know this at the time I chose to upgrade to Mojave but have since learned that these changes have resulted in such dynamic changes to 1Password that its developer created a new type of browser extension that he has dubbed the “1Password X project”. Basically, what I had to do was to upgrade my version of 1Password to v7.2 (the one designed for Mojave), throw out my existing “works with High Sierra” (Google) Chrome browser extension, and replace it with a new "1Password X" browser extension. The 1Password v7.2 upgrade was made somewhat difficult because even though I had purchased my copy of 1Password through the App Store, the v7.2 version of 1Password has yet to be posted there (as of this writing) and must be downloaded instead from the vendor’s (agilebits) web site, URL: https://app-updates.agilebits.com/product_history/OPM7. The new v7.2 browser's "1Password X" browser extension is already available in the Chrome Web Store.
With the new software in hand, you upgrade your existing copy of 1Password (I had v7.1.2 previously) and swap out your existing browser extension for the "1Password X" one. Once this is done, you’ll find that 1Password now works differently in the Chrome browser. When needing to fill in a password at any given website, instead of clicking on the browser extension icon (in the extension tray) to fill in the password as before, the 1Password icon actually appears on the web page where the password needs to go. You click on that icon, your login password choices appear, and you select one which, in turn, supplies the password to the web page’s password field. One of the casualties of this approach you will likely notice is that you will now need to press the Return key to submit your Password choice to the web page. In the past, the old 1Password browser extension offered an “auto submit” feature which supplied the password and automatically submitted it to the web page and the new "1Password X" extension, which is a stand-alone program unto itself, does not. It is my understanding that because of the underlying programming changes made to macOS within Mojave, the addition of an “auto submit” feature is no modest undertaking for the developer and therefore does not exist presently.
This is not just a Chrome issue with 1Password. It exists also with the Safari and Firefox web browsers as well. When you first launch Safari, after upgrading to Mojave, and go to use 1Password, Safari then tells you upfront that you need a new browser extension that is only available from its Safari Extensions collection. This is a very straight-forward process and easily accomplished.
With Firefox, the process of upgrading is much the same as that for Google Chrome with the only real difference being the you’ll find the new "1Password X" browser extension in the Firefox Manage Add-Ons section of the browser rather than the Chrome Web Store.
All this change takes some getting used to, but other than the loss of the “auto submit” feature, I found that this new version of 1Password pretty much worked the same as the previous one.
Also, I just discovered that if you are using a Logitech keyboard, you should update your Logitech Options application. While working with Excel and Evernote, I discovered that the keyboard shortcuts for Copy and Paste had been remapped from Cmd+C and Cmd+V to Ctrl-C and Ctrl+V (as a result of my upgrading to macOS Mojave). I checked my copy of the Logitech Options app and found that an updated version was available. So I updated and now the keyboard mapping is correct again. Thank you Logitech!
Last edited:
Based on posts here, it appears that Photoshop CS6 does work with Mojave although some people are having issues saving files.
Does anyone still have CS5 and can you confirm if it works with Mojave? If not, is there anyway I can somehow download and purchase a key for CS6?
Does anyone still have CS5 and can you confirm if it works with Mojave? If not, is there anyway I can somehow download and purchase a key for CS6?
Last edited:
In Mojave 18A391 (release version) I noticed that a .pkg that wants to install 32-bit software is now blocked. The installer will just do nothing when clicking „install“. I am talking about the attempt to freshly install 32-bit software that previously worked fine when doing an upgrade installation with the Mojave betas.
Any way to switch this off?
Sorry if this has been discussed before.
Last edited:
I cannot edit the wiki. Found the following apps to work that I use in my workflow:
Cyberduck
Docker
Irvue
Netbeans
Cyberduck
Docker
Irvue
Netbeans
Anyone got Bartender3 working after installing the official Mojave release? It just won't load on my system with SIP enabled (works with SIP disabled, but that's just useless).
I tried the developer's hint to no avail: https://www.macbartender.com/b3_knowledge/not-starting-at-login. Any other suggestions?
I tried the developer's hint to no avail: https://www.macbartender.com/b3_knowledge/not-starting-at-login. Any other suggestions?
Worked fine for me... prompted me to enable the helper app and afterwards, it seems to be functioning perfectly.
or check system preferences>security & privacy; under privacy>accessibility, is bartender there, checked?
My first experience using my go to app "CarbonCopyCloner" on Mojave APFS ended in a disappointment.
I'm sure I've read on this forum of users having success cloning APFS systems, but this is what I get when I attempted to clone
a new installation. APFS -> APFS.
I'm sure I've read on this forum of users having success cloning APFS systems, but this is what I get when I attempted to clone
a new installation. APFS -> APFS.
Make sure you've installed the latest update to little snitch if you're upgrading. I found out the hard way today, mac was freezing, CPU running at 100 percent ended up having to restore the unit back to high sierra. Installed the update for little snitch, no further issues
Boom3D will install fine, the audio component does not work.There is no sound
Boom3D will install fine, the audio component does not work.There is no sound
