PN rejected based on pushDisallowed here too, iOS 15.2.
Romano_Ba
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Hi,
I had a similar issue while doing some dev regarding Silent Push Notifications.
I was sending notifications sall day long and finally met some limits:
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[Max allowed CPU Usage level]: Required:50.00, Observed:75.00},]}}
], FinalDecision: Must Not Proceed}
From this moment, the Push Notifications were not completely cancelled, but rather delayed until app was entering on Foreground.
Policy is not the same, but it seems I managed to reset the CPU Usage Level by incrementing the version of the app.
I could then see some device logs mentioning Relaxing scores on the next Notification reception.
default 17:14:43.708426+0200 dasd com.apple.pushLaunch.***:9722B2:[
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.50, Rationale: [{cpuLevel == 50}]}}
] sumScores:94.410000, denominator:96.910000, FinalDecision: Can Proceed FinalScore: 0.974203}
default 17:14:43.709007+0200 dasd 'com.apple.pushLaunch.***:9722B2' has compatibility score of 0.917862 with 'com.apple.pushLaunch.***:1D1192'. Relaxing scores.
default 17:14:43.709773+0200 dasd 'com.apple.pushLaunch.***:9722B2' DecisionToRun:1 (Bypasses Predictions)
Hope it helps.