If you are receiving a regular push notification and try to read the content of the push notification in AVSpeechSynthesizer, it will read the text when the app is in the foreground, but when the app is closed, stopped, or in the background, it will display “Unable to list audio folders” and the text cannot be read.
I couldn't find anything in the documentation about whether this works for critical alerts, so if anyone knows, please let me know.
This text has been translated with DeepL
Notifications
RSS for tagLearn about the technical aspects of notification delivery on device, including notification types, priorities, and notification center management.
Post
Replies
Boosts
Views
Activity
Nous souhaitons activer l'entitlement com.apple.developer.usernotifications.filtering pour notre extension MsgNotificationService. Pourriez-vous nous fournir des instructions supplémentaires ou activer cet entitlement pour notre App ID ? Si des informations supplémentaires sont nécessaires ou des étapes spécifiques doivent être suivies.
actuellement cela n'a pas d'impact sur le build mais sur le product->archive. impossible upload le build
Une idée, un conseil ?
Merci,
The ActivityKit API requires developers to parameterize calls to pushToStartTokenUpdates by the live activity's attributes, e.g.
for await data in
Activity<AdventureAttributes>.pushToStartTokenUpdates {
// Send token to server.
}
for await data in
Activity<BoringAttributes>.pushToStartTokenUpdates {
// Send token to server.
}
At runtime, I have noticed that the token is the same for the different live activity attribute types we support in our app.
Can someone confirm if this behavior is consistent? If the pushToStartToken is the same across different live activity types, it can simplify our database design 🙏🏼.
Hello.
platform: Please let me know which platform 'Non-Apple platform' is referring to. For example, Google or Amazon? And is it correct to mean the platform that consumed the products received due to in-app purchases?
playTime: Does 'playTime' mean the time when the customer purchased the app and actually accessed the app? Or do you mean the time you accessed after the in-app purchase?
When a user receives a provisional notification and they click the "Keep" button and choose deliver immediately, there is no OS setting changes. The notifications are stuck in "delivered quietly" unless the user happens to change that in their Settings.
When a request comes from the server, I want to set the screen time API of the requested phone or retrieve usage information. I would like to use silent push to complete that action in the background.
Is it impossible for the Screen Time API to run in the background?
I download the image from remote and use local image url to fill communication notification.
But notification attachements do not display
Our Java backend application is responsible for sending millions of push notifications. However, we are encountering an issue where thousands of connection resets occur daily. This irony leads to an inability to keep up with the volume, resulting in a lag that affects real-time performance.
The application is built on Java, utilizing JDK 1.8 and the Apache HttpClient for network communications. Below is the Maven dependency we use:
XML
Additionally, we employ Spring’s RestTemplate to dispatch push notifications. Here is a snippet of the pseudo-code used to call the Apple Push Notification service (APNs):
Java
ResponseEntity postForEntity = restTemplate.postForEntity(apnsURL, entity, responseType);
getResponse(aPNSResponse, postForEntity);
AI-generated code. Review and use carefully. More info on FAQ.
It’s important to note that our calls to APNs are not made directly but are routed through an F5 load balancer, which then communicates with the APNs endpoint.
Could someone guide us in the right direction to resolve these connection reset issues?
Can I use Screentime API in CLLocationPushServiceExtension?
For example, I am curious about whether it is possible to set a managed setting in the Screentime API to limit app usage time or change the time limit.
If the implementation of the above function is impossible or causes rejection by the App Store, is there a way to use the Screentime API in the background through push notification?
ello!
I am writing to seek your assistance regarding an issue we have encountered with the in-app purchase subscriptions in our application.
Issue Description
In our application, when a user initially subscribes and opts for the free trial, the product identifier is co.cleaner.storage_001. However, upon renewal, the product identifier changes to co.cleaner.storage_003. This change is causing issues because our backend system relies on the product identifier to manage subscriptions.
Assistance Required
We would like to understand the following:
Does Apple change the product identifier when transitioning from a free trial to a renewal? If so, how should we handle this situation?
Is there any configuration or setting that can ensure the same product identifier is used during both the free trial and the renewal period?
Any recommendations or solutions to ensure our subscription management system can correctly handle user renewals.
Attached are the first free trial data and the renewal notification data for your reference.
Thank you very much for your help and support. I look forward to your response.
Best regards,
Hello!
I am writing to seek your assistance regarding an issue we have encountered with the in-app purchase subscriptions in our application.
Issue Description
In our application, when a user initially subscribes and opts for the free trial, the product identifier is co.cleaner.storage_001. However, upon renewal, the product identifier changes to co.cleaner.storage_003. This change is causing issues because our backend system relies on the product identifier to manage subscriptions.
Assistance Required
We would like to understand the following:
Does Apple change the product identifier when transitioning from a free trial to a renewal? If so, how should we handle this situation?
Is there any configuration or setting that can ensure the same product identifier is used during both the free trial and the renewal period?
Any recommendations or solutions to ensure our subscription management system can correctly handle user renewals.
Attached are the first free trial data and the renewal notification data for your reference.
Thank you very much for your help and support. I look forward to your response.
Best regards,
first free trial data
renewal notification data
We are using Apple Notification V2 and supporting only one subscription service per user (e.g., Netflix with Basic, Premium plans). In Notification V1, we could fetch the latest subscription information using the /verifyReceipt API. However, the documentation for Notification V2 suggests using SignedDataVerifier to decode the data locally.
This raises a concern that the data received via notification might not always be up-to-date. For example, if a user cancels a subscription but the server fails to process the notification for some reason, and later the user upgrades and resumes the subscription, the new notification succeeds. In this scenario, the previously failed cancellation notification will be resent after some time. How should the backend server handle this?
Should we always use APIs like get all subscription statuses to fetch the latest data instead of solely relying on the decoded data from each notification?
No message notifications coming through
Tried all these steps
Force restart
DIsabled focus mode
Notifications are enabled in both device and in app settings
Disabled summary notifications.
Tried sending notification from pusher tool, that also is not showing up in the center.
What could be the reason and a possible solution?
Good day!
Recently, we are doing the feasibility study for transferring our App from team A to team B.
Our App uses Apple Push Notifications service (APNs) and we know we need to recreate certificates after the App transferring.
We have a question that can we use the old device tokens which are registered before the transferring to send the notification to users?
For example,
Before the transfer:
User A installs App and upload tokenA_old to our service server.
Our service server stored it into our database.
After the transfer:
User A doesn’t launch App and we only have the tokenA_old which is stored in our server.
After we recreate push notification certificate, can we send notification with tokenA_old to user A?
Or his device token will be renewed after the App is transferred?
Does he need to launch App and get the new registered device token from APNs and upload it to our server again?
override func application(
_ application: UIApplication,
didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data
) {
let deviceTokenString = deviceToken.map { String(format: "%02x", $0) }.joined()
uploadDeviceToken(deviceTokenString)
}
We want to check above question for following tokens:
deviceToken (Push notification)
API: https://developer.apple.com/documentation/uikit/uiapplicationdelegate/1622958-application
pushToStartToken (Live activity)
API: https://developer.apple.com/documentation/activitykit/activity/pushtostarttoken
Does deviceToken will be renewed after the App is transferred?
Does pushToStartToken will be renewed after the App is transferred?
Thank you.
Tried all these steps
Force restart
DIsabled focus mode
Notifications are enabled in both device and in app settings
Disabled summary notifications.
Tried sending notification from pusher tool, that also is not showing up in the center, for the device effected but on another device it is working fine for the same application(same version too)
What could be the reason and a possible solution?
Experiencing 403s (InvalidProviderToken) [https://api.push.apple.com/3/device/] due to invalid or unverifiable provider tokens. We have noticed that after retrying the request inline, the notification is delivered successfully without any changes to the request even with same authorization token.
Someone please guide or suggest why it is happening as the JWT token which is generated is correct because we are caching the jwt token and using the same token to send out the subsequent request which is kind of successfull.
Sending the notification for multiple team Ids under the same application.
Hello.
I have a few questions about Location Push Service and Screentime Family controls.
Do Location Push Service and Screentime Family controls require permission to be tested with development builds?
Will my application for permission to test be approved?
How long does it take to receive results if I apply for permission?
Is it possible to use the functionality of the Screentime api in LocationPushServiceExtention?
Is it possible to control remotely even if I apply for Screen time API's Family Controls permission as an individual? (ex. Change Screen time settings by push from server)
Information is needed to plan an app that includes both functions.
Thank you
According to the documentation (https://developer.apple.com/documentation/usernotificationsui/unnotificationcontentextension), a Notification Content Extension should consist of a UIViewController that adopts the UNNotificationContentExtension protocol.
The only problem is that UNNotificationContentExtension's methods are not @MainActor isolated, but UIViewController is, which produces this error when you try to build your code with Complete concurrency checking turned on:
Main actor-isolated instance method 'didReceive' cannot be used to satisfy nonisolated protocol requirement
If you add nonisolated, you are then left with another problem in that UNNotification is not Sendable.
What is the recommended solution to this problem?
Hello All, I am getting following popup for our application,
I have implemented PTT Push To Talk framework by following https://developer.apple.com/documentation/pushtotalk/creating-a-push-to-talk-app
We are using following VoIP entitlements, Our app support from iOS 12
i) com.apple.developer.pushkit.unrestricted-voip
ii) com.apple.developer.pushkit.unrestricted-voip.ptt
We have updated app with new Push To Talk framework and it's working fine. Our app's minimum deployment target is iOS-12.0 , So app will also work without using PTT framework for older iOS.
Question,
Why popup display even after new Push To Talk framework implementation?
what should I do to remove this popup from showing? Should I do any other setting to complete this framework?
Thanks.