Hi, I have recently downloaded the app to start learning how to code in swift and so on. On my first try I have gotten the error stating that ”.swiftpm files cannot be opened”. I have followed some forum posts. I restarted my iPad several times and redown the app several times. I tried to disable the iCloud sync but I think I deleted the iCloud directory entirely that just results in the app closing on any action taken. (such as pressing the “New App” option or choosing the quick actions to make apps). Is there a way to fix this? Any help is appreciate, please ask me to provide any extra needed information.

Today I got stuck with a weird behaviour with my c++ project. There is the code which doesn't catch exception from standard library (the same snippet works well on intel mac and under linux machines). Code snippet: #include <exception> #include <stdexcept> #include <iostream> #include <string> int main() { try { std::stod("notanumber"); } catch (const std::invalid_argument&) { std::cerr << "Caught std::invalid_argument" << std::endl; } } Compilation command: clang++ -fno-rtti main.cpp -o main && ./main Clang versions: clang++ --version Homebrew clang version 15.0.3 Target: arm64-apple-darwin21.6.0 Thread model: posix InstalledDir: /opt/homebrew/opt/llvm/bin Also tried: Apple clang version 14.0.0 (clang-1400.0.29.102) Target: arm64-apple-darwin21.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin Output: libc++abi: terminating with uncaught exception of type std::invalid_argument: stod: no conversion [1] 65643 abort ./main Expected output: Caught std::invalid_argument Other info: Chip: Apple M1 OS: 12.6

I'm working with CBConnectPeripheralOptionNotifyOnConnectionKey, and my understanding is that it should trigger an alert when a reconnection occurs while the central app is in the background. To test this, I've set up two separate iPhone devices—one acting as the peripheral and the other as the central. The process I'm using is as follows: The central app connects to the peripheral app. I then switch to a different app on the central device, which causes the central app to go into the background. I manually disconnect and reconnect Bluetooth on the central device, which should trigger the peripheral app to reestablish the connection. However, despite the central app being in the background, I don't see the expected alert on the central side. The connection reestablishes correctly, but no alert appears. I would appreciate any insights on what might be causing this issue or if I'm misunderstanding the behavior of CBConnectPeripheralOptionNotifyOnConnectionKey. I'd be happy to provide more specific code or logs if needed. Thanks in advance! I’m relatively new to Core Bluetooth and feel like I’ve explored most of the options, but I’m still encountering this issue.

When I try to run my project on the simulator, it tells me there is a bug. It is not in the code I wrote, but I believe in the compiler. It would work perfectly, say the build succeeded, but the phone turns white and stops there. I don't know how to debunk it, what to do! Picture of what happens with the phone: Picture of the debugging area:

Lcov config file (.lcovrc) is not present in below default locations: ~./lcovrc How to link manually created lcovrc file to lcov to customise the behaviour of lcov?

Hello. I face such a problem as the fact that the screen does not work after turning on the developer mode. Read more: I'm trying to install an application that is not available in the App Store, and after installing it, I'm required to use developer mode. I turn it on, restart the phone, and the screen lits up in front of me that everything is ready to use the developer mode, and you just need to swipe up. I'm trying to do it, but the screen doesn't respond to my touch at all. I tried to restart the phone, but it didn't help. I reset it to factory settings - it didn't help either. I would like to hear advice from those people who have faced the same problem, or from those who know how to solve it.

Hello, I recently decided to start learning how to code for iOS. I don't have much coding experience but I still wanted to explore it for fun at least. I downloaded Xcode on my Macbook, and opened a new iOS file after downloading iOS 18.1 so I could run the simulator/get a preview of my code. Even though I only had the basic "Hello World!" that is auto-generated in my code, the preview would never show and sat at a loading screen for multiple hours, saying "Preparing (Automatic) iPhone Simulator" at the top. There is probably a simple solution that I'm missing. I would appreciate any tips! Thanks.

In my Mac's Settings -> General -> Storage -> Developer -> (i) I have a series of entries for "bridgeOS", all 2.49 GB except one that is "zero". Do I need these? Can I remove them? I am only doing "normal" iPhone / iPad development. (There was some previous mention of this here: https://developer.apple.com/forums/thread/711279 with no feedback.)

