Thanks @ivanmah That's a great head start!!

Thanks for the info @sabyankees, but I'm still having trouble running this sample code using Xcode 13 and iOS 15.1 I've changed: .controlProminence(.increased) TO .buttonStyle(.borderedProminent) (thanks @anthroDevChris) And changed: "async" TO "Task" And changed: var tasks = Set<Task.Handle<Void, Never>>() TO var tasks = Set<Task<Void, Never>>() But I still get "'async' call in a function that does not support concurrency" I don't understand what you meant by changes to 'tasks.insert'. Could someone be even more specific to help me get started?

For anyone else struggling, I changed the startSharing function in Canvas as below, and the code is running now. I'm not very current on concurrency, so I may have broken more than I fixed. `func startSharing()  {         Task{            try await DrawTogether().activate()}     }`

Hi @JoeKun. Thanks for the comment. But even when I use MPMusicPlayerController to play an Apple Music track, my iOS app running on an M1 Mac always returns 0 for currentPlaybackTime while the track is playing. When paused, the current playtime is reported correctly. Any idea of what to do to make this work? Thanks!

@JoeKun I did submit this issue in feedback assistant nearly 1 year ago with no reply, response or resolution. Is there a better way for me to address this issue? https://feedbackassistant.apple.com/feedback/8934262

I had a user report the problem after updating to iOS 15.3 My fingers are crossed today's iOS 15.3.1 update has a fix. Of course, my fingers have been crossed for months.

What iOS are your customers on when they experience this bug? I've had only a few reports of missing data in the past few weeks so I'd hoped it was fixed in 15.3.1 Without guidance from Apple, it's a guessing game. But the more info we can share with each other, the better our guesses can be.

So far, I've had no user reports of this happening after iOS 15.4 update. Has anyone else had the bug reported from a user on 15.4? I hope it's been fixed, and REALLY wish Apple would start acknowledging their open bugs. I want to be compassionate regarding possible workplace slowdowns, but without updates about what's going on, I get the sinking feeling that a bunch of Apple folk are staying home in their PJs ;-)

Thanks so much for sharing! It works exactly as you describe. Any unexpected consequences that you've noticed? I'm checking to be sure the music player is playing (otherwise, pause get unpaused) but it seems to be reliable. Such a shame that code arounds like this have to be shared in dev forums rather than iOS bugs being addressed. But I do appreciate you sharing your solution!