-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS X 10.15 Catalina support? #81
Comments
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.) |
In the mean time, to get around this, you can go to the folder (⌘⇧G from Finder) |
This doesn't work for me. |
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. |
EDIT: @samcat116 cleared this up in the subsequent comment. |
Notarization does not require the $99/yr subscription. Just needs an Developer Apple ID and Xcode . |
I tried
On a related note, I see this message when I try the same thing for a json file with a json reading plugin. |
Same here, just updated to Catalina yesterday and QLStephen stopped working. |
+1 |
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. |
If it helps, here are the docs on Notarizing Your App Before Distribution. |
@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. |
Can you try with the CLI? It might look more complex, but could you give it a shot and try it out. |
@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. |
@partheseas Check this out - https://forums.developer.apple.com/thread/119445 |
watching…… |
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. |
Note that Is the move forward to publish a version that is notarized? Or is it a different issue? |
So I tried notarizing one of the plugins with my paid developer account, and it doesn't seem to accept I ran the
There seems to be no documentation online on notarizing QuickLook plugins either. |
Check this out -> anthonygelibert/QLColorCode#51 (comment) |
I hope description on this site might be useful. |
Thanks @KoCMoHaBTa @ahmetgeymen, I'll try this again in the coming weekend. |
it works for me at macOS 10.15. |
QL插件都在~/Library/QuickLook/目录,但从系统设置->拓展->快速查看,却没有允许使用此目录,但其中包含了/System/Library/Frameworks/RealityKit.framework内的几个插件。 |
You are kidding right? You only get a valid developer id, when you pay $99 for the Apple Developer program. |
not for me. What else did you do? |
|
@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. |
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. |
@fregante Instructions worked for me. |
Came here to say the same. You can even run |
I ran this with wildcard and my Markdown and Syntax highlighter plugins all work now! |
This did not work for me but using sudo did
|
might depend on how your bash permissions are set up? |
1.5.1 should works on macOS 10.6 (Snow Leopard) - 10.15 (Catalina) |
I uninstalled via brew, then installed the latest version:
Then I got this: I also noticed this in Preferences: Even after clicking Allow Anyway, the extension is not working for me. I'm on macOS 10.15.2. |
Did you try to reboot your machine? QL cache is very error prone. |
|
Without paying $99/yr for an Apple dev account I cannot fix this. I found in testing that even reloading the plugin with Could you try this:
Check if it works. |
I would like to thank everyone for investigating/posting various solutions! Thanks! |
Again, the QL caching is very error prone. Restarting Finder might help in most cases but not in all. My full procedure would be:
@frankrolf Do you have other plugins that may override specific file types? I'm not sure what the precedence is when multiple plugins claim the same extension. Also the readme states:
|
Thanks @relikd for the steps #81 (comment)
I added the steps from @relikd to the |
The steps as outlined in the Readme, which do not mentioning rebooting the entire computer as a requirement, do NOT solve the problem for me. Basically so far I tried all those steps, in that order, and I still don't see anything when trying to view a LICENSE file. The only thing I haven't tried yet is a system reboot. I'll report back when I do. |
Like others this is working for me except for files with an extension. I can QL |
FWIW I've tried everything in this thread including removing all qlgenerator bundles except QLStephen.qlgenerator to no avail. What is the actual process that loads the qlgenerator? Is there a background daemon that needs to be running? mp4s still work, so I can only assume /Library/QuickLook/Video.qlgenerator is being loaded. Maybe I should put my bundles there. |
Check out issue #87 for discussion on file extensions and types and why some files work and some do not.
There is a process called |
Sadly, debugging QL issues got much harder on Catalina. Previously you could run Which means:
Again, sadly the results aren't useful in many cases. Stupid privacy rules hide important information, e.g., there are a couple of entries simply showing:
I don't know how this can be useful at all. You don't even know what plugins were loaded. Still it is helpful in some cases where the QL plugin would crash! |
@relikd I mentioned you in the comment, but for anyone else finding this thread, please head over to issue #87, this is not specifically a Catalina issue anymore, it has to do with dynamic UTI values. More info can be found in this comment |
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.
The text was updated successfully, but these errors were encountered: