I am attempting to use the AVSpeechSynthesizer to include text to speech in my Swift Playgrounds project, but when I attempt to use it on my IPhone i get the following errors: It works just fine on the simulator, but no audio is produced when I run it on-device. Is there a way to set this "bundle display name" within Swift Playgrounds, or are there any workarounds? My code: import AVFoundation class Speaker { let synthesizer = AVSpeechSynthesizer() func speak() { let utterance = AVSpeechUtterance(string: "Test, I am the speaker") synthesizer.speak(utterance) } }

Installation has completed login is successful but after 30 secs it returns to login screen safe mode does the same. tried recovery mode and reinstalled. Still in the login loop. what are my choices now?

We are currently facing an issue with implementing "Sign in with Apple" in our iOS application built using Flutter. We've implemented "Sign in with Apple" using Firebase and On attempting to sign in, we are encountering the following error: “Sign-up not completed.” We have verified that: The Apple Sign is enabled on our Firebase Project. The Sign in with Apple capability is enabled in the Xcode project. The Apple Sign-In capability is enabled for the App ID on our Apple Developer account. All the certificates were re-provisioned after enabling the capability. The Bundle ID matches across Apple Developer portal and our app configuration. The email and fullName scopes are requested in the credential. Please let us know if you require any additional information. We’re happy to provide whatever is needed. Here's a screenshot attached to explain the problem better

