Team, this is an ancient issue and the use case has gone nowhere. If I'm using the applicationMusicPlayer over the systemMusicPlayer, I'd expect the session boundary to exist within my application.

As it stands the nowPlaying widget is being managed by Apple's Music app service as is the AudioSession by the look of it. I obviously want to be able to handle the nowPlaying controls within my app, I obviously want to be able to handle the AVAudioSession and its interruptions inside the app, otherwise, I wouldn't bother using the applicationMusicPlayer.

At the risk of sounding confrontational, if you want to know why since 2016, developers haven't flocked to Apple's streaming service as a provider for their users over Spotify, it's not down to it not being as popular, it's down to issues like this making it unserviceable.

Feedback report has since been updated by someone from Apple:

"Potential fix identified – For a future OS update"

Having the same issue. Please look into this

The issue is resolved in iOS 16 and macOS Ventura.

The issue was resolved in iOS 16 and macOS Ventura. The limit is now much higher and more difficult to run into.

https://apps.apple.com/in/app/rocketsim-for-xcode-simulator/id1504940162?mt=12

Rocket sim provides this as a premium feature

Status was updated to "Potential fix identified - For a future OS update"

Closing, no longer reproducible.

Hi,

My issue is not about a transient issue just from 3/27.

These are production receipts that consistently return this error. If you try the example curls in the file, they will reproduce for you.

Regarding the "sudo doesn’t read from stdin so this doesn't work", this is likely happens because Swift's Process uses posix_spawn(2), which has no support for setting terminal process group TPGID, at least on Darwin.

An easy fix would be to call tcsetpgrp(3) after process.run() as follows:

tcsetpgrp(STDIN_FILENO, process.processIdentifier)

See https://stackoverflow.com/questions/76088356/process-cannot-read-from-the-standard-input-in-swift for more details.

Hello Anthony,

Thank you for filing the feedback report. It looks like there was an increase in these errors immediately after 3/27, but it has since subsided. If you continue to see this issue at a high rate, please file a new feedback.

If the issue is resolved, you can close this feedback by selecting “Close Feedback” via the Actions button found above. If we don’t hear from you in the next two weeks, we’ll assume the issue is resolved or not reproducible and will consider this issue closed. After this time, you can create a new Feedback report if the issue remains. Thank you.

"Der Teilweise" wants to let you know: https://layer8.space/@teilweise/110185240128982744

Basically, you are calling willMove(:) but should be calling addChild(:).

It's April 2023 and this is still an issue in macOS Ventura 13.3.1 (22E261) on a Mac Studio with 128 GB or RAM.

Also one other hopefully helpful tidbit, if we call the storekit 2 history endpoint it fixes the issue on verifyReceipt.

repro steps: call verifyReceipt over and over, fails continuously call https://api.storekit.itunes.apple.com/inApps/v1/history/ORIGINAL_TRANSACTION_ID once everything works again on verifyReceipt

For a somewhat similar example, see what Xcode shows for deprecated methods:

1. The deprecation warning details for the selected method.
2. A small warning icon on the right side of the method.

I think my suggestion could be patterned after this: A small red icon in the listing indicating platform/version requirements prevent the method from being used (without a fallback), and show the requirements themselves under the description. Add red warning text as needed.

https://reviews.llvm.org/D110216 was the fix. https://reviews.llvm.org/D116342 only fixed a crash introduced by D110216 when printing a warning.

Duplicate of https://openradar.appspot.com/radar?id=5536358726631424, close

Confirmed the fix on iOS Simulator 16.0 with the following environment - macOS: 13.3 (BuildVersion: 22E252) - Xcode: 14.3 (Build version 14E222b) - xcrun: 64 - simctl: PROJECT:CoreSimulator-885.2 - iOS: 16.0 - device: iPhone 12 simulator

As for iOS 15.5, the phenomenon still persists. I'd like to close this issue once

Please also see FB11991898 "Sheet does not appear when triggered while a popover is visible"