After changing the bundle identifier of my app, I’ve encountered several issues that I can’t seem to resolve, even though I’ve followed all the necessary steps. The app with the previous identifier was live on Testflight, and working perfectly fine, but now I’m facing the following problems: WeatherKit Authentication Issue WeatherKit has stopped working, and I’m getting authentication errors. I’ve updated the app in the Developer Portal to reflect the new bundle ID, but it still doesn’t authenticate properly. Xcode Cloud Configuration Issue: Xcode is asking me to set up Xcode Cloud again, which I understand is expected after a bundle ID change. However, during the setup process, it fails to recognize my remote repository, even though the repository is correctly added and visible under the Source Control tab. TestFlight Internal Testing Issue: I manually uploaded a build to TestFlight, but internal testers cannot use it because the invitation appears as invalid. This wasn’t an issue with the app’s previous identifier. It seems like the bundle ID change has caused some fundamental issues that I can’t resolve despite following all the usual instructions. Has anyone experienced this before or knows how to resolve these problems? I'm using the latest Xcode 16.2 on Mac OS Sequoia 15.2

In my Swift app, Xcode has decided to put various important settings like, SWIFT_VERSION under "User Defined." Does anyone know why?

We are considering the development of a new service, We would like to ask for detailed information on the feasibility of the following. Is it possible to encapsulate only xcframework, such as encapsulating xcframeworkA into xcframeworkB? If the above is possible, will the application incorporating the xcframework in the above state pass the review of apple?

The iPhone set display and brightness to automatic, the App is placed in the dock column at the bottom of the desktop, and the icon showing the dark mode appears in the light mode. Is this a system problem? device: iPhone 16 pro max system version: 18.2

Hi, I'm not sure why but when my fileURL is .jpg file and I drop the file from my app to Finder folders it make the dropped file as .jpeg Is there a way to fix it? [.onDrag { if FileManager.default.fileExists(atPath: file.path) { // Provide the file as an item for dragging let fileURL = URL(fileURLWithPath: file.path) let itemProvider = NSItemProvider(contentsOf: fileURL) // Remove the file extension in the suggestedName let baseNameWithoutExtension = fileURL.deletingPathExtension().lastPathComponent itemProvider?.suggestedName = baseNameWithoutExtension return itemProvider ?? NSItemProvider() } else { // Handle the case where the file no longer exists print("File no longer exists at path: \(file.path)") return NSItemProvider() } })

Hi, What's the difference Swift Packages Frameworks ? for me I see them the same as not an expert developer ? Which should I use ?for example for a SwiftUI UI Kit to be distributed online for sale ? Kind Regards

We have a big iOS project and we are using .xcconfig files to define our compiler options and build settings. We have our SWIFT_TREAT_WARNINGS_AS_ERRORS set to YES so that all Swift related warnings will be reported as errors. Now, we are trying to migrate to Xcode 16.1 and set 'targeted' in the 'Strict Concurrency Checking' flag. This produces some errors that are related to Swift's concurrency checks. We are now planning to have an approach where we still want to keep SWIFT_TREAT_WARNINGS_AS_ERRORS as is but we want all concurrency related warnings to be still treated as warnings while the rest will get reported as errors. We found this new compiler option - https://forums.swift.org/t/warnings-as-errors-exceptions/72925. It looks like the one we want but I think it is still not out yet and we need to wait until Swift 6.1 (correct me if im wrong). Or is there any other way to do what we want to achieve?

Hello all ! I am starting to explore UI testing with XCode and was wondering if there's a simple way to access application logs directly in XCode after the session ends. We currently have access to many things (captures, video, xctest logs) in report UI (see capture) but I am surprised we don't also have the app logs. I know there's a way of accessing it via terminal in .xcresult via a custom script (https://github.com/ChrisMash/XCResultExtractor) but I find it a little tedious and unfriendly as it gives raw .txt I also noticed I can switch processes in XCode console to see app logs but it switches back to xctest logs once the test ends ^^' Is there some "see app logs" button I missed in XCode UI or is XCResultExtractor our only option ? Thank you in advance !

