Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Chris <ithinkiam@gmail.com>
Newsgroups: misc.phone.mobile.iphone,comp.mobile.ipad
Subject: Re: Custom shortcut not working after ipadOS 18 update
Date: Thu, 27 Feb 2025 08:04:01 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <vpp69h$31ej4$1@dont-email.me>
References: <vikrp7$3fo7e$1@dont-email.me>
 <lr8s89F3p76U2@mid.individual.net>
 <ving6r$7naa$1@dont-email.me>
 <lr9gnpF71viU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 27 Feb 2025 09:04:02 +0100 (CET)
Injection-Info: dont-email.me; posting-host="45e19d855d6673a96d4730a61613ef36";
	logging-data="3193444"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19sfARZ2gFOSdh0ra34H+7kEgrQ4eh4sI0="
User-Agent: NewsTap/5.5 (iPhone/iPod Touch)
Cancel-Lock: sha1:wx3V+OOEFLfpuCrdnzQLvxnY/5w=
	sha1:0gVM8AR2F+prH1Qe61cRYzQVYag=
Bytes: 2188

Jolly Roger <jollyroger@pobox.com> wrote:
> On 2024-12-03, Chris <ithinkiam@gmail.com> wrote:
>> Jolly Roger <jollyroger@pobox.com> wrote:
>>> On 2024-12-02, Chris <ithinkiam@gmail.com> wrote:
>>>> 
>>>> Final attempt at a sensible discussion on here...
>>>> 
>>>> Over the weekend I updated my ipad (9th gen) to ipadOS 18 from 17 and
>>>> I now notice a custom shortcut isn't working properly anymore.
>>>> Basically, it creates a new note with today's date as a title and
>>>> throws up two dialogue boxes for a note description and a set of tags.
>>>> Everything behaves as before except the tags are ignored. 
>>>> 
>>>> I have very little experience of Shortcuts and this is pretty much my
>>>> first one. Any ideas on how to debug?
>>> 
>>> A link to the shortcut we can examine would be a good start.
>> 
>> How do I do that?
> 
> Using one of these methods: 
> 
> <https://support.apple.com/guide/shortcuts/share-shortcuts-apdf01f8c054/

Update: this is now working again. Must have been a bug that was fixed in a
recent update.