Sequoia 15.01 release as well as 15.1 beta 6 Automator problems

[Henties]

@all Dating many macOS versions ago I created some bash scripts and converted them to applets with Apple's Automator.

These scripts have been working reliably all along until I started investigating Sequoia's possible introduction into my network

and workflow, just to discover that none of my Automator based Applets are now functioning properly.

When however I run the original "raw" bash scripts manually from the command line, without Automator at all, these scripts

are working the way they should.

 

The same scripts still run perfectly in the latest Sonoma release environment, even as Automator Applets.

 

Looks like Apple introduced some Automator problems, perhaps some security patches that require a different approach or

whatever, when generating these scripts.

 

I can actually generate an Automator Applet under Sequoia and run it successfully in Sonoma although it will not run under Sequoia,

the environment it was actually generated in.

 

For me Sequoia is consequently not at all viable to be used as a daily platform to do one's business with.

 

Has anybody else perhaps experienced similar problems as described above ? Would like to hear from you and if possible also present

a solution to solve this phenomenon. It may well be that I overlooked something essential that causes this kind of behavior however the

scant Sequoia release notes that Apple published for Senuoia thus far have as yet not revealed anything tangible.

 

Any feedback will be greatly appreciated.

 

Greetings Henties   

 

 

   

[chris1111]

Hi @Henties 

 

I was curious to see if it worked
Well no you are not the only one

 

[Henties]

@chris1111thanks for your feedback, we will therefore have to wait and see what the future holds in store for us on this particular

issue. Personally I believe this should not have slipped through Apples QA at all, just my 2 cents.

 

Greetings Henties

[meg2014]

I hope this is not off topic for your thread.

 

I have an Adlink 2tb NVME drive that Sequoia (B5 and B6) will not recognize nor work with.  I thought, at first, that the drive was done for.   However, on Windows 10, Windows 11 and Linux Mint, the drive works fine.  No issues. I tried several different cases and no change.  Just won't work on Macs running Sequoia.

 

There are discussions on Macrumors, and even on Apple's forum that many others have noted a problem with PCIE M.2 drives not mounting properly https://discussions.apple.com/thread/255339675?sortBy=rank

 

Unless this get fixed soon, Sequoia will sit unused until Apple gets around to fixing this problem.

Edited October 9, 2024 by meg2014

[Henties]

@meg2014 I don't think this a drastic flaw at this particular juncture in Sequoia's development cycle, never forget that Sequoia is still in a relatively infant state in it's development phase with problems of this nature unfortunately surfacing from time to time.

In the long run we will end up with a stable Sequoia that everybody will believe is the best.

 

Just my 2 cents.

 

Greetings Henties

 

 

 

 

 

Edited October 9, 2024 by Henties
Spelling error

[Henties]

@allWhat is disturbing is that whatever I try to change is not nearly consistent with what I try to accomplish.

I am now wandering whether one can actually rely on these "hogwash" settings at all.

 

[Henties]

@allAfter upgrading to Sequoia 15.1 Version 24B82 my Automator generated applets are still not functioning,

basically this means that Sequoia is useless for deployment in my environment, at least until Apple has fixed this problem or alternatively documents a properly functioning workaround.

Fortunately all my Applets are still functioning correctly under control by Sonoma.

Greetings Henties 

[chris1111]

Testing create Automator App from macOS Sequoia 15.0.1 (24A348)

No such issue here Create an App HP-EliteBook-840-G3.app

 

Create a simple Toggle Dark/Light App also work

 

 

Edited October 25, 2024 by chris1111