I'm seeing a crash on AVSpeechSynthesizer as well - it *just* started yesterday, on January 20th. I didn't put out an app update recently and there haven't been any recent iOS updates, either, so it's unclear why this class would just randomly start crashing all of a sudden. I've filed my bug report as FB8977390. I'm attaching the relevant stack trace below. OP, is this the same crash you are seeing? Exception Type: EXCBADACCESS (SIGSEGV) Exception Subtype: KERNINVALIDADDRESS at 0x0000000143794089 VM Region Info: 0x143794089 is not in any region. Bytes after previous region: 295050 Bytes before following region: 442231 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL MALLOCLARGE 143700000-14374c000 [ 304K] rw-/rwx SM=PRV --> GAP OF 0xb4000 BYTES MALLOCSMALL 143800000-144000000 [ 8192K] rw-/rwx SM=PRV Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [21347] Triggered by Thread: 13 Thread 13 name: com.apple.TextToSpeech.SpeechThread Thread 13 Crashed: 0 TextToSpeech 0x00000001a7ca6e4c TTSCreateDecryptedDataFromEncryptedData + 168 1 TextToSpeech 0x00000001a7ca6e6c TTSCreateDecryptedDataFromEncryptedData + 200 2 TextToSpeechBundleSupport 0x00000001b0b5d674 -[TTSVocalizer loadResource:mimeType:resourceURL:supportsAccurateWordCallbacks:] + 424 3 TextToSpeechBundleSupport 0x00000001b0b5aa34 -[TTSSpeechServerInstance loadVoiceResource:voiceResource:] + 484 4 TextToSpeechBundleSupport 0x00000001b0b5a510 -[TTSSpeechServerInstance initializeSpeechEngine:] + 1852 5 TextToSpeechBundleSupport 0x00000001b0b5a794 -[TTSSpeechServerInstance initializeSpeech:] + 56 6 TextToSpeechBundleSupport 0x00000001b0b57c10 -[TTSSpeechServerInstance processCurrentRequest:] + 64 7 TextToSpeechBundleSupport 0x00000001b0b58e44 -[TTSSpeechServerInstance handleSpeechThread] + 1552 8 TextToSpeechBundleSupport 0x00000001b0b57bc0 SpeechThread + 48 9 libsystempthread.dylib 0x00000001d30e5b40 pthreadstart + 320 10 libsystempthread.dylib 0x00000001d30ee768 thread_start + 8

After removing the speech synthesizer's delegate, I haven't been able to reproduce. So that seems to be the workaround for now, if your app doesn't rely on the functionality in the delegate. (It breaks an animation for me, but I'd rather lose that than have the app crash all the time.) I agree that it must be something with a certificate expiring (or at least something along those lines) - that would explain why it randomly cropped up out of nowhere.

I have a major app update scheduled to go live on January 28th, will the OTA update be pushed out before then? Or should I resubmit with the workaround to ensure there are no crashes on launch day?

The same thing was happening to me on beta 3. The time-sensitive tag wasn't getting applied to my notifications until I restarted my phone. Spent over an hour trying different things to get it to work 🤦‍♂️

Filed as FB9452624.

The Xcode release notes say that this issue was fixed in beta 3. It definitely was not - just tried building on the just-released beta 5 and am still seeing the same thing with 3,500 warnings in my project.

Filed as FB9484119 with a sample project showing the issue.

Very strange that this works just fine when adding the image to a UIImageView, but using the exact same image in drawRect does not. Using hierarchical or multicolor symbols in drawRect works as well, just not the palette images.

I just realized this isn't happening solely with Intents-related code. I had added a little Swift file so that my Obj-C code could call out to the new Swift-only AppStore class that lets you open the subscription management screen in-app - the auto-generated Swift bridge has a bunch of nullability warnings for that code as well.

Same issue here. I did just notice that one of my alternate icons had an extra pixel in height, so I'm going to see if that fixes the warnings on next submission, but I wouldn't be surprised if that was just a coincidence.

I'm seeing the same thing for the Modular Duo face now on the Series 7.

I am seeing the same thing. Works fine without using a token, gives an error when the token is included.

The API limits definitely haven't been exceeded - I have subscribed for 2m calls per month and have used just 40k of them so far. And calls from other users are going through just fine.

It seems to always be the same users, but I even tried having them go through a proxy server and they are still getting the error. Whenever I try the same request for the same location, though, it loads just fine. So I'm not really sure what's going on. Here's one of their requests in case it helps: /v1/weather/en-US/42.047/-96.163?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily And I submitted this as FB11577100 in case you need the ticket for internal tracking purposes.

I was just able to reproduce this using the following request: /v1/weather/en-US/41.925/-87.64?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily Tried again a little later and it worked just fine.