macOS X 10.15 Catalina support?

Question

macOS X 10.15 Catalina support?

silviu-bucsa opened this issue 6 years ago · 118 comments

On the Public betas of Mac OS X QLStephen.qlgenerator stopped working. I've attached a screenshot with the message I'm receiving:

I haven't found a workaround.

Thank you.

fvvliet commented 5 years ago

+1

👍11
👎5

Answer 1 · 2019-08-07T23:35:50.000Z

This is probably because of notarization enforcement. The binary just needs to be notarized by Apple. (Which I believe requires their $99 developer program subscription.)

Answer 2 · 2019-08-23T13:38:32.000Z

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

Answer 3 · 2019-08-23T14:01:54.000Z

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

This doesn't work for me.

Answer 4 · 2019-09-10T01:30:08.000Z

On the latest beta you can get by it by going to Security in system preferences after you try and open it once and hit "Allow Anyway". Still would love to see it notarized properly.

Answer 5 · 2019-10-08T00:07:39.000Z

This is probably because of notarization enforcement. The binary just needs to be notarized by Apple. (Which I believe requires their $99 developer program subscription.)

~~Not gonna lie this sounds like extortion. Open source developers should be able to freely ship their code when end users fully understand and accept the risks of using such code.~~

EDIT: @samcat116 cleared this up in the subsequent comment.

Answer 6 · 2019-10-08T00:12:33.000Z

Notarization does not require the $99/yr subscription. Just needs an Developer Apple ID and Xcode .

Answer 7 · 2019-10-08T00:23:10.000Z

On the latest beta you can get by it by going to Security in system preferences after you try and open it once and hit "Allow Anyway". Still would love to see it notarized properly.

I tried qlmanage -p README.MD for a readme file. I don't get the warning to move the plugin to the Trash, but I now get an error message in the console and the file appears the way it did if I never installed this plugin (plain text).

Testing Quick Look preview with files:
	README.MD
2019-10-07 20:18:17.998 qlmanage[32498:129283] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x6f07, name = 'com.apple.coredrag'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2019-10-07 20:18:18.054 qlmanage[32498:129283] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xb01f, name = 'com.apple.tsm.portname'
See /usr/include/servers/bootstrap_defs.h for the error codes.

On a related note, I see this message when I try the same thing for a json file with a json reading plugin. this preview cannot be safely displayed in quick look

Answer 8 · 2019-10-08T19:54:11.000Z

Just updated my operating system and got this message:

Answer 9 · 2019-10-09T05:49:59.000Z

Same here, just updated to Catalina yesterday and QLStephen stopped working.
Please update it in order to be compatible with Catalina.

Answer 10 · 2019-10-09T15:57:10.000Z

Please use thumbs up instead of "+1" or "me too" comments. They often add no value, clutter the issue's discussions, and generate unnecessary notifications to all participants, including the project's maintainers.

Answer 11 · 2019-10-09T16:03:24.000Z

If it helps, here are the docs on Notarizing Your App Before Distribution.

Answer 12 · 2019-10-09T20:44:48.000Z

@samcat116 This is what I get when I follow the instructions on this page. The app in the screen shot is an freshly created, properly code signed app that meets all of the notarization requirements. If you know something I don't I would love to be proven wrong, but from all the resources I've come across and my own personal experience it seems that the paid Apple Developer Program membership is a necessary part of notarization.

Answer 13 · 2019-10-09T20:58:38.000Z

Can you try with the CLI?
As per Notarize Your Preexisting Software under Notarizing Your App Before Distribution, you can try to Upload Your App to the Notarization Service using altool

It might look more complex, but could you give it a shot and try it out.

Answer 14 · 2019-10-09T22:17:47.000Z

@KoCMoHaBTa When following those instructions, the Archive Post-action script that it gives doesn't even export the zip file that it is supposed to export. I made my own zip file instead, tried uploading it, and got this error. I find it weird that there is a space between "provider" and the period following it, like there is supposed to be a provider name there. The command I ran is exactly the command given in the instructions (except for the file name of course). I'm not entirely sure what a provider is in this context, but I'm guessing it's related to ADP membership.

