Are you perhaps based in one of the "unavailable" countries?
https://9to5mac.com/2021/07/20/apple-expands-availability-of-u1s-ultra-wideband-technology-to-more-countries/
jlc3
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
Last seen
User for
Post
Replies
Boosts
Views
Activity
Update - it looks like the my test apps do get launched into the background, but less frequently on iOS 15 compared to previous versions. Sometimes days without a background launch. I haven't launched the app manually into the foreground since starting the test on October 5, 2021.
It's available now in watchOS 8.
iOS 15.1 beta 3 test so far is inconclusive. One app got some limited background processing time, but the test is confounded by having Background Modes checked for Background fetch and Background processing. Disabling those now. The other app, which works fine on iOS 14, didn't get any processing time.
default 11:12:21.732196-0400 dasd com.apple.healthkit.background-delivery.tld.domain.app1:094E1A:[
{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}
], FinalDecision: Must Not Proceed}
default 11:12:21.732573-0400 dasd com.apple.healthkit.background-delivery.tld.domain.app2:F09C36:[
{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}
], FinalDecision: Must Not Proceed}
default 11:12:21.734499-0400 dasd com.apple.healthkit.background-delivery.tld.domain.app3 (production app):53F125:[
{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}
{name: FileProtectionPolicy, policyWeight: 0.010, response: {Decision: Absolutely Must Not Proceed, Score: 0.00, Rationale: [{classALocked == 1 AND activityFileProtection == <File Protection: ClassA>}]}}
], FinalDecision: Absolutely Must Not Proceed}
Then I got lines like this, but only for the production app:
default 11:27:08.675816-0400 dasd com.apple.healthkit.background-delivery.tld.domain.app3:53F125:[
] sumScores:68.598232, denominator:68.620000, FinalDecision: Can Proceed FinalScore: 0.999683}
default 11:27:39.184446-0400 dasd COMPLETED com.apple.healthkit.background-delivery.tld.domain.app3:53F125 at priority 30 <private>!
Nils-B, any update? I think we're seeing the same problem.
See ~/Library/Caches/org.swift.swiftpm/.