Hi everyone, Since a couple days, I can't launch my watchOS widget extension in the Xcode simulator. After launching the scheme in Debug or Release, I always end up with Xcode stuck on "Waiting to attach to watchOSWidgets on Apple Watch Series 9". I already uninstalled and reinstalled Xcode and cleared all Xcode related folders in Library. I also tried to use Debug > Attach to process, then Xcode goes into "Running watchOSWidgets on Apple Watch Series 9" but no widgets are installed, neither the app so I cannot debug anything. I tried on different simulators, always end up with the same problem. However, the watch app scheme works fine, in Debug or Release, it is only the widgets extension which doesn't work anymore. This seems related to my computer, because if I create an empty project with a default watch widget extension, I still have the same issue. I really don't know what to do... Does anyone has a clue ? Thanks

Error Diagnostics I'm able to run my app on a simulator, but previews aren't working even for the simplest test preview. I build my project with XcodeGen. Here is my project.yml file: name: Ecstasy options: deploymentTarget: iOS: 17.0 xcodeVersion: "15.2" developmentLanguage: en targets: Ecstasy: type: application platform: iOS sources: - path: Sources - path: Resources info: path: Configurations/Info.plist properties: CFBundleDevelopmentRegion: "$(DEVELOPMENT_LANGUAGE)" CFBundleExecutable: "$(EXECUTABLE_NAME)" CFBundleIdentifier: "$(PRODUCT_BUNDLE_IDENTIFIER)" CFBundleInfoDictionaryVersion: "6.0" CFBundleName: "$(PRODUCT_NAME)" CFBundlePackageType: "APPL" CFBundleShortVersionString: "1.0" CFBundleVersion: "1" UILaunchStoryboardName: "" UIViewControllerBasedStatusBarAppearance: true UIStatusBarHidden: false UIRequiresFullScreen: true UISupportedInterfaceOrientations: - UIInterfaceOrientationPortrait UIUserInterfaceStyle: Light settings: base: DEVELOPMENT_TEAM: MLJ2C965T7 PRODUCT_BUNDLE_IDENTIFIER: com.raw-e.Ecstasy SWIFT_OPTIMIZATION_LEVEL: "-O" SWIFT_COMPILATION_MODE: wholemodule ENABLE_PREVIEWS: YES DEBUG_INFORMATION_FORMAT: dwarf-with-dsym CLANG_ENABLE_MODULES: YES SWIFT_VERSION: 6.0 TARGETED_DEVICE_FAMILY: 1 ENABLE_BITCODE: NO SWIFT_ACTIVE_COMPILATION_CONDITIONS: DEBUG SWIFT_EMIT_LOC_STRINGS: YES SWIFT_STRICT_CONCURRENCY: complete ENABLE_USER_SCRIPT_SANDBOXING: YES configs: debug: SWIFT_OPTIMIZATION_LEVEL: "-Onone" SWIFT_COMPILATION_MODE: incremental ENABLE_TESTABILITY: YES GCC_OPTIMIZATION_LEVEL: 0 ONLY_ACTIVE_ARCH: YES DEBUG_INFORMATION_FORMAT: dwarf ENABLE_PREVIEWS: YES SWIFT_ACTIVE_COMPILATION_CONDITIONS: "DEBUG PREVIEW" release: SWIFT_OPTIMIZATION_LEVEL: "-O" SWIFT_COMPILATION_MODE: wholemodule ENABLE_TESTABILITY: NO GCC_OPTIMIZATION_LEVEL: s ONLY_ACTIVE_ARCH: NO dependencies: - package: APITime - package: GUITime - package: LoggingTime - package: Shares packages: APITime: { path: "/Users/raw-e/Desktop/Useful Swift Things/My Packages/APITime" } GUITime: { path: "/Users/raw-e/Desktop/Useful Swift Things/My Packages/GUITime" } LoggingTime: { path: "/Users/raw-e/Desktop/Useful Swift Things/My Packages/LoggingTime" } Shares: { path: "/Users/raw-e/Desktop/Useful Swift Things/My Packages/Shares" }

Inside our app, after login (user side), getting grey screen on homepage.

