I am attempting to implement App Refresh with the Background Tasks framework - https://developer.apple.com/documentation/backgroundtasks and I cannot get the app to wake. Obviously I can get it to wake with debug functions - https://developer.apple.com/documentation/backgroundtasks/starting_and_terminating_tasks_during_development, but I cannot seem to have the app refresh occur normally. At first I assumed I was doing something wrong, so I went and downloaded the Refreshing and Maintaining Your App Using Background Tasks - https://developer.apple.com/documentation/backgroundtasks/refreshing_and_maintaining_your_app_using_background_tasks sample code. I edited it to OSLog every step of the way and ran that on two separate devices for over a day. One device is a test device for work, the other is my daily driver. Upon inspecting the logs I'm not seeing any of my log messages indicating executions of the App Refresh Tasks, on either device. Searching the logs with "com.example.apple-samplecode" provides a bunch of messages from dasd. It looks like when the app has first been loaded onto the phone it came up with a "Final Decision" of "Can Proceed" but then was immediately followed up with plain com.apple.duetactivityscheduler default 2021-02-16 10:48:29.767009 +1100 dasd scoring 'bgRefresh-com.example.apple-samplecode.ColorFeed.refresh:5EE83C' CurrentScore: 0.617755, ThresholdScore: 0.772525 DecisionToRun:0 Which seems like something made it decide it shouldn't run (based on "DecisionToRun:0"). Subsequent messages from dasd the decision always becomes "Must Not Proceed", with the vast majority of logs appearing like so plain com.apple.duetactivityscheduler default 2021-02-16 10:58:25.975816 +1100 dasd scoring bgRefresh-com.example.apple-samplecode.ColorFeed.refresh:5EE83C:[ {name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}  ], FinalDecision: Must Not Proceed} Occasionally there'll be extra policies, but vast majority of the time it's just the ApplicationPolicy. There seems to be one of those log entries, from dasd, quite frequently with the most frequent being mere tens of milliseconds, all the way up to 4 minutes; though the most common time between evaluation does appear to be ~30 seconds. With nearing an additional day of running the app on both devices I am seeing within about a 3 hour window another dozen "Can Proceed" messages immediately followed by "DecisionToRun:0", but there haven't been any more for the last 10 or so hours. Obviously also none of my log messages are there either. Is there something, obvious or otherwise, that am I doing wrong here?

I have downloaded the SF Symbols 2 beta from the developer website and noticed that after installing the SF Symbols 1.1 version installed on my system can no longer be opened. The app icon shows as broken and when you attempt to open the app it brings up a dialog 'The application "SF Symbols" can't be opened.' Additionally, when I try to re-install SF Symbols 1.1 it fixes that application but appears to completely remove the SF Symbols 2 beta application from the Applications folder. Is it not possible to have these installed side-by-side on the same system?

An email error meant that I didn't see one of the labs I'd booked had been confirmed, and stupidly I didn't check the website, meaning I missed being able to attend it. I didn't notice this until 10 minutes ago, which means unfortunately registration for tomorrow is closed too 😔 I've been hearing a lot on Twitter and other places that the labs are largely under-booked anyways. So knowing this, are there any options to be able to register for the session tomorrow and be able to get in if its not full?