I’ve been using the app Book Tracker (which I love, and has a lot of Shortcuts support) to keep track of books I’ve read/am reading/want to read.
I was just working on a shortcut to answer a question via iMessage about books I’ve read by looking up the information in Book Tracker. It’s not working, and so I was trying to troubleshoot with Logger, but found no guidance on using Logger to track error messages.
Logger allows you to capture internal values. It has no way t lo hook into the errors Shortcuts encounters. They are managed exclusively by Shortcuts. That’s why a native debugger for Shortcuts has been a request that’s been floating around for many years.
I don’t have the Book Tracker app, but I guess the action being used where you are hitting the issue is looking up and retrieving data about the book.
Try a new shortcut with just that action, manually populated with data you know is in the app and run it to see what happens. Basically simplify things just for a test case and see if the action is broken or if there is something about the data being passed in in your original shortcut that is off.
If the latter, replace the data being passed in in your original shortcut with the same static data as your test shortcut. Then one by one, put the dynamic data back in and run the Shortcut. When it begins to fail you have found an issue with the data and you can compare the Logger entries to what you manually entered.
Do not there could be more than one issue, so it is important to go step by step and resolve any issue as it arises before moving on to check the next.
Hopefully that all.make sense and gives you a bit of direction on what to try next.
