Popping Sound

[quote='854282022, juozas, /thread/797007?answerId=854282022#854282022, /profile/juozas'] Or should I file a separate one? [/quote] It’s probably better to do this. Assuming that I’ve understood you properly (-: It sounds like you want installer packages to be able to install and activate system extensions. If so, that’s a question for the installer team, as opposed to the NE team, and so a separate bug report makes sense. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've been pulling my hair out, even after pulling everything out in to a on a simple Multi-platform project, with two demos. ASK and Not ASK. If ASK isn't completely branched it burns BT radios. In the flagship sample project private static let pinkDice: ASPickerDisplayItem = { let descriptor = ASDiscoveryDescriptor() descriptor.bluetoothServiceUUID = DiceColor.pink.serviceUUID return ASPickerDisplayItem( name: DiceColor.pink.displayName, productImage: UIImage(named: DiceColor.pink.diceName)!, descriptor: descriptor ) }() I only see bluetoothServiceUUID provided, in the docs however: Each display item’s descriptor, a property of type ASDiscoveryDescriptor, needs to have a bluetoothCompanyIdentifier or bluetoothServiceUUID, and at least one of the following accessory identifiers: bluetoothNameSubstring A bluetoothManufacturerDataBlob and bluetoothManufacturerDataMask set to the same length. A bluetoothServiceDataBlob and > bluetoothServiceDataMask set to the same length. It wasn't until I removed bluetoothN

It sounds like you may be embedding a framework in your app that has already been signed. Here's a document that talks about the right way to sign embedded frameworks: Technical Note TN2435: Embedding Frameworks In An App

Custom sound not playing issue is fixed in the latest beta builds. If it is not working for you, and you have made sure your sound file is correct (supported format and less than 30 seconds), please file a bug report For sounds not looping, please file a Feedback report for consideration.

I’ve now upgraded Xcode to the latest available build: Xcode 26.0 beta 5 (17A5295f). This should, in theory, resolve the version mismatch issue you highlighted. Please let me know if I should expect to wait for beta 6 specifically, but since this is the latest release, I assume it covers the ABI/runtime symbol alignment. Current behavior: macOS (Intel MacBook Pro): The app launches successfully, and the window is displayed. Pressing the record button (⭘) results in console logs: localeNotSupported could not record: invalidAudioDataType Playback works (I can hear the recorded sound), but there is no transcription displayed and no highlighting. Play button plays back my speech. iOS (iPhone 11, iOS 26.0 beta): Same as macOS above, except playback volume is extremely faint, even at maximum system volume. Question regarding Dictation: I also tried enabling Edit → Start Dictation from the menu, and accepted the prompt. After that: I don’t see any option to disable it within the app. Turning off Dictation i

I’m having the same issue. Until beta 5 or 6 the custom sound file wouldn’t even play and it would only play a system sound. I’m hoping this is still just a bug and they fix these issues but I’m not sure what to expect.

I understand how it work now, thank you for your explanation! Sounds like usage of EntityQuery is required by the Intent framework, and Entity for Visual Intelligence is not exempted from it. I understand it allows AppEntity to be more verastile, although personally I think the Entity->ID->Entity retrieval process could be optimized in the case of Visual Intelligence, assuming there's an underlying collectionView that maps each cell to the Entity instance. Thanks again for your help!

Thank you for your answers, Argun! While most of the answers are very helpful, I am puzzled by the one regarding duplicated sessions. As you can see in the screenshot, for example, session ID 5B155CE8-6AA9-4A3F-BCD0-9D88AF69F196;1 was linked to all three different classifications (laughter, shouting, speech), which is the opposite of each sound classification within the same utterance or call will output a separate identifier explanation. It's the same case for all the other session IDs ; and all these session IDs are linked with the same time stamp and the same start time. And it's not uncommon, below is another example from the same subject. I marked the records with same time with the same name; note that the blue records are again the same session ID linked with three different classifications. And in general why would a same segment be classified to different categories? Does that mean all of them are possible but can't be sure? Therefore, is there any recommended cut-off of the confidence (e.g.

Let me try to clarify some of this: Microphone Activation: Q: how is the microphone being turned on to capture a speech session? A: Speech Metrics are collected when the user has already engaged the microphone - through a Siri utterance or through telephony (a VoIP app, the Phone app, FaceTime). SensorKit does not manipulate the microphone itself Q: how is each session determined to be an independent session? A: each session mainly marks a Siri utterance or a phone call. But changing system conditions with the audio subsystem during a session (a long phone call where the user starts a call, switches to a Bluetooth headset, and perhaps connects to a car audio, for example) may change session ids. Negative Values: Q: In the speech classification data, there are entries where some of the start and end values are negative A: this is not expected behavior, and we would need to see what exactly is being sent to your app. Please file a Feedback Report with as much details of the occurrence, and log

@DTS Engineer after much tweaking I've managed to reduce the working configuration to: s.user_target_xcconfig = { 'STRIP_STYLE' => 'non-global' } This works but sets the stripping style of the whole user project. I took a look at the output of Xcode build phases for the pod target and -exported_symbols_list doesn't work with cocoapods (out of the box) because cocoapods generates static lib by default. However setting s.static_framework = false did produce a dynamic framework but the symbols still are stripped. I'm not sure what other consequences STRIP_STYLE would have... sounds like a setting this only for my library is a bad idea, but I'm out of ideas on how to keep the symbols. I also tried passing each symbol directly to the linker and that also did not work s.user_target_xcconfig = { 'OTHER_LDFLAGS' => '$(inherited) -Wl,-u,_ios_prepare_request -Wl,-u,_ios_set_request_header -Wl,-u,_ios_present_webview -W...' }

When Apple compensates me hourly at your salary to devise sample projects for the bugs I find in your new stuff, maybe I'll take the time to do so. I have a day job, and my hobby is having a top 10 iOS app. I'm already working stupid hours to make your stuff look good (and have had the most fun since you made everything flat in iOS 7 and killed a bunch of joy so that's not actually a complaint). My report was mostly to help others with a workaround if they got themselves in that state. I mean, maybe I'm doing something weird here. I've isolated the bugs I care about in sample projects. It usually takes at least an hour to do a good job because I have a very complex view hierarchy. I'm not making a sample project for every bug for a trillion dollar company. That sounds like work, not something I should spend time away from my family for.

How are you identifying these particular devices? And is your app in the foreground when you are not able to identify? This problem sounds like one of the two typical cases we see, 1- The advertised name and the GAP name of the devices are different. When the device has never been seen before, CoreBluetooth will report the advertised name. Once connected, the GAP name of the device will be cached, and the next encounter, CoreBluetooth will report the cached GAP name instead of the advertised name. If these names are different, and you are specifically looking for a match in the peripherals name, this could be the mismatch. I would suggest to either make both names the same, or look for either of the possible names. 2- what is the advertising rate of the Wiser device? When your app is not in the foreground, the scan rate will dramatically drop down, and if the peripheral is not advertising fast enough, 3 minutes may not be enough to reliably detect the advertising. To reliably detect the device under