Since recently (maybe after updating to Sonoma 14.7.1 - 23H222, but not sure, I get a crash report stating that SafariBookmarksSyncAgent quitted unexpectedly Once acquitted the report, it will reappear 2 minutes later as long as Xcode is open. Configuration: Sonoma 14.7.1 Safari Technology Preview Release 208 (Safari 18.2, WebKit 19621.1.5.1) Xcode 15.3 (15E204a) That seems to be a known problem. Question: Is it due to MacOS version ? To Xcode version ? To Safari version ? To webKit version ? Or to simulator, as I gat an AegirPoster crash (as described here: https://stackoverflow.com/questions/77083912/macbook-pro-crashes-when-using-simulator-aegirposter-process) I read that I would need to restart some devices (eg, iPhone). That seems to temporarily solve the problem Here is a part of the report: Incident Identifier: 0D2456DF-5801-41D6-8294-2BF442224913 CrashReporter Key: 4DE33529-174E-32C5-D8A8-26FE128BE16B Hardware Model: Mac14,12 Process: SafariBookmarksSyncAgent [38972] Path: /Volumes/VOLUME/*/SafariSupport.bundle/SafariBookmarksSyncAgent Identifier: com.apple.SafariBookmarksSyncAgent Version: 8614 (8614.1.25.0.17) Code Type: ARM-64 (Native) Role: Unspecified Parent Process: launchd_sim [28070] Coalition: com.apple.CoreSimulator.SimDevice.0058D576-D9FF-4169-8437-D0A24C923500 [9832] Responsible Process: SimulatorTrampoline [1116] Date/Time: 2024-11-27 15:19:42.4908 +0100 Launch Time: 2024-11-27 15:19:42.4610 +0100 OS Version: macOS 14.7.1 (23H222) Release Type: User Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000204476580 Exception Codes: 0x0000000000000001, 0x0000000204476580 VM Region Info: 0x204476580 is not in any region. Bytes after previous region: 894002561 Bytes before following region: 58984012416 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL VM_ALLOCATE 1cefdc000-1cefe0000 [ 16K] r--/rwx SM=PRV ---> GAP OF 0xdf1020000 BYTES commpage (reserved) fc0000000-1000000000 [ 1.0G] ---/--- SM=COW reserved VM address space (unallocated) Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [38972] Triggered by Thread: 0 Thread 0 Crashed: 0 dyld_sim 0x104f9dc7c dyld4::SyscallDelegate::forEachInDirectory(char const*, bool, void (char const*, char const*) block_pointer) const + 172 1 dyld_sim 0x104f88b6c invocation function for block in dyld4::ProcessConfig::PathOverrides::processVersionedPaths(dyld4::ProcessConfig::Process const&, dyld4::SyscallDelegate&, dyld4::ProcessConfig::DyldCache const&, dyld3::Platform, dyld3::GradedArchs const&, lsl::Allocator&) + 104 2 dyld_sim 0x104f88aa0 dyld4::ProcessConfig::PathOverrides::forEachInColonList(char const*, char const*, bool&, void (char const*, bool&) block_pointer) + 224 3 dyld_sim 0x104f886b8 dyld4::ProcessConfig::PathOverrides::processVersionedPaths(dyld4::ProcessConfig::Process const&, dyld4::SyscallDelegate&, dyld4::ProcessConfig::DyldCache const&, dyld3::Platform, dyld3::GradedArchs const&, lsl::Allocator&) + 144 4 dyld_sim 0x104f882a8 dyld4::ProcessConfig::PathOverrides::PathOverrides(dyld4::ProcessConfig::Process const&, dyld4::ProcessConfig::Security const&, dyld4::ProcessConfig::Logging const&, dyld4::ProcessConfig::DyldCache const&, dyld4::SyscallDelegate&, lsl::Allocator&) + 344 5 dyld_sim 0x104f868b8 dyld4::ProcessConfig::ProcessConfig(dyld4::KernelArgs const*, dyld4::SyscallDelegate&, lsl::Allocator&) + 152 6 dyld_sim 0x104f85e30 _dyld_sim_prepare + 352 7 dyld 0x10492fa8c dyld4::prepareSim(dyld4::RuntimeState&, char const*) + 1276 8 dyld 0x10492e4f0 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 308 9 dyld 0x10492def4 start + 1868 I filed a bug report: Nov 27, 2024 at 3:41 PM – FB15976427