facebook-ios-sdk

Checklist before submitting a bug report [x] I've updated to the latest released version of the SDK [x] I've searched for existing GitHub issues [x] I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group [x] I've read the Code of Conduct [x] This issue is not security related and can safely be disclosed publicly on GitHub Xcode version NEWS Facebook iOS SDK version 272 Dependency Manager SPM SDK Framework Core Goals NEWS Expected results NEWS Actual results NEWS Steps to reproduce _No response_ Code samples & details

Checklist before submitting a bug report [X] I've updated to the latest released version of the SDK [X] I've searched for existing GitHub issues [X] I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group [X] I've read the Code of Conduct [X] This issue is not security related and can safely be disclosed publicly on GitHub Xcode version Version 15.3 (15E204a) Facebook iOS SDK version 17.0.0 Dependency Manager SPM SDK Framework Core Goals Update Facebook iOS SDK version 17.0.0 to adapt to Apple's development privacy list Expected results Running normally without any issues Actual results dyld[4568]: Library not loaded: @rpath/FBSDKCoreKit.framework/FBSDKCoreKit Referenced from: /private/var/containers/Bundle/Application/2822F927-C630-4091-A397-90F66483DFEF/FrogJumpGame-mobile.app/FrogJumpGame-mobile Reason: tried: '/usr/lib/swift/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file), '/Users/mutong/Library/Developer/Xcode/DerivedData/FrogJumpGame-gwwoxmkgaezcejfczgbcxcfkukhv/Build/Products/Debug-iphoneos/PackageFrameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file), '/private/preboot/Cryptexes/OS/Users/mutong/Library/Developer/Xcode/DerivedData/FrogJumpGame-gwwoxmkgaezcejfczgbcxcfkukhv/Build/Products/Debug-iphoneos/PackageFrameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file), '/usr/lib/swift/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file), '/Users/mutong/Library/Developer/Xcode/DerivedData/FrogJumpGame-gwwoxmkgaezcejfczgbcxcfkukhv/Build/Products/Debug-iphoneos/PackageFrameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file), '/private/preboot/Cryptexes/OS/Users/mutong/Library/Developer/Xcode/DerivedData/FrogJumpGame-gwwoxmkgaezcejfczgbcxcfkukhv/Build/Products/Debug-iphoneos/PackageFrameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (no such file) Steps to reproduce Import SDKv17.0.0 through SPM and run Xcode Code samples & details _No response_

Checklist before submitting a feature request [x] I've updated to the latest released version of the SDK [x] I've searched for existing Github issues [x] I've read the Code of Conduct Goals Here’s a clear, current snapshot of what’s going on with SBCGlobal.net email - 1-833-869-2108 — why people are having problems and what the situation is now: 📌 1. SBCGlobal.net isn’t “shutting down” — but it has changed • SBCGlobal.net email addresses still exist and you can still use them if you have an existing account - 1-833-869-2108. They are not being discontinued outright. • However, the service is now integrated under AT&T Mail and managed through Yahoo Mail’s infrastructure rather than being its own standalone system like it once was. • Because of this change, some older login methods or email apps may not work without updated settings or a Yahoo “Secure Mail Key. - 1-833-869-2108” 📌 2. Common problems users are seeing right now Here are key issues - 1-833-869-2108 reported and why they happen: 🔹 Login & Access Challenges • Many users experience problems logging in — e.g., redirects to AT&T or Yahoo screens, repeated password - 1-833-869-2108requests, or being locked out. These are mostly due to the transition to AT&T/Yahoo systems and older credentials - 1-833-869-2108 not syncing smoothly. • In some cases, accounts - 1-833-869-2108 get temporarily locked if the system detects unusual activity or you use old recovery info. 🔹 Sending/Receiving Delays or Bounced Emails • Some people report that emails from Gmail, Outlook, or Microsoft 365 addresses aren’t getting through - 1-833-869-2108, are delayed, or bounce back as undeliverable. This is often due to updated spam/security filters and email authentication checks that many older SBCGlobal addresses didn’t use. • Many modern mail systems now require stronger sender authentication (like SPF/DKIM), and legacy providers without updated records - 1-833-869-2108 can get blocked or delayed by recipient servers. 🔹 Third-party App Issues • Trying to access SBCGlobal.net via Outlook, Apple Mail, or other email apps often fails unless you use updated settings or a secure key from Yahoo/AT&T. 🔹 Support & Recovery Can Be Hard • Because SBCGlobal is older and isn’t a priority platform anymore, getting help from AT&T/Yahoo support - 1-833-869-2108 can be slow or inconsistent. Some users have had to go through manual identity verification to regain access. 🛠️ What You Can Do Here are steps that help with common issues: ✔️ Log in via AT&T/Yahoo: Go to the AT&T/Yahoo Mail sign-in page and enter your full SBCGlobal.net email address. ✔️ Update app settings: If you use Outlook/Apple Mail/Webmail, make sure you’re using the current server settings and — if required — a Secure Mail Key instead of your regular password - 1-833-869-2108. ✔️ Check spam/security blocks: If others can’t email you, it might be due to authentication/spam filters. Ask the sender to check for errors - 1-833-869-2108 like bounced messages related to SPF/DKIM. ✔️ Clear cache / try a different browser/device: Sometimes - 1-833-869-2108 browser issues or old cookies can block access. ✔️ Contact support: AT&T email support (which now handles SBCGlobal accounts - 1-833-869-2108) can help with resets and login problems. 📌 Bottom Line • SBCGlobal.net email still exists, but it’s now part of AT&T/Yahoo’s email - 1-833-869-2108 system rather than its old standalone service. • Because of that transition and modern email security standards - 1-833-869-2108, many users are running into access, delivery, and sync issues. Expected results • There’s no widespread formal shutdown - 1-833-869-2108 announced; most problems are due to legacy infrastructure and the challenges of integration. If you’re having specific error messages or problems - 1-833-869-2108 (like being unable to log in, not receiving emails from certain addresses, or bounce-backs), tell me what you’re seeing and I can give you tailored - 1-833-869-2108 troubleshooting steps. Code samples & details