ShazamKit supported for iOS apps that can run on Mac silicon?

All of the bug report numbers posted here pertain to a similar issue for libswiftWebKit.dylib, and those are addressed. Those bug reports made a difference, so thank you for filing them!

I haven't yet seen any of those bug reports for libswiftShazamKit.dylib, which the OP asked about, so for anyone encountering this message with ShazamKit, please make sure to file a bug report and to record the FB number here to make sure we can take a look at them.

— Ed Ford,  DTS Engineer

Does it need more FB's for the ShazamKit issue to even take a look at this issue? Just want to understand the process.

Looks like I am being sent around in circles by Apple. After more than a week I finally got a reply through Feedback Assistant with the answer to ........

...... post the issue on this forum and refer to the forum message in the FB report.....

Come on, please can you provide me with some support here rather than sending me back and forth?

@ridmaur, can you include your FB number? I'd like to see the redirection loop that you're stuck in.

— Ed Ford,  DTS Engineer

See FB16554632

@ridmaur, I left some internal notes on FB16554632 to break that redirect loop you were stuck in. We will take a look at this further internally now.

— Ed Ford,  DTS Engineer

I’m also facing the ShazamKit issue. FB17045898

Me again. Any progress on this now we do have nother person reporting the same issue. I cannot understand why this is taking so long for Apple to provide a proper response. What else is needed to expedite this beyond this forum and filing a bug report.

@WunDaii, thank you for filing FB17045898. I've made a note that it is related to FB16554632 in this thread.

@ridmaur, you've done what you needed to with filing FB16554632. The investigation is underway.

— Ed Ford,  DTS Engineer

Any update on the investigation? Any info on when to expect at least some feedback, resolution or otherwise on this issue.

I am now blocked for months to update my app for Apple Mac Silicon, that used to work without issues in the past, without any clear understanding why and when to expect at least an answer.

I would argue that paying for the Apple Developer program and the fee Apple is witholding from my app revenue, would at least accommodate for a better response than I have witnessed so far. Apologies for my humble rant, but I am deeply frustrated about the lack of communication on this issue.

Yesterday, I announced on another thread that the bug disappeared:

I can announce that this bug has magically disappeared with the latest version of Xcode Version 16.3 (16E140) installed on my Mac. I never got any response back from Apple directly whether this was a bug or not and whether this has been solved in whatever shape or form. Completely in the dark and just by retrying over and over again I finally discovered the bug has been fixed. I would really like to understand what is the purpose of the Feedback Assistant other than a big black hole where you submit a bug into without ever getting any valuable feedback. Very disappointed the way Apple's support for developers is working, given the yearly fee you have to pay. Happy, the bug is miraculously solved so I finally can provide an update of my app that works for Mac (designed for iPad) situations again.

However, with a new update of my app submitted to App Store I once more hit the same bug. So not resolved yet.