System: OS: macOS 15.5 CPU: (10) arm64 Apple M1 Pro Memory: 82.02 MB / 16.00 GB Shell: 5.9 - /bin/zsh` IDEs: Xcode: 16.1/16B40 - /usr/bin/xcodebuild Managers: CocoaPods: 1.15.2 - /Users/liuxiwei/.rvm/gems/ruby-3.3.5/bin/pod SDKs: iOS SDK: Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1 Android SDK: Not Found i use react-native to build ios app . when archive than it happens: ld: Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5184.

I have raised a support ticket regadring a concern I had with apple developer account. I got a respose via email, asking some more details. After that I have replied to the same mail thread with requested details. But I havent got any respose after that. I would like to is that the correct way of responding to support ticket ? Am I suppose to get the response for the same mail thread , after I reply ? or Every time I have open a new support tikcet ?

On recent versions of macOS (including current betas), when enabling Internet Sharing from Ethernet to Wi-Fi, the configured WPA2/WPA3 password is ignored and the shared network is broadcast as an open (unsecured) network. Steps to Reproduce: Connect Mac to Ethernet via USB/LAN adapter Go to System Settings > General > Sharing > Internet Sharing Set up Wi-Fi options with a valid WPA2/WPA3 password Enable Internet Sharing Expected Behavior: Devices should see a password-protected Wi-Fi network with a lock icon and require authentication. Actual Behavior: The network appears unsecured (no lock icon) Devices like iPhone connect without entering a password This can be verified immediately from iOS Wi-Fi settings Additional Notes: Reproducible across macOS 15.5 RC and 16.0,26.0 Developer Beta Feedback has been submitted via Feedback Assistant multiple times This is a serious security risk if used in public or shared environments Has anyone else experienced this? Any known workarounds besides terminal-level defaults or Plist edits? Thanks in advance!

As developers of an app with a free basic version and a paid premium version, we recently received a malicious review on our premium app. The review falsely accused our app of being a scam and baselessly claimed it was error-ridden. This comment is clearly malicious and designed to dissuade other users from purchasing our app. The most critical point is that we haven’t had any sales records in that region recently. In response to this review, we promptly contacted Apple Support but received only a generic, templated response stating that no action would be taken. We followed up with another complaint about the review, but it was still dismissed. Apple Support provided a link to their guidelines, and within those guidelines, we found specific clauses that Apple should act upon in cases like this. We sent another email pointing this out, but we’ve received no response since. It feels like developers are left defenseless against such malicious reviews. When we face these attacks, there’s no fair judgment, and Apple doesn’t uphold the very policies it has set to protect developers’ rights. If this continues, how can developers trust this platform to safeguard their basic interests?

I downloaded Xcode Beta 26 and built the POS code repository project. However, an error appeared: unable to find the module dependency 'minizip'. No changes have been made to the repository since upgrading to iOS 18.0. Is this a new issue with Xcode 26, and what are the resolution steps?

I recently updated iOS 26 beta and now my SingPass keeps crashing when I tried to open it. can I revert back to iOS 18?

iPadOS 26 Dev Beta 1 - need to do a restore via DFU mode. I made sure iPad in normal mode shows up in Finder and I can see device details. When I boot into DFU mode (I have kept the ipad connected to mac), it does not show up in Finder. No matter what combination of plugging/unplugging cables, rebooting, again into DFU mode, it will not show up in Finder. Looking for steps to resolve this, or do I need to wait until beta 2 to resolve this?

Two days ago, I tested IOS 26 on my device, but it was still overheating severely. Today, the device is very sluggish. What should I do? Or do I just need to wait...

The MacStudio has only one account on it, and that is of course an admin account. The password to this account is lost. The MacStudio has an association with my AppleID I log into developer.apple.com with. To recover, this procedure was followed: The recovery mode was entered by holding down the power key for 15 seconds. In the options that appeared the "Forgot all passwords" option was clicked on. I entered the same credentials I log into developer.apple.com with. The credentials were accepted. The shell was launched, and the in the shell the command "resetpasswords" entered. The message: "If you don't know the password for any user on your Mac, you can deactivate your Mac and set new passwords for all users. An internet connection will be required to reactivate your Mac". Beneath this message there was in blue text: "Deactivate Mac". I did not proceed after this because I was not sure what deactivation would mean for the files on the computer. On it there is code written in Swift that needs to be preserved. If the deactivation is done will the files be preserved, and be accessible? Or does a deactivation remove all files?

I’ve encountered a critical issue in macOS Tahoe (Beta) that affects the Photos app or any app that leverages Apple’s editing frameworks. After editing certain photos—whether applying filters, cropping, or making basic adjustments—the image suddenly turns completely black upon saving or exiting the edit mode. Details: macOS Version: macOS Tahoe (latest beta) Affected App(s): Photos, Preview, and some third-party editing apps Steps to Reproduce: Open a photo in the Photos app Make any basic edit (e.g., crop, adjust brightness) Click “Done” The edited photo appears entirely black Notes: Happens with both JPEG and HEIC formats Original photo appears fine before editing Exporting the photo also results in a black image Restarting the app/system does not resolve the issue iCloud Photos is enabled This issue seems related to the image rendering pipeline post-editing, possibly tied to Core Image or GPU rendering frameworks. It severely affects photo usability and could result in permanent data loss if backups are not maintained. Please advise if a workaround exists or if this bug has been logged already. Happy to provide system logs or sample images if needed.

In our iOS app we have added example.com in associated domains from the very beginning With no AASA file hosted at example.com domain Now we need a subdomain app.example.com to be intercepted in our app, so for the same, we are thinking to host AASA at app.example.com and add app.example.com in associated domains too. so my question is will hosting AASA at sub domain works? If yes, will it affect older apps where app.example.com is not handled. In short we only want the links with app.example.com to be open in our app not the example.com links

Hello, everyone, I hope you're all doing well. I'm facing an unfortunate issue with my Apple Developer Program membership that was suddenly terminated. I received a generic email from Apple, stating that my membership was revoked, but no specific reason was provided for this action. I appealed the decision, offering all possible explanations and commitments to adhere to guidelines, only to be met with a reply stating that the decision is "final" and no subsequent appeals will be processed. Has anyone here faced a similar situation? Are there any steps that can be taken to understand the reason for termination when Apple doesn't disclose it? Is there a way to open a dialogue with Apple, even when they've stated that their decision is final? Would publicizing this issue through social media or blogs be advisable? This is a particularly trying time for us, as we are recovering from a recent earthquake and our app is our sole source of income. Any insights, advice, or shared experiences would be greatly appreciated. Thank you for taking the time to read my post. We don't violate any apple's policies... any information would be welcome. Best regards,

Hi, I'm struggling to access Keychain Access app on a brand new mac mini m4 pro running Sequoia 15.3.1. After opening the app, I get a prompt to enter the current password; after I enter the correct password the first time, the prompt opens again. I enter the correct password again and the app terminates. I've checked Console and Keychain Access process logged: Initial auth failed: Error Domain=com.apple.LocalAuthentication Code=-1000 "ACM policy evaluation succeeded, but ACM is still requesting 1:1, 3:1, 15:1 on ACMContext 111 after a retry." UserInfo={NSDebugDescription=ACM policy evaluation succeeded, but ACM is still requesting 1:1, 3:1, 15:1 on ACMContext 111 after a retry., NSLocalizedDescription=Authentication failure., BiometryType=1} terminate: void _NSDisableAutomaticTerminationAndLog(NSString *) Terminating Attempting sudden termination (1st attempt) ... App termination approved I've also tried to update the password of my user but Keychain doesn't accept the new password.

I have updated my iPhone 14 Pro to iOS 26 without any problems. I also have AirPod Pro A2698 version 7E93. The new update of the firmware is not shown.developer mode is activated.on the pre-release is AirPod Pro visible if connected but no possibility for an update.what am I doing wrong or is there any thing I have to wait for thank you

Mac users often ask whether they should install "anti-virus" software. The answer usually given on ASC is "no." The answer is right, but it may give the wrong impression that there is no threat from what are loosely called "viruses." There is a threat, and you need to educate yourself about it. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to log in to it remotely. That threat is in a different category, and there's no easy way to defend against it. The comment is long because the issue is complex. The key points are in sections 5, 6, and 10. OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits. 2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect." The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders. The following caveats apply to XProtect: ☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets. ☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked. As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware. 3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.) Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following: ☞ It can easily be disabled or overridden by the user. ☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware. ☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error. Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however. For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking. 4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT. 5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, and a technological fix is not going to solve it. Trusting software to protect you will only make you more vulnerable. The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "****** horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the scam artists. If you're smarter than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. Malware defence By Linc Davis - https://discussions.apple.com/thread/6460085

I just installed macOS Tahoe beta on a mac mini. It says I am not connected to the internet, and attempts to use file sharing fail. Network status says that Ethernet and WiFi are working. Any suggestions?

Please expedite to Solve this bug , my Singpass is unable to launch in iOS 26. I believe this is more urgent than a new pride theme wallpaper 🏳️‍🌈