Answer 15 · 2019-10-10T08:25:25.000Z

@partheseas Check this out - https://forums.developer.apple.com/thread/119445
Looks like the message is misleading and for some reason, the tool cannot find this provider automatically.
So you have to specify it as the --asc-provider parameter, part of altool command.
In order to find your provider name - check the first post from eskimo on this thread - https://forums.developer.apple.com/thread/113798

Answer 16 · 2019-10-11T05:00:32.000Z

watching……

Answer 17 · 2019-10-11T12:05:38.000Z

Simply cross-referencing similar issues in other QuickLook plugins in case a solution surfaces somewhere :

Also, there seems to be changes in Catalina beyond notarization breaking the plugins.

Answer 18 · 2019-10-12T18:42:49.000Z

Note that sudo qlmanage -p README.md works for me, with SIP and notarization disabled (with csrutil disable and sudo spctl --master-disable).

Is the move forward to publish a version that is notarized? Or is it a different issue?

Answer 19 · 2019-10-15T09:44:57.000Z

So I tried notarizing one of the plugins with my paid developer account, and it doesn't seem to accept .qlgenerator files

I ran the xcrun alttool command, and got an error like

 1 package(s) were not uploaded because they had problems:
	/var/folders/nz/nlsr_8yn2tdblj6fcfyylv140000gn/T/62F12993-D9CA-4467-829C-0460DC836E3A/com.fiatdev.QLMarkdown.itmsp - Error Messages:
		ERROR ITMS-4064: "File extension of file 'QLMarkdown' is invalid for this software; use 'zip,pkg,dmg' instead." at SoftwareAssets/EnigmaSoftwareAsset
2019-10-15 17:40:56.282 altool[3526:23550] *** Error: ERROR ITMS-4064: "File extension of file 'QLMarkdown' is invalid for this software; use 'zip,pkg,dmg' instead." at SoftwareAssets/EnigmaSoftwareAsset

There seems to be no documentation online on notarizing QuickLook plugins either.

Answer 20 · 2019-10-15T10:16:41.000Z

Check this out -> anthonygelibert/QLColorCode#51 (comment)

Answer 21 · 2019-10-15T23:11:38.000Z

I hope description on this site might be useful.
https://glyphsapp.com/tutorials/how-to-notarize-your-plug-ins

Answer 22 · 2019-10-16T04:15:34.000Z

Thanks @KoCMoHaBTa @ahmetgeymen, I'll try this again in the coming weekend.

Answer 23 · 2019-10-17T02:44:41.000Z

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

it works for me at macOS 10.15.

Answer 24 · 2019-10-19T13:47:28.000Z

