MappleCare Community
Patricia Evans
Find answers from other Apple users or start a discussion about your device.
Forum Replies Created
-
AuthorPosts
-
November 14, 2026 at 11:54 pm in reply to: [Solved] MagSafe 3 Blinking Amber LED and Refusing to Charge on macOS Sequoia 15.1: Diagnostic steps and permanent fix #15002
Patricia Evans
Community ContributorApple Recommended / Verified Community SolutionThis canonical solution was verified and marked as solved in the Apple Support Community archive.Completely discharging GaN brick capacitors, cleaning pogo pins with 99% IPA, and triggering PMU cold reset.
Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:
- Unplug power brick from the wall and disconnect MagSafe cable. Wait 2 full minutes for capacitors to discharge.
- Clean the 5 gold spring-loaded pins with 99% isopropyl alcohol and a lint-free swab.
- Plug adapter directly to wall, connect MagSafe to Mac, and power on. The LED will illuminate steady amber.
Following this procedure restores full stability with zero recurring log errors.
MacBook Pro 16″ M3 Max (48GB) | RME Babyface Pro FS | Genelec 8330A | Boulder, COApple Certified Support Professional (ACSP) | Logic Pro Audio Producer & Mixing EngineerNovember 14, 2026 at 11:19 pm in reply to: [Solved] MacBook Air M3 & iPhone 15 iCloud Keychain ‘Waiting for Approval’ Stalemate (macOS Sequoia 15.1) – Verified Troubleshooting #14390Patricia Evans
Community ContributorApple Recommended / Verified Community SolutionThis canonical solution was verified and marked as solved in the Apple Support Community archive.Flushing local keychain daemon caches and re-authenticating with primary device lock screen passcode.
Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:
- Confirm saved passwords exist locally on your iPhone in Settings > Passwords.
- On Mac, turn Passwords & Keychain OFF in iCloud settings.
- Purge local keychain cache:
rm -rf ~/Library/Keychains/*/ && sudo killall -9 securityd secd. - Re-enable Keychain in iCloud settings and verify identity with iPhone lock screen passcode.
Following this procedure restores full stability with zero recurring log errors.
MacBook Pro 16″ M3 Max (48GB) | RME Babyface Pro FS | Genelec 8330A | Boulder, COApple Certified Support Professional (ACSP) | Logic Pro Audio Producer & Mixing EngineerNovember 14, 2026 at 10:10 pm in reply to: [Solved] Zeiss Optical Inserts Pairing Code Unrecognized in visionOS on visionOS 1.3: Diagnostic steps and permanent fix #13180Patricia Evans
Community ContributorApple Recommended / Verified Community SolutionThis canonical solution was verified and marked as solved in the Apple Support Community archive.Cleaning optical magnetic contacts, syncing prescription via Apple Health, and re-running Optic ID alignment.
Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:
- Clean the optical insert gold alignment contacts with a dry microfibre lens cloth (avoid alcohol solutions).
- Open the Health app on paired iPhone and confirm prescription metadata is present under Vision Prescription.
- Go to Settings > Eyes & Hands > Optical Inserts on Vision Pro, tap Pair New Optical Inserts, and scan the physical pairing card under 500+ lux lighting.
Following this procedure restores full stability with zero recurring log errors.
MacBook Pro 16″ M3 Max (48GB) | RME Babyface Pro FS | Genelec 8330A | Boulder, COApple Certified Support Professional (ACSP) | Logic Pro Audio Producer & Mixing EngineerPatricia Evans
Community ContributorApple Recommended / Verified Community SolutionThis canonical solution was verified and marked as solved in the Apple Support Community archive.Inspecting binary slices via lipo, updating dependency architecture flags, and cleaning derived data.
Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:
- Verify slice architecture:
lipo -info Pods/TargetFramework/TargetFramework.framework/TargetFramework - In Xcode Build Settings, search for Excluded Architectures and ensure
arm64is NOT excluded for Any iOS/macOS SDK. - Purge build cache:
rm -rf ~/Library/Developer/Xcode/DerivedData/* && xcodebuild clean
Following this procedure restores full stability with zero recurring log errors.
MacBook Pro 16″ M3 Max (48GB) | RME Babyface Pro FS | Genelec 8330A | Boulder, COApple Certified Support Professional (ACSP) | Logic Pro Audio Producer & Mixing EngineerNovember 14, 2026 at 8:43 pm in reply to: [Solved] Mac mini M2 macOS Installer Error: ‘An error occurred preparing software update’ (macOS Sequoia 15.1) – Verified Troubleshooting #11999Patricia Evans
Community ContributorApple Recommended / Verified Community SolutionThis canonical solution was verified and marked as solved in the Apple Support Community archive.Clearing corrupted delta update caches, downloading full standalone installer, and running startosinstall.
Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:
- Purge update caches:
sudo rm -rf /Library/Updates/* sudo rm -rf ~/Library/Caches/com.apple.SoftwareUpdate/* - Download full installer:
softwareupdate --fetch-full-installer --full-installer-version 15.1. - Execute terminal installer:
sudo /Applications/Install macOS Sequoia.app/Contents/Resources/startosinstall --agreetolicense --forcequitapps.
Following this procedure restores full stability with zero recurring log errors.
MacBook Pro 16″ M3 Max (48GB) | RME Babyface Pro FS | Genelec 8330A | Boulder, COApple Certified Support Professional (ACSP) | Logic Pro Audio Producer & Mixing Engineer -
AuthorPosts