smb big sur

Looking for some advice around how best to communicate a new feature release that is guarded by an A/B test. Only 50% of upgraded users will be seeing the new experience. What would you say are the pros/cons of releasing with updated App Store assets and release notes that discuss this big new feature, but only 50% will be able to see it / use it. Is it best to wait to release new assets / notes discussing the feature once it's at 100% rollout for all users? Or is it acceptable to release earlier - and have some customers wondering why they aren't seeing it. Thank you!

I need to elicit the location of the user in the Siri intents and so I call: override init(){ super.init() self.locationManager=CLLocationManager() self.locationManager.delegate = self; self.locationManager.startUpdatingLocation() self.locationManager.requestWhenInUseAuthorization() } Still neither public func locationManagerDidChangeAuthorization(_ manager: CLLocationManager) nor public func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation]) are ever called, notwithstanding the presence of the correct entry in the info.plist, the inclusion of the library and the indication of the delegation with: class IntentHandler: INExtension, INSendMessageIntentHandling, CLLocationManagerDelegate, UISceneDelegate are ever called. Is there any problem with CLLocation manager on intents? What would be a big problem as there is no way to share information with the main app!

Hey everyone, I'm encountering an issue with audio sample rate conversion that I'm hoping someone can help with. Here's the breakdown: Issue Description: I've installed a tap on an input device to convert audio to an optimal sample rate. There's a converter node added on top of this setup. The problem arises when joining Zoom or FaceTime calls—the converter gets deallocated from memory, causing the program to crash. Symptoms: The converter node is being deallocated during video calls. The program crashes entirely when this happens. Traditional methods of monitoring sample rate changes (tracking nominal or actual sample rates) aren't working as expected. The Big Challenge: I can't figure out how to properly monitor sample rate changes. Listeners set up to track these changes don't trigger when the device joins a Zoom or FaceTime call. Please, if anyone has experience with this or knows a solution, I'd really appreciate your help. Thanks in advance! ⁠

i have a game that i upload it in the app store that my game size is 3 gigaByte but when I download it, it show that the really size is about 100 megaByte, i upload the game in google app is given me the real size, so the problem i think is when it get out the xcode, maybe some one can give me i clue for what is going on. my game was made by unity2020. if that helps.

I've updated to Sequoia 15.4 and Xcode 16.3 on my Intel iMac 2019 and now everything Xcode does results in a spinning rainbow. Open a window? Spin. Look up documentation? Spin. Compile the app? Well that doesn't spin, but simple things like compiling a storyboard now takes over 5 minutes. Every compile needs to redo compiling Clang modules over and over again. And compiling the project at times just stalls out. It's been bad for a while but now with these versions it's gotten even worse. Is Apple just saying give up on Intel and get an M-series Mac just to develop with? On my Intel Mac the project takes over 19 minutes to compile. The main storyboard takes almost 7 minutes alone! It didn't take this long with Xcode 16.2. The other storyboards are showing times of over 4 minutes as well, a vast increase. A swift file with two functions, neither of which is over 10 lines, takes 87 seconds? It seems like everything involving swift code is now taking much much longer to compile. And don't even get me started on d