QL插件都在~/Library/QuickLook/目录，但从系统设置->拓展->快速查看，却没有允许使用此目录，但其中包含了/System/Library/Frameworks/RealityKit.framework内的几个插件。
brew cask 不允许使用root，并且/System/Library/Frameworks/RealityKit.framework只读。
很烦~ :(

Answer 25 · 2019-10-21T02:11:51.000Z

@samcat116

Notarization does not require the $99/yr subscription. Just needs an Developer Apple ID and Xcode .

You are kidding right? You only get a valid developer id, when you pay $99 for the Apple Developer program.

Answer 26 · 2019-10-22T09:38:20.000Z

~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

it works for me at macOS 10.15.

not for me. What else did you do?

Answer 27 · 2019-10-22T09:42:18.000Z

not for me. What else did you do?

I had to go to Security & Privacy in System Preferences right after you get an error message and I could whitelist it from there. I think I went: Quicklook -> error -> Security panel -> Quicklook again -> additional confirmation dialog and then it worked.

Answer 28 · 2019-10-22T09:51:56.000Z

For me just asked me in the begging to approve, after that, it's not showing that normal window approve in sucurity.
This path I could not find it: Quicklook -> error -> Security panel -> Quicklook again ->
suggestions ?

Answer 29 · 2019-10-22T09:57:51.000Z

Sorry that was unclear. I mean that I triggered an error by trying to quicklook a file using QLStephen and after that I could go to the security settings to approve it etc

Answer 30 · 2019-10-22T10:04:20.000Z

Sorry for this questions again...
Ok, If I got your logic, I run this:

root@MacBookPro _FILMs # qlmanage -p Test.mkv                                 
Testing Quick Look preview with files:
	Test.mkv
2019-10-22 13:01:01.845 qlmanage[11471:2293464] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x6e03, name = 'com.apple.coredrag'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2019-10-22 13:01:01.884 qlmanage[11471:2293464] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x1431f, name = 'com.apple.tsm.portname'
See /usr/include/servers/bootstrap_defs.h for the error codes.

After that, nothing show up.

Answer 31 · 2019-10-22T10:21:22.000Z

Perhaps an inspiration to port this to the new system can be found here anthonygelibert/QLColorCode#51

Answer 32 · 2019-10-23T00:41:47.000Z

~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

it works for me at macOS 10.15.

not for me. What else did you do?

I don't know how it happened. I tried to uninstall it and then do the same thing again, but after deleting it , the md file still can be preivewed. It confused me.

Answer 33 · 2019-10-23T00:50:45.000Z

Oh, maybe the Xcode, because it suggests me to open with it.
ps: I installed the Xcode yesterday.

Answer 34 · 2019-10-23T07:14:27.000Z

Do you have a Apple paid dev account? That according to what I'm reading can make a huge difference.

Answer 35 · 2019-10-23T11:58:51.000Z

So I was successfully able to notarise the plugin, using the steps here. Unfortunately, the signed binary still didn't work in Catalina (atleast QLMarkdown, which I tested). I didn't get security related errors, but it just failed to work.

I think these plugins will have to be re-written as System Extensions to work in Catalina.

Answer 36 · 2019-10-23T18:16:20.000Z

Solution that did a trick for me:

Disable Gatekeeper (Terminal > sudo spctl --master-disable)
Check: .ipa preview works
Enable Gatekeeper (Terminal > sudo spctl --master-enable)
Open 'System Preferences' > 'Security & Privacy' > General tab >> you will see a message at the bottom, 'QLStephen.qlgenerator was blocked from opening because it is not from an identified developer.' > Click on 'Open anyway'
It works now with enabled Gatekeeper

Answer 37 · 2019-10-24T07:33:42.000Z

2. Check: .ipa preview works

What do you mean about "Check: .ipa preview works" ?

I downloaded an .ipa app and pressed Space in Finder, nothing shows up, and tried: qlmanage -p -d1 Downloads/File.ipa and still, nothing is coming to ask me the permission on the System Preferences' > 'Security & Privacy'.

suggestions?

Answer 38 · 2019-10-24T07:48:35.000Z

It's an additional step, just to make sure that preview works.

After disabling Gatekeeper you need to restart Finder to be able to see the .ipa preview.
To restart Finder: hold 'option' button and right click on Finder icon in Dock > click Relaunch

And then after enabling Gatekeeper (and clicking on 'Open anyway') you need to restart Finder again.

Answer 39 · 2019-10-24T08:13:20.000Z

I did all of that but still doesn't show anything. Also, I did a test with a zip file with the BetterZip quick preview and also is not working.

What else I'm missing?

Answer 40 · 2019-10-24T08:24:53.000Z

Preview of zip files doesn't fork for me as well now.
But ipa - works.

If you want to see preview of archive formats you can try this:
https://macitbetter.com/BetterZip-Quick-Look-Generator/

Install it > Launch > Relaunch Finder > Try zip preview

Answer 41 · 2019-10-24T08:39:30.000Z

I did that already too, but still shows that error above.

Answer 42 · 2019-10-24T08:44:48.000Z

Because of Gatekeeper.

Please follow the steps above, and you should get it working.

Answer 43 · 2019-10-24T09:13:00.000Z

Still. there is something else that you have done in yours that I didn't in mine.
Do you need to have the Xcode installed?
have you done this too: sudo csrutil disable ?

I consider myself pretty smart, so I'm doing what you are saying to do.

Answer 44 · 2019-10-24T09:52:57.000Z

Yes, I have Xcode installed, but I think it doesn't matter.
No, 'sudo csrutil disable' didn't do.

I'm sure it should work with disabled Gatekeeper, so check the preview functionality when you have this:

(and don't forget to relaunch Finder)

Answer 45 · 2019-10-24T10:03:07.000Z

PS: the files with .md and .ipa the previews are working, but not the .apk .zip .mkv .json .js .mp3.
All the QuickPreview extensions were installed by the same way.

Answer 46 · 2019-10-24T10:04:18.000Z

Yes, I have Xcode installed, but I think it doesn't matter.
No, 'sudo csrutil disable' didn't do.

I'm sure it should work with disabled Gatekeeper, so check the preview functionality when you have this:

(and don't forget to relaunch Finder)

yeap, that it my case, even after reboot and still.

Answer 47 · 2019-10-24T11:53:03.000Z

Hm...

Not sure, but maybe try to update Homebrew.

Answer 48 · 2019-10-24T12:17:41.000Z

have done that too.

:(

Answer 49 · 2019-10-24T16:46:24.000Z

I've been experimenting with a fresh macOS Catalina install on a vm and these are the steps I can reliably make QLStephen work:

brew cask install qlstephen
Restart Finder
Open a finder window and navigate to any folder that contains a plaintext file qlstephen tries to generate a preview for. Maybe you need to trigger Quicklook explicitly by selecting the file and hitting space.
This will generate an error message saying the developer can't be verified. From "move to trash" and "cancel" choose "cancel"
Open System Preferences -> Security & Privacy and under the General tab at the Botton click "Allow anyway"
Log out and log back in
Repeat step 3
In the warning message that now appears choose "open"

Everything should be working now. If you don't have a clean install and you can't trigger the first error message anymore I would uninstall QLStephen first and restart your Mac.

Btw, depending on factors I'm not entirely sure about you can sometimes skip step 2 and/or 6

Answer 50 · 2019-10-25T03:31:01.000Z

I've been experimenting with a fresh macOS Catalina install on a vm and these are the steps I can reliably make QLStephen work:

brew cask install qlstephen

Restart Finder

Open a finder window and navigate to any folder that contains a plaintext file qlstephen tries to generate a preview for. Maybe you need to trigger Quicklook explicitly by selecting the file and hitting space.

This will generate an error message saying the developer can't be verified. From "move to trash" and "cancel" choose "cancel"

Open System Preferences -> Security & Privacy and under the General tab at the Botton click "Allow anyway"

Log out and log back in

Repeat step 3

In the warning message that now appears choose "open"

Everything should be working now. If you don't have a clean install and you can't trigger the first error message anymore I would uninstall QLStephen first and restart your Mac.

Btw, depending on factors I'm not entirely sure about you can sometimes skip step 2 and/or 6

Try this and not work for QLimagesize

Answer 51 · 2019-10-25T09:51:02.000Z

I've been experimenting with a fresh macOS Catalina install on a vm and these are the steps I can reliably make QLStephen work:

brew cask install qlstephen

Restart Finder

Open a finder window and navigate to any folder that contains a plaintext file qlstephen tries to generate a preview for. Maybe you need to trigger Quicklook explicitly by selecting the file and hitting space.

This will generate an error message saying the developer can't be verified. From "move to trash" and "cancel" choose "cancel"

Open System Preferences -> Security & Privacy and under the General tab at the Botton click "Allow anyway"

Log out and log back in

Repeat step 3

In the warning message that now appears choose "open"

Everything should be working now. If you don't have a clean install and you can't trigger the first error message anymore I would uninstall QLStephen first and restart your Mac.

Btw, depending on factors I'm not entirely sure about you can sometimes skip step 2 and/or 6

Guys, sorry but I lost my brain, there is something that we are missing.
I did also a new VM, and did this:

`
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

brew cask install betterzip
created a test .zip
test pressing Space
nothing happened
relunched Finder
nothing happened
opened once the Betterzip unckecking everything
test pressing Space
nothing happened
relunched Finder
Worked

brew cask install QuickNFO
created a test .nfo
test pressing Space
nothing happened
relunched Finder
nothing happened
brew cask install qlcolorcode
created a test .js
test pressing Space
nothing happened
relunched Finder
error about permission show up
authorized in Settings/Security
test pressing Space
nothing happened
relunched Finder
nothing happened
restarted the VM
error about permission show up / clicked open
test pressing Space
this error below show up

brew cask install quicklook-json
created a test .js
test pressing Space
nothing happened
relunched Finder
Worked
but....after other instalation below, this stopped to work. What is the logic?

brew cask install qlimagesize
created a test .nfo
test pressing Space
nothing happened
relunched Finder
nothing happened

brew cask install quicklook-csv
created a test .nfo
test pressing Space
nothing happened
relunched Finder
nothing happened

brew cask install suspicious-package
created a test .zip
test pressing Space
nothing happened
relunched Finder
nothing happened
opened once the suspicious-package app
test pressing Space
nothing happened
relunched Finder
Worked

brew cask install qlstephen
created a test README
test pressing Space
nothing happened
relunched Finder
error about permission show up
authorized in Settings/Security
test pressing Space
nothing happened
relunched Finder
nothing happened
restarted the VM
error about permission show up / clicked open
test pressing Space
this error below show up

`

like...in my real computer, the only thing that it's working is:
qlmarkdown
suspicious-package
provisionql
QuickLookAddict

So....what are we missing?

Answer 52 · 2019-10-25T16:10:52.000Z

Hi there,

The box "qlstephen cannot be opened because its from an unidentified developer" with button "OPEN ANYWAY" wasn't appearing in my Security and privacy.

I managed to make it work in my machine doing this:

brew cask reinstall qlstephen
Relaunch Finder
sudo spctl --master-disable # disable gatekeeper
ensure that it works by doing a quicklook on a random file
sudo spctl --master-enable # plug gatekeeper back
then opening the "Security and Privacy" did contain the "OPEN ANYWAY" button on the bottom

Cheers,

Answer 53 · 2019-10-25T20:05:49.000Z

@jorge-d Doesn't work.

Answer 54 · 2019-10-25T21:21:24.000Z

I've been following and attempting most of the suggested solutions without any success... until just now. I did the following:

open ~/Library/QuickLook/ and removed QLMarkdown.qlgenerator, which I was about to reinstall. It probably makes sense to delete any non-working .qlgenerator.
ran qlmanage -r
relaunched finder
reinstalled quicklook plugin(s)
ran qlmanage -r + relaunched finder
invoked quicklook on a few files.
NOTE: it didn't immediately seem to work so I repeated the previous step 1-2 times. After relaunching finder for the 2-3rd time and invoking quicklook it decided to work.

Removing and reinstalling quicklook plugins seemed to make the difference. That and attempting to reload quicklook + relaunch finder multiple times. Sorry for the non-specific potential fix but hope it helps someone. It's been driving me crazy.

Answer 55 · 2019-10-26T17:42:50.000Z

no lock from me again.

Answer 56 · 2019-11-03T19:16:47.000Z

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

For me this was not enough. I had to open the binary like this and also open the bundle. Right-click QLStephen.qlgenerator and open with BBEdit, accept the warning. Now it works.

Answer 57 · 2019-11-04T05:15:48.000Z

In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) ~/Library/Quicklook/QLStephen.qlgenerator/Contents/MacOS/ and right-click QLStephen, selecting Open. This will give you the option to open it anyway, and it should load correctly in the future.

For me this was not enough. I had to open the binary like this and also open the bundle. Right-click QLStephen.qlgenerator and open with BBEdit, accept the warning. Now it works.

I did that and still doens't work for me.

Answer 58 · 2019-11-11T08:27:33.000Z

simple way to fix this warning is to run xattr -d com.apple.quarantine ~/Library/QuickLook/QLStephen.qlgenerator

Answer 59 · 2019-11-11T08:50:39.000Z

simple way to fix this warning is to run xattr -d com.apple.quarantine ~/Library/QuickLook/QLStephen.qlgenerator

no success here.

Answer 60 · 2019-11-27T01:16:51.000Z

I've been following and attempting most of the suggested solutions without any success... until just now. I did the following:

open ~/Library/QuickLook/ and removed QLMarkdown.qlgenerator, which I was about to reinstall. It probably makes sense to delete any non-working .qlgenerator.

ran qlmanage -r

relaunched finder

reinstalled quicklook plugin(s)

ran qlmanage -r + relaunched finder

invoked quicklook on a few files.
NOTE: it didn't immediately seem to work so I repeated the previous step 1-2 times. After relaunching finder for the 2-3rd time and invoking quicklook it decided to work.

Removing and reinstalling quicklook plugins seemed to make the difference. That and attempting to reload quicklook + relaunch finder multiple times. Sorry for the non-specific potential fix but hope it helps someone. It's been driving me crazy.

Hi there,

The box "qlstephen cannot be opened because its from an unidentified developer" with button "OPEN ANYWAY" wasn't appearing in my Security and privacy.

I managed to make it work in my machine doing this:

brew cask reinstall qlstephen

Relaunch Finder

sudo spctl --master-disable # disable gatekeeper

ensure that it works by doing a quicklook on a random file

sudo spctl --master-enable # plug gatekeeper back

then opening the "Security and Privacy" did contain the "OPEN ANYWAY" button on the bottom

Cheers,

After tried those two suggestions, qlstephen seems to works fine. Thank.

Answer 61 · 2019-11-27T20:14:44.000Z

I have a feeling two problems are conflated here:

QLStephen not working at all
QLStephen not working for certain file types.

I just did some tinkering and realized that QLStephen will work on non-suffixed files following this suggestion: #81 (comment)
However, QLStephen won’t work for files with arbitrary extensions – .fea in my case.

I tried re-assigning the default opening application – no luck just yet.
I’d be curious to find out how to permanently force QuickLook to use a specific generator for a given file type.

Answer 62 · 2019-11-28T01:36:20.000Z

I have been doing some debugging. @frankrolf you are right.

The way QuickLook selects a plugin to generate a preview is by matching the LSItemContentTypes properties in the Info.plist of QLStephen with the kMDItemContentType property of a file, which you can obtain by doing mdls -name kMDItemContentType myFile.

For example, if a file has a value of public.data for the kMDItemContentType property, QLStephen will be used to preview it (because public.data is under the LSItemContentTypes property of the Info.plist).

I noticed that yml files have the property kMDItemContentType set to public.yaml, and thus they are not opened with QLStephen. Also, some files have a dynamic value for kMDItemContentType, as you can read here, and they are not opened with QLStephen.

A solution that works for me is to add some extra values to the Info.plist of QLStephen:

<key>LSItemContentTypes</key>
<array>
	<string>public.data</string>
	<string>public.yaml</string>
	<string>com.apple.xcode.strings-text</string>
	<string>dyn.ah62d4rv4ge81e3pxr70hq3pe</string>
</array>

Find the plugin attached here with those changes:
QLStephen.qlgenerator.zip

Remember that every time that a plugin is changed, Finder has to be restarted.

Also, find here a script to read the kMDItemContentType property of multiple files:

for f in *; do
  type=$(mdls -name kMDItemContentType $f)
  echo "$f -> $type"
done

Answer 63 · 2019-12-03T20:17:08.000Z

@samcat116

Notarization does not require the $99/yr subscription. Just needs an Developer Apple ID and Xcode .

You are kidding right? You only get a valid developer id, when you pay $99 for the Apple Developer program.

I have a valid developer id and I didn't have to pay the $99.

Answer 64 · 2019-12-10T11:19:29.000Z

(just posted my solution in another issue anthonygelibert/QLColorCode#51 (comment))

Removing the quarantine attribute from all files is another solution, to get Quicklook working. No need to change any code.

List attributes
xattr -r ~/Library/QuickLook/QLColorCode.qlgenerator

Delete attribute com.apple.quarantine
xattr -d -r com.apple.quarantine ~/Library/QuickLook/QLColorCode.qlgenerator

Answer 65 · 2019-12-10T12:33:20.000Z

(just posted my solution in another issue anthonygelibert/QLColorCode#51 (comment))

Removing the quarantine attribute from all files is another solution, to get Quicklook working. No need to change any code.

List attributes
xattr -r ~/Library/QuickLook/QLColorCode.qlgenerator

Delete attribute com.apple.quarantine
xattr -d -r com.apple.quarantine ~/Library/QuickLook/QLColorCode.qlgenerator

It doesn't work for me. :(

Answer 66 · 2019-12-16T13:37:10.000Z

Hi there,

The box "qlstephen cannot be opened because its from an unidentified developer" with button "OPEN ANYWAY" wasn't appearing in my Security and privacy.

I managed to make it work in my machine doing this:
* `brew cask reinstall qlstephen`

* Relaunch Finder

* `sudo spctl --master-disable` # disable gatekeeper

* ensure that it works by doing a quicklook on a random file

* `sudo spctl --master-enable` # plug gatekeeper back

* then opening the "Security and Privacy" did contain the "OPEN ANYWAY" button on the bottom
Cheers,

Similar to this I did the following to get mine to show the elusive button:
brew cask remove qlstephen && brew cask install qlstephen
Open finder so that the cannot be opened because the developer cannot be verified error
Opened up System Preferences > Security and Privacy > General tab
Then there was a button at the bottom right of that box, next to text of the app which was blocked
(qlstephen). Clicked allow and it now works fine.

This issue is affecting many applications (including big ones like Terraform).

Answer 67 · 2019-12-28T19:20:17.000Z

simple way to fix this warning is to run xattr -d com.apple.quarantine ~/Library/QuickLook/QLStephen.qlgenerator

Works for me! DOn't forget killall Finder in the end!

Answer 68 · 2019-12-29T01:51:34.000Z

simple way to fix this warning is to run xattr -d com.apple.quarantine ~/Library/QuickLook/QLStephen.qlgenerator

Works for me! DOn't forget killall Finder in the end!

I tried and it works on Catalina 10.15.1

Answer 69 · 2019-12-29T21:47:19.000Z

not on 10.15.2 :-(

Answer 70 · 2019-12-30T02:45:03.000Z

@leirissa
is gatekeeper disabled?
sudo spctl --master-disable

Answer 71 · 2020-01-03T23:06:10.000Z

I installed QLStephen.qlgenerator via brew in 10.15.2
Gatekeeper is disabled
I clicked a README file (public.data) and pressed space
I cannot view the file in QL

What am I doing wrong?

Answer 72 · 2020-01-03T23:16:17.000Z

indeed I am stucked as well,,,,e.g bla.conf files are showing the default app icons ( e.g sublime) but no preview...changing to xml and , bang ,,,ok

Answer 73 · 2020-01-04T08:09:29.000Z

not on 10.15.2 :-(

@leirissa
I updated macOS to 10.15.2 and it works.
(i downloaded QLStephen.qlgenerator.1.4.4.zip with safari and installed manually.)

Answer 74 · 2020-01-06T16:14:01.000Z

I did:
brew cask reinstall qlstephen
and re-launched the Finder. No-go!
spctl --status
assessments disabled

Answer 75 · 2020-01-06T18:00:13.000Z

compiled quickview that won't load: https://drive.google.com/open?id=1eo6q4JNmLxl_5EdAj3sRU0jtNzRgNj0U

Answer 76 · 2020-01-06T18:10:55.000Z

compiled quickview that won't load: https://drive.google.com/open?id=1eo6q4JNmLxl_5EdAj3sRU0jtNzRgNj0U

@ballo sorry I meant the text file without extension. it shows the files without the extension I created myself. maybe there is something different in your file.

for example;
touch testfile
echo "hello world" >> testfile

Answer 77 · 2020-01-06T18:13:50.000Z

mdls -name kMDItemContentType README
kMDItemContentType = "public.data"

Answer 78 · 2020-01-06T18:15:34.000Z

mdls -name kMDItemContentType testfile
kMDItemContentType = "public.data"

Answer 79 · 2020-01-06T18:15:58.000Z

oke, so how to open a file with .conf ( mapped with sublime and only shows the icon)

Answer 80 · 2020-01-06T18:18:17.000Z

mdls -name kMDItemContentType blah.conf
kMDItemContentType = "dyn.ah62d4rv4ge80g55sq2"

Answer 81 · 2020-01-06T18:24:47.000Z

qlstephen is for files without extension?

Answer 82 · 2020-01-06T18:28:29.000Z

@hazarek Look up "kMDItemContentType"

Answer 83 · 2020-01-06T18:31:17.000Z

@hazarek Look up "kMDItemContentType"

so?

Answer 84 · 2020-01-06T18:31:34.000Z

It isn't the "extension"

Answer 85 · 2020-01-06T18:36:52.000Z

it does not show files with the conf extension because The plugin does not support.

Answer 86 · 2020-01-06T18:49:15.000Z

Is there a different app that uses quick look plugins which logs their loading, or is it all done by the system and thus a black box

Answer 87 · 2020-01-06T18:59:17.000Z

strange, before catalina this works!

Answer 88 · 2020-01-06T19:01:58.000Z

I'm regretting Catalina very day. The 32bit absence has killed a lot of functionality like 32bit mplayer (old codecs) and WINE.

Keep it up Apple; Windows is looking better every 'upgrade'

Answer 89 · 2020-01-06T19:17:26.000Z

@ballo https://iina.io/.
why do you use old fashioned mplayer.

Answer 90 · 2020-01-06T19:19:34.000Z

@hazarek I use it when old win32 codecs are necessary. There's a compatibility layer.

I guess I should say used since Catalina makes it impossible now. I'll have to use Linux in a virtual machine, or figure out a downgrade method (which may be tricky since I never used Mojave)

Answer 91 · 2020-01-10T08:38:34.000Z

Solution

Make sure you follow each step correctly. Please don't leave more unnecessary comments so that new users will see this one.

Install the plugin (brew cask install qlstephen)
Select a file without an extension. macOS will show a warning like this one.
- DO NOT CLICK "Move to Trash"
- Click "Cancel"
Open System Preferences
Visit Security & Privacy
Ensure you're in the General tab. You should see a notice regarding this plugin at the bottom:
- Click "Allow Anyway"
Select another file without extension OR run:
qlmanage -p /path/to/file/without/extension
You should see a warning similar to the first one, but with a new button
- Click "Open" 🎉
Enjoy QuickLooking extension less files on Catalina

Answer 92 · 2020-01-10T18:57:34.000Z

'Select a file without an extension. macOS will show a warning like this one.
DO NOT CLICK "Move to Trash"'

nope

Answer 93 · 2020-01-11T02:41:14.000Z

Yeah, maybe on your machine but not mine.

Answer 94 · 2020-01-11T11:26:17.000Z

I had no issue with @fregante instructions - worked perfectly

Answer 95 · 2020-01-14T12:20:29.000Z

xattr -cr ~/Library/QuickLook/QLStephen.qlgenerator
This worked as for all other apps with same issue

Answer 96 · 2020-01-14T21:41:28.000Z

@varyform Can you confirm whether or not you saw the "cannot be opened" error and if your solution is for people who have seen the error?

I have yet to see that error.

Answer 97 · 2020-01-15T08:09:54.000Z

@ballo I wasn't able to see the error either, but @varyform 's command worked for me.

Answer 98 · 2020-01-15T08:48:26.000Z

Doesn't help here.

I also tried moving all contents from ~/Library/QuickLook/ into ~/Library/QuickLook.old/ and reinstalling QLStephen.qlgenerator from brew. It reinstalled but same non-function and non-error.

Answer 99 · 2020-01-15T17:09:46.000Z

@fregante Instructions worked for me.