Popping Sound

I’ve experienced these too, along with also wanting the option of NO sound for the alarm, just vibration on the watch and iPhone.

One idea I thought of would be to add a flag to my CoreData that allows one date to be selected as widget ready then the creation of the widget could pick that up. I'm not sure this is better than just creating a iOS 16+ intent that allows a date & description entry as the widget is being added. One feature that would be really useful would be if the same date is selected as one that's in the database already, then the description text from the database could be offered as a default. I have no idea how I'd go about that but it sounds useful.

Hey there, You might trie this: I had updated the iOS emulator to iOs 26.0, earlier I had iOS 18.4 and 18.6 and the latest 26.0 I removed the iOS 18.4, and I configured the simulator to run iOS 26.0, and in the first start of the simulator with the new iOS version the sound glitched a bit (I had a YouTube video open in a safari tab) I Quite the core audio process (the OS restarts it automatically after) then the sound was back normally, after that in the simulator no kind of media can be played (it shows a play logo with a side arrow on it). then I just quite the simulator and reopened it again, and it did work. no glitches with the sound from the browser tab, and the sound in the simulator works (tried YouTube on safari) and media content. I hope this is clear and helps someone, use the latest iOS version, -> quite the simulator -> Reopen it again -> (if sound glitches still happen force-Quite the core audio process) -> Reopen the sim

We've received several reports of a new bug while setting up our products with WAC. The Accessory Setup UI appears with a blank network selected and the message 'This accessory will be set up to join (null).' at top. The user can tap Show Other Networks... to select another network, but this experience is very confusing. Why does this UI present a choice that is known to be invalid when other valid choices exist? I'm not sure of what specifically changed but it sounds like we broke something. Have you filed a bug? If so, what's the bug number? Is there anything I can change in my iOS code or in my accessory's WAC server to improve this experience? No, you don't have any control over this UI. However, one thing I would suggest is filing a separate bug asking us to redesign how WAC pairing works and integrating this into AccessorySetupKit. At this point, the WAC pairing APIs are quite old and need to be revisited, with AccessorySetupKit being the most natural home for them. Finally, this assumes that y

Hello. Ed asked me to look into this question as I handle a lot of iOS Code Signing questions. Reading through the conversation so far it sounds like your App ID may have inadvertently gotten registered to one of the other accounts you are using (most likely the account with the name 'Or Itach' associated with it). Please login directly to developer.apple.com using your other accounts and verify that the App ID you are trying to use is not registered in any of your non-company accounts. If you find the App ID in any of your other accounts, delete it. Once you have done that, you should be able to add it to your Green Vibe account. If this does not help then I'd like to review the settings on your machine, check App IDs registered to your account(s), and help you get this set up right. So we can work on that together in private, please start a code level support request. Here's a link for starting a code level support request: https://developer.apple.com/support/technical/ If you start a code level su

Hello, It's sounds like your configuration is correct (including use of platform-specific bundle) and you've discovered another bug in macOS. We expect parity with iOS. Try syncing the bundle with App Store Connect again and if that doesn't work send us a bug report. You'll also want to ensure you're testing a version of your game that isn't live yet.

@Christopher_Rice, you should hear from someone through your other inquiries regarding Indoor Maps. From the update I received today, it sounds like that has already happened, but if not, they should be in touch soon. — Ed Ford,  DTS Engineer

minimum deployment target set to 1 That sounds like your app's version number or maybe its build number. The deployment target is the minimum iOS version your app supports. It should be at least iOS 15, if not something more recent. If it's something older (like iOS 12), then you should raise it and expect to see the libswift files disappear from your app, since they aren't needed for recent iOS versions. How can I integrate a static library (.a file) into an iOS app so that it does not appear in the final app bundle? It should appear in the Link Binary with Libraries build phase, and not subsequently appear in any build phases that copy files into the built app. Cocoapods is a third-party tool, so you'll want to check that they aren't doing anything to copy the file and seek their support if you need help with configuring their tool. — Ed Ford,  DTS Engineer

Thanks, I should have mentioned that I also tried OSLog and could not see any output in the console app. All I did was: let logger = Logger() logger.error(authFill some text) Now, I am realizing the outward behavior is a little different on MacOS, so possibly prepareInterface(forPasskeyRegistration registrationRequest: any ASCredentialRequest) is not executing on MacOS (Designed for iPad). On both systems, it is popping Create a passkey dialog and letting me choose my provider and continue. But on MacOS it then displays my CredentialProviderViewController view. That never appears on iOS. I just get the desired callback to prepareInterface. I will investigate further. At this point, I am just trying to understand the webauthn/fido flow and implement my own key management and signing. I guess I can do that just as well on iOS, and worry about MacOS later.

Open Audio MIDI Setup and change every output device to 44.100 Hz. Finally, open the Terminal and run the next command: sudo killall coreaudiod.

func createFixAlarm(_ ck: CKRecord, _ cdate: Date, _ block: ((Bool, String?)->Void)? = nil) async { if cdate <= Date() { JCTips.showTip(闹钟时间不可小于当前时间！) block?(false, nil) return } let keynoteDateComponents = DateComponents( calendar: .current, year: cdate.year, month: cdate.month, day: cdate.day, hour: cdate.getOnComponent(.hour), minute: cdate.getOnComponent(.minute)) let date = Calendar.current.date(from: keynoteDateComponents)! typealias AlarmConfiguration = AlarmManager.AlarmConfiguration let stopButton = AlarmButton( text: 我知道了, textColor: .white, systemImageName: stop.circle) let alertPresentation = AlarmPresentation.Alert( title: LocalizedStringResource(stringLiteral: ck[RecordData.title.rawValue] as? String ?? 快开始了!), stopButton: stopButton, ) let attributes = AlarmAttributes( presentation: AlarmPresentation( alert: alertPresentation), metadata: JCMeta(), tintColor: Color.accent) let su = ck[RecordData.sound.rawValue] as? String let alarmConfiguration = AlarmConfiguration( schedule:.fixed(date),

Our recommendation is to use semantic colors so they automatically adapt. It sounds like you're doing that, but sometimes it's not working? Here's an older thread where another developer seemed to be having the same issue, and was able to reproduce the error with our sample app. Can you do the same, and compare to my screenshots from that thread? — Ed Ford,  DTS Engineer