mikedvzo

Thanks for your patience on this issue, the 5.1 b2129 pre-release now has the authorised provisioning from Apple to show you notes again.

@mikedvzo It's tricky to parse what you've done based on these messages so could you please set your Alfred preferences to be stored in a your home directory, in a locally stored folder (not Documents or Desktop, which most users sync via iCloud) and leave it as unsynced.
 
From my understanding of your replies, you are immediately re-setting a synced remote location. The objective here is to establish whether you see normal behaviour when the preferences remain unsynced.
 
Please keep it that way for at least a few days, and see what behaviour you get. This will help focus the issue on whether your issue is specifically caused by syncing or not.

First open you Run Script. Edit it:
Change Language to /bin/zsh. Replace all code with /usr/bin/swift ./mediakeys "${1}"
Now open the Workflow’s contents in the Finder and create a new mediakeys file. Inside, put this code:
 
// Based on the code on https://stackoverflow.com/questions/11045814/emulate-media-key-press-on-mac import Quartz let NX_KEYTYPE_SOUND_UP: UInt32 = 0 let NX_KEYTYPE_SOUND_DOWN: UInt32 = 1 let NX_KEYTYPE_PLAY: UInt32 = 16 let NX_KEYTYPE_NEXT: UInt32 = 17 let NX_KEYTYPE_PREVIOUS: UInt32 = 18 let NX_KEYTYPE_FAST: UInt32 = 19 let NX_KEYTYPE_REWIND: UInt32 = 20 let supportedKeys: [String: UInt32] = ["playpause": NX_KEYTYPE_PLAY, "next": NX_KEYTYPE_NEXT, "prev": NX_KEYTYPE_PREVIOUS, "volup": NX_KEYTYPE_SOUND_UP, "voldown": NX_KEYTYPE_SOUND_DOWN] func HIDPostAuxKey(key: UInt32) { func keyDown(_ down: Bool) { let flags = NSEvent.ModifierFlags(rawValue: (down ? 0xa00 : 0xb00)) let data1 = Int((key << 16) | (down ? 0xa00 : 0xb00)) let ev = NSEvent.otherEvent(with: NSEvent.EventType.systemDefined, location: NSPoint(x:0,y:0), modifierFlags: flags, timestamp: 0, windowNumber: 0, context: nil, subtype: 8, data1: data1, data2: -1) let cev = ev?.cgEvent cev?.post(tap: CGEventTapLocation.cghidEventTap) } keyDown(true) keyDown(false) } HIDPostAuxKey(key: supportedKeys[CommandLine.arguments[1]]!)  
The code could get some cleanup, but it will work like your previous one.

All this rhetoric is totally unnecessary as there are no problems in the App and it works beautifully.  However, all of this can be dispelled with a simple answer of whether we can expect an update in 6 months, 1 year, 2 years etc..... Just a rough guideline since there has been no feedback on this for a very long time - over a year now.  
 
As I have stated in the past, I would like to see a new updated version for the iPhone with the latest iOS features but understand that Andrew has to allocate his time appropriately.  I personally am willing to pay for such an update.  

The simple answer to this is Alfred Remote *will* get a major update, but I can't give you a timescale.
 
To keep Alfred's quality as high as possible, we are extremely selective over which features bring the most value to our wider user base. Alfred Remote constitutes a minor part of this user base, so while we have continued to add features to Remove via updates in Alfred itself, the core Alfred Remote app has remained as is.
 
While it would be nice to do a minor update to Remote to include some of the newer iOS features, Apple has evolved iOS significantly since Remote was originally released, with some technologies deprecated, and some new ones introduced, so Remote would need an overhaul to fit with within Apple's framework and "vision", all while trying to keep Remote backwards compatible with Alfred 3.
 
Over the past number of years, I've been keeping a close eye on Swift and Swift UI, and this may provide a perfect platform for a complete Alfred Remote rewrite, but it could be too early to allow this to work on a wider number of older devices.
 
As I said before, when Alfred Remote version 2 comes out, I'd like to keep it as a free update for all current Alfred Remote users.

Problem Solved.  I was prompted to allow Alfred 4 access to Reminders and now everything works as expected.  
 
Thank you so much Andrew for the quick turn around.
 
Is there a way to donate to Alfred Mega Supporter License after the fact? I would like to do so. I can not imagine life without Alfred  

I know this is not specific to Alfred but does anyone know if there is a way to associate the tel:{query} Phone field under Contacts Features with Google Hangouts.  When I used to work for Cisco I had this tied to Cisco Jabber so I could dial from Alfred Contact search with Jabber.  I want too do the same with Google Hangouts which I run in Chrome to Dial a phone Number.  I have  Jabra USB headset connection to my Laptop and the only missing piece is the convenient Dialer from Alfred.  I have my Contacts uploaded to Google so I can Dial with Hangouts form Chrome by name but Alfred is far more convenient.  
 
I am thinking if there is way to make Google Hangouts the Default for Calls  in FaceTime.  However,  since Hangouts is not a resister Dialer applications not sure how to accomplish or if there is a possible workaround.  

I find it useful once in a while since I use more than one browser to be able to have a Web Search that allows you to set which browser will be used instead of the default browser.  I primarily add custom searches as an easy method to access a URLs that I use frequently.  I use this instead of bookmarks because I find it more convenient for my most visited sites but sometimes need to use my non default browser.  

I have noticed a similar behavior since upgrading to 10.12.4.  I have noticed that the Alfred process is showing High CPU regularly now with 10.12.4.  When I look further I notice there is an issue where I constantly have to force quit the Python process on my Mac since the CPU is at 98% on the Python process.  When I inspect the process it is always related to a simple Alfred Workflow that has called the Python process.  I will continue to monitor it but it has happened 4 times in the last couple days and always the same situation.  
 

Same problem here only no movies work at all.  Using it for years so suspect something has changed on IMDB that has broken the Workflow.  
 
Here is the debug output showing that there is nothing returned:  
 
[2017-02-04 11:44:35][STDERR: input.scriptfilter] 11:44:35 workflow.py:1972 DEBUG    Workflow version : 2.3.0
11:44:35 media.py:39 DEBUG    TMDb info retrieved.
11:44:35 workflow.py:1387 DEBUG    Reading settings from `/Users/xxxxx/Library/Application Support/Alfred 3/Workflow Data/com.mcknight.movies/settings.json` ...
11:44:35 workflow.py:2163 DEBUG    Set last run version : 2.3.0
11:44:35 workflow.py:2008 DEBUG    Workflow finished in 0.114 seconds.
[2017-02-04 11:44:35][input.scriptfilter] <?xml version="1.0" encoding="utf-8"?>
<items><item valid="no"><title>The item was not found.</title><subtitle /></item></items>

When searching workflows the search should be fuzzy and not just match the first character.  Especially important since everything has been turned into a workflow.

When searching workflows the search should be fuzzy and not just match the first character.  Especially important since everything has been turned into a workflow.

Thanks man that change worked.  Looks like Alfred did not like the function call and I am not about to figure out why.  :-)