I am receiving a push through "incomingPushResultForChannelManager" of Push to talk Framework and setting a remote participant through "pushResultForActiveRemoteParticipant" or setting a remote participant using "setActiveRemoteParticipant" directly in the PTT App without receiving a push.
When the app establishes a remote participant on a channel, an Audio Session is started anew and will receive an active Audio Session.
The problem is that the time to activate this Audio Session is not short.
For this reason, there are many cases where the first part of the other party's voice passes without being played.
Also, if the app is running in the foreground, even if it doesn't acquire a new audio session, it can play the voice through the app's own audio session. However, by restarting the Audio Session, the Audio Session is changed unnecessarily and the voice playback is delayed.
Question. Can I set the Audio Session to not change when setting the remote participant's information?
If this is not possible, please advise on a solution for the case where the audio session is activated after the voice starts to be received.
Post
Replies
Boosts
Views
Activity
According to the article linked below, it is explained that apps that have been closed by the user cannot be woken up using Silent Push.
https://developer.apple.com/forums/thread/714426?login=true
However, what we actually saw in iOS 16 and iOS 17 is that apps that the user has closed wake up with an Silent push and start running in the background.
There was confusion about which action was right.
Please help me understand this behavior.
I'm going to apply the Location Push Service Extension function to the app I'm currently developing.
It's still in the development stage, and it hasn't been uploaded to TestFlight.
When request permission for the Location Push Service Extension feature, it says App Store url is required.
Can this feature be added after the app is deployed to the App Store?
I tried to test it through CloudKit, but the CLLocationPushServiceErrorDomainError3" error occurred in CLLocationManager's startMonitoringLocationPushes method, so I can't test it either.