[speedyapoc]

Here's an excerpt from the reply that I get from filing a TSI for functionality that is ultimately a bug with iOS.

------------

Hello,

Thank you for contacting Apple Developer Technical Support (DTS).

We believe this issue is a bug. Please file a bug report via Feedback Assistant (https://feedbackassistant.apple.com). For more information on Feedback Assistant, visit https://developer.apple.com/bug-reporting.

------------

From here, typically the Feedback Assistant bug report will remain open. For years. With no acknowledgement.

I would happily pay Apple a developer rate to fix these bugs. Some of them are massive showstoppers in a large scale production application.

[chongli]

I think it's safe to say that Apple doesn't care about any individual developer unless they are large enough (i.e. Adobe) to move the needle. If developers really wanted to get Apple's attention, they wouldn't boycott Feedback Assistant, they'd boycott the App Stores. If enough developers pull their apps off the market it would move the needle and Apple would have to pay attention.

[culi]

> I would happily pay Apple a developer rate to fix these bugs. Some of them are massive showstoppers in a large scale production application.

Wow that's pretty intense. Any examples of such show-stopping bugs?

[speedyapoc]

Here's a few recent ones:

1. Xcode 15's "Replace Container" feature replaces the app container with incorrect permissions that results in the app not being able to write to its container (ex. the documents directory). This is an important feature for debugging and flat out doesn't work.

2. Apple's AVPlayer has an API called MTAudioProcessingTap which allows you to get access to low level audio data. Since iOS 17.1, it is not possible to have more than one MTAudioProcessingTap running at the same time.

3. AVPlayer's `addPeriodicTimeObserverForInterval` function will randomly stop calling back to its observer, and never recover, when connected to an Apple TV via AirPlay on iOS 17.

Issue 1 makes debugging more arduous. Issue 2 stops my app from being able to crossfade audio together or play more than one audio stream at once. Issue 3 requires me to build my own time observer which is further technical debt, versus being able to rely on Apple's API.

I've spent hours debugging each of these and trying to find a workaround before resigning myself that it's a platform issue and relegating myself to abandoning that specific API or feature.

[toast0]

> Issue 3 requires me to build my own time observer which is further technical debt, versus being able to rely on Apple's API.

IMHO, it's the same amount of technical debt, regardless of who built it. In this case, the overall situation is worse: because you didn't build it, you can't fix it. If you have a dependency built by a benevolent provider, that may mean less work for you in the future, but it's still technical debt.