solak

There have been a few discussion items on this forum regarding problems encountered when using multiple Macintosh Alfred Servers from an iOS Alfred Remote. I encountered problems in the reverse situation of using multiple iOS Alfred Remotes to control the same Macintosh Alfred Server(s). The essence of the situation is that I tried using Alfred Remote on both my old and new iPhone. Each time I used a different iPhone, I had to delete the connection and re-connect the Remote to the Server. From reading those other forum posts here, I speculated that my new iPhone (initialized by cloning my old iPhone) had the same internal ID. My attempted solution of deleting Alfred Remote from one iPhone and re-installing it has solved the problem. Now both Alfred Remote apps can retain their connection settings to the Alfred Server(s). I hope this info can help someone else avoid a frustrating failure.

It may have seemed that I posted the same bug twice yesterday, but actually I was distinguishing "file missing" (which may be trivial to repair or explain) in the other report from "error text wording" (which may require consideration, coding, review, and updating the software kit) in this one.

Thanks for the alternate link. Thanks for the networking information. I am investigating my configuration and that further here. Unfortunately, the reproducer I described above now fails to fail, so I have to blame my ISP or other temporary network outage.

What you were doing when the issue happened In Alfred Preferences, clicked on [Download update] Whether you were able to replicate it a second time by performing the same action (Update any third-party apps and restart your Mac if relevant) Yes, as well as on another computer. Include any screenshots that might help us Include the Alfred version & build number you are using Currently running Alfred 5.0.6 Include your macOS version MacOSX 12.6.5 Include the version number of any third-party apps relevant to your issue The failure message says "Unable to download update data, please check internet connection". Actually, the internet is fine but the file https://cachefly.alfredapp.com/Alfred_5.1_2134.dmg is missing on the server. Not sure how much work this is worth, but perhaps just checking another URL to distinguish between "no internet" and "no file" would be simple. Thanks for making a product so useful and reliable that I always click on the update button.

Already, I have an update and correction. Since I was thinking about apps permissions, I wound down from this bug report by reviewing System Preferences, Security & Privacy, Privacy. There I found that Terminal.app did not yet actually have the Full Disk Access that I thought I had granted because it had not yet quit and restarted. So, the above description is not a hard bug, but a strong suggestion, because "sudo mdutil -X volume-path" works without needing a restart of Terminal.app to grant it a new permission.

Using Alfred 4.6.5 [1299] on macOS Monterey Version 12.4. Using Alfred to launch apps started to miss some applications that it had previously found. Eventually I went to Alfred Preferences, Advanced, Rebuild macOS Metadata and included Delete .Spotlight-V100 before reindex. A new Terminal window popped open and also another window asking whether I would grant Terminal.app access to the whole disk. I clicked yes. The run of /Applications/Alfred 4.app/Contents/Frameworks/Alfred Framework.framework/Versions/A/Resources/reindexdel.sh proceeded, but it complained that it could not delete .Spotlight-V100. I had given my password to sudo, but that failed because I have set my account as a non-admin for safety. I opened another Terminal window to login to my other account which does have admin privs and copied the command line there. This time sudo succeeded, but the deletion of .Spotlight-V100 still failed. I tried to sudo chmod 777 .Spotlight-V100 to give myself permission to delete it, but even the chmod failed. Further research seems to indicate that one should delete that directory using sudo mdutil -X volume-path but I do not know precisely which macOS version was the first to require this. ________ This relates to a previous post but I'm starting a new topic because it seems that remedy is no longer sufficient.