vitor

Please add further information on the GitHub issue, so we don’t split the discussion. But remember that as per the moderator’s note:

On 2/27/2024 at 1:03 AM, iandol said:

This is complex and requires advanced configuration, not something we can officially provide support for. This thread was split from the main one so members of the community can help each other setting up their own specific models.

So if you find the cause and can submit a PR (something janky is fine, as long as it works and I can evaluate) I’ll can look further into it. Otherwise, as stated previously, it would be untenable to support every quirk from every model. Either they support the API correctly or not, and the workflow works with the ones who do.

I’ve already replied on GitHub, try that version.

Unfortunately I’m out of ideas so far, we’ve covered everything I could think of that might affect this. You’re the only report of this, so it seems that something on your machine is blocking the action. If I get more reports, maybe I’ll get more clues to be able to investigate further.

We may have found the problem. Turn on each of the disabled ones in turn and do steps 5 and 6. One of the disabled ones is likely to be the missing piece.

When you ran step 4, did you get a notification about a background process?

If you go into System Preferences → General → Login Items, do you see an osascript item, and is it on?

What are the contents of ~/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password/Data?

Did you try after the reboot?

No, you did things right, I just need more information to start ruling things out. Do this next:

1. Disable “Detect Changes” in the Workflow’s Configuration.
2. Run :1pextras → Force Update Items.
3. Enable “Detect Changes” in the Workflow’s Configuration.
4. Run :1pextras → Force Update Items again.
5. Change the title or username on an item in 1Password.
6. Check if it worked. Really search for `Update` to make sure it’s not further down the list.

If it still did not work, restart your Mac and do steps 5 and 6 again. Sonoma 14.4 broke a bunch of stuff, one of them related to this.

@mrzumo I’ll consider that for the next version. I’ve also moved your post to the correct thread.

When reporting issues, please include your exact installed versions of:

• The Workflow.
• Alfred.
• macOS.
  

In addition to:

• The debugger output. Perform the failing action, click “Copy” on the top right and paste it here.
• Details on what you did, what happened, and what you expected to happen. A short video of the steps with the debugger open may help to find the problem faster.
  

29 minutes ago, Send Me said:

2) if I toggle the "Only show login items" option it will not change the behavior of the results, i.e. it will still list non-login items in results.

That only happens after results are updated, and whatever options sticks until the next update.

30 minutes ago, Send Me said:

PS: Alfred Debug shows no error messages.

Even so, I need to see it to understand what is and is not happening. Open the debugger, then make a change to an item in 1Password and save. What does the debugger say?

Welcome @Zhibin He,

If you go into the Workflow Environment Variables and add a new https_proxy key, it should work.

The Perplexity AI docs say their API is the same as OpenAI, so that would already be possible by changing the API endpoint.

I’ve moved your post to the relevant thread which explains how.

You can copy the current chat to the clipboard with a shortcut, then use another workflow with a keyword to save the chat in the format and name you want to the folder you want.

Updated to 2024.2.

macOS 14.4 stable broke searching of manual pages with man (FB13690576), so they are now retrieved by location. This alters the results list slightly, as retrieving descriptions one by one takes too long. But by showing the path in the subtitle, it’s now possible to differentiate between different manuals with the same name (e.g. for a tool which ships with the system but you have installed a more recent version with Homebrew).

Updated to 2024.2.

• Support input and output in feet and inches (e.g. 7ft 4in).
• Support optional inches when given number after feet.
• Support ' and '' for feet and inches.
• Support “foot” for “feet”.
• Add option to output fractional feet.
• Add option for thousands separator.
• Add option for scientific notation.
• Add standardAtmosphere unit.
• Add milli, micro, nano, pico seconds.
• Allow lowercase L for liters symbols.
• Allow numbers starting with period.
• Allow negative numbers.
• Use Number Slider for fractions.
• Skip Script Filter as Universal Action.
  

Updated to 2024.1.

Use Number Slider.

There’s no proper method to tell macOS to shutdown while respecting that setting. But you can use Shutdown Timer (it also works without a timer) to do it, as it has a setting to close all apps before proceeding to shutdown.

More information is required to diagnose the issue. Please see the short post How to Report a Problem with a Workflow for details on what to provide.

1 hour ago, zzz said:

Usually, the selected text is used for query

I think you might be misunderstanding Universal Actions. You shouldn’t use them to fill text in Alfred and then add a command, but to run the command directly. From your other issue, you seem to be loading Universal Actions into existing Keywords but they’re most powerful when used directly from the object.

You’re conflating the List Filter Input and the Script Filter Input.

What you need is to add a Universal Action object before the List Filter.

1 hour ago, jesused said:

P.S: Developers, tell Apple that sometimes the S.O forgets some apps in Accessibility

It has been reported. Ostensibly, reporting an issue multiple times helps developers at Apple make a case for prioritising it. You can open a report to Apple by using the Feedback Assistant app on your Mac.

That option is not available and is out of scope. The workflow uses yt-dlp, which is the tool outputting that message, you can run it in the terminal to add the necessary details. Instructions on how to do that are in the linked website.

As stated, the most likely cause is that the API is down for the moment.

Changes made to the shortcut are not supported, only the unmodified workflow. If you want to make a report on the upload action of the shortcut not working for you, you can use the Feedback Assistant app on your Mac to contact Apple, I have no control over their implementation.

There hasn’t been any recent change, and it wouldn’t have happened without you noticing. The most likely cause is that the imgur API is down. Imgur is an external service and the upload is entirely handled by the shortcut, which is handled by Apple.