Anyone know how to set Side By Side Comparison in the new commit UI? New UI seems to missing a lot of features like multi-select of files to discard/stage...

this is our code foe fetching the apnstoken - and registering for the FCM and snding it to our servers. - we are consistently getting apns == null import 'dart:io'; import 'package:firebase_messaging/firebase_messaging.dart'; import 'package:firebase_auth/firebase_auth.dart'; import 'package:cloud_firestore/cloud_firestore.dart'; import 'package:firebase_messaging/firebase_messaging.dart'; import 'package:solaris/services/fetch_deviceId.dart'; Future initializeFCM() async { final FirebaseMessaging _firebaseMessaging = FirebaseMessaging.instance; // Request notification permissions for iOS final settings = await _firebaseMessaging.requestPermission(); print('Notifcation Permission Status: ${settings.authorizationStatus}'); String? apnsToken; int retries = 0; const int maxRetries = 60; const Duration retryDelay = Duration(seconds: 2); // Retry fetching the APNs token until it's available or max retries are reached while (apnsToken == null && retries < maxRetries) { print(retries); apnsToken = await _firebaseMessaging.getAPNSToken(); if (apnsToken == null) { await Future.delayed(retryDelay); retries++; } } if (apnsToken != null) { // APNs token is available, proceed to get FCM token String? fcmToken = await _firebaseMessaging.getToken(); if (fcmToken != null) { // Register the device and token with your backend await registerDeviceAndToken(fcmToken); } else { // Handle the case where FCM token is still null print('FCM token is null.'); } } else { // Handle the case where APNs token is not available after retries print('APNs token not available after retries.'); } } Future registerDeviceAndToken(String fcmToken) async { //fcmToken = fcmToken; print(fcmToken); final user = FirebaseAuth.instance.currentUser; if (user == null) { print('❌ User not logged in'); return; } final deviceId = await DeviceInfoService.getUniqueDeviceId(); //final fcmToken = await FirebaseMessaging.instance.getToken(); print('📱 Device ID from register_fcm: $deviceId'); print('📩 FCM Token from mew getapnd function: $fcmToken'); if (deviceId == null || fcmToken == null) { print('❌ Failed to get deviceId or fcmToken'); return; } final docRef = FirebaseFirestore.instance .collection('master_users') .doc(user.uid) .collection('deviceId') .doc(user.uid); // This document holds a map: { deviceId: fcmToken } print(docRef); try { // Get current data, fallback to empty map final snapshot = await docRef.get(); final data = snapshot.data() ?? <String, dynamic>{}; print(data); // Update or add current deviceId key data[deviceId] = fcmToken; // Save updated map back to Firestore await docRef.set(data); print(data); print('✅ Device ID and FCM token updated/stored under correct structure'); } catch (e) { print('❌ Firestore write error: $e'); } }

Hi I've downloaded the latest version of Xcode 14.2 but when I run the app in Simulator I can only test it on iOS16.2 Is there a way to run it in 16.3?

I have a SwiftUI app that I've been working on in XCode 16.1. The project builds and runs in the simulators, on my mac and on my iPhone/iPad without any issues. I'm also able to build my unit test project and run them without any errors. The project has zero warnings in it. When I go to the Edit Schemes options and change the Run scheme to be a Release build with the Debug Executable unchecked I get a compiler error: Command SwiftCompile failed with a nonzero exit code I've attempted this Release Run with the following target devices in XCode: My iPhone 15 Pro Max (iOS 18.2 Beta 3) MacBook Air (M1) (15.2 Beta) iPhone 16 Simulator (iOS 18.1) Any iOS Simulator Device (arm64, x86_64) All 3 of these target have the same issue. Normally I would just debug the error from the logs but when I look at the build output I can't see any information in the log to tell me what happened. It looks like the source files are sent into the SwiftCompiler and the compiler fails without bubbling up the issue. I've provided the full error log export as a Gist HERE due to it's size. Is there anything in the log I'm missing? Is there a way for me to turn on more verbose logging during compilation of a Release Build? I created a brand new Multiplatform App in XCode and I added all of my source files to it. No project configuration settings were changed. I could build it successfully with the debug configuration. I then changed it to the Release configuration and experienced the same error. I can create another fresh project and make the same release configuration with none of my source files in it and get a successful build. I t seems there is something wrong with my source files and the release configuration but the compiler doesn't indicate what. I'm lost at this point as I can't figure out how to get a release build and can't seem to find any indication as to why.

Hi everyone, I’ve been struggling with an issue related to the com.apple.developer.fonts-provided-by-application entitlement in Xcode. Despite configuring everything correctly, I’m still encountering an error stating that the fonts provided by application are missing. Here’s a breakdown of what I’ve done so far: Entitlements File: My entitlements file includes the com.apple.developer.fonts-provided-by-application key set as an array with 28 font items listed (e.g., Lato-Bold.ttf, Montserrat-SemiBold.ttf, etc.). All font names match the actual filenames, including extensions, and are spelled correctly. Info.plist: I’ve listed all the fonts under the UIAppFonts key, and they match the entries in the entitlements file. Font Files in Xcode: All font files are present in my project and included in Build Phases &gt; Copy Bundle Resources. Provisioning Profile: The Fonts capability is enabled in my App Identifier in the Apple Developer Program, and I’ve regenerated my provisioning profile to ensure it reflects this entitlement. What’s Working: Other entitlements in the entitlements file (like keychain access and sandboxing) are functioning correctly, so the entitlements file is linked properly to my app target. The provisioning profile shows everything else is in sync. What’s Not Working: Xcode consistently shows the error "missing fonts provided by application", even though I’ve verified the fonts, file paths, and plist entries multiple times. Questions: Could this issue be related to the placement of the fonts folder within my project structure? Do I need to remove unused fonts or adjust file extensions (like .ttf vs .otf)? Is there another step I might be missing in Xcode or the Apple Developer Program? Any guidance would be greatly appreciated. This has been a challenging problem to resolve, and I’d love to hear from anyone who has encountered something similar.

Xcode16.2+iOS18以上的系统，加载图片http类型的url时，会自动升级为https，下面是Safari自动打印的日志：This content was automatically upgraded and should be served over HTTPS.有什么解决方案吗？

In app purchase is not executed in ios while i run the code in xcode 16.3 But it's working fine in Xcode 16.0. There is no proper error message or any alerts showing. It just returns an empty product identifier. Provide the me the solution or kindly fix the issue in xcode IDE regarding this issue in latest xcode

Xcode16.2 加 iOS18 以上的系统加载图片 http 类型的 url 时， http 链接会自动升级为 https，请问有处理方案吗？浏览器报错信息如下：This content was automatically upgraded and should be served over HTTPS.

Apple's push cannot receive information, use the open-source library JdSoft. Apple.Apns.Notifications Because I am not familiar with it, I modified Tls12. Does anyone know how to modify this open-source library to achieve push functionality apnsStream.AuthenticateAsClient(this.Host, this.certificates, System.Security.Authentication.SslProtocols.Tls12, false)

After updating to 16.3, my project now fails to compile with the diagnostic: "Command SwiftCompile failed with a nonzero exit code". This is a SwiftUI document project with two local packages, the second of which is a rather large one with 112 SwiftUI files. It is this second package that is failing. There are no issues when compiling with 16.2. Without diagnostics I'm having a bit of difficulty in determining the cause. My thought is to regress the commits unit 16.3 gives a success, or shows issues. Although I'm not catching a similar issue in the forums, I'm seeing other problems with 16.3. Has anyone else had such build failure isolated to 16.3? Any advice on other ways to approach this problem? Thanks in advance

I am creating an xcframework for a static library for iOS, but I am encountering a perplexing issue with Xcode 16.3. When I build an xcframework using C++ in one project and import it into another project, the application runs with corrupted memory. In the framework project, I use os_unfair_lock, but when attempting to lock, the app crashes due to a state error. This suggests that memory corruption is occurring. When the xcframework is built with Xcode 16.2, a proper binary is generated, and the app runs without any problems. Since I do not want to disclose the source code, I am trying to construct a minimal project that reproduces the issue, but so far I have not been successful. Fundamentally, I feel that the compiler in Xcode 16.3 cannot be trusted.

I have had content blockers in the Mac App Store for years. Ever since moving to Sonoma, doing a clean build or archive in XCode deletes the extension from Safari settings since it never gets into the built app. The only way for me to get it back is to remove the DerivedData and target, reboot, and create a target with a different name. That works and stays around in Safari settings as long as I only build and don't clean. However, a clean or an archive removes it again. Restoring a version of the project from Time Machine that was posted to the App Store weeks or months ago doesn't work. However I can download the version of the app in the App Store, and it works, but I can't build it now from the source code that was used to build that version without going through the above process. Moving from Sonoma 14.7.1 to 14.7.2 didn't work. I would move to Sequoia if I had reason to believe that would work, but I don't. Safari 18.2, Sonoma 14.7.2, 32GB, 2.2 GHz 6-Core Intel Core i7

If I create an Xcode (version doesn't matter, 16.N )project of type framework then install some dependencies using SPM. Then within the Frameworks and Libraries section, the Embed part is empty. This doesn't happen if the project type is app rather than framework. If I want to set this to embed or not embed then how can this be done if its not even visible, for that matter how can I tell what it is set to even?

I have an app that connects to a BLE device and registers its services. I can create a notification when my app is running on foreground or background, but is it possible to show a notification when a message is recieved from the BLE device while the app has been killed by the user?

Hi! I´m new developing in this app, I have a problem. The preview screen is showing me the image bellow, There is no other response, I dont know what could happened. Thanks!

Error (Xcode): unsupported option '-G' for target 'x86_64-apple-ios14.0-simulator' I keep getting this error when trying to running my program. I asked chatgpt, deep-seek, and cursor yet nothing... Can anyone help! Thanks

Hi everyone, I'm encountering a persistent issue when trying to build my React Native project for iOS. I'm using the react-native-vision-camera library (version 4.6.4) and I've set my iOS deployment target to 16.0 in the app.json file. Despite this, the build process fails with an error related to the react-native-vision-camera pod, which seems to be stuck on an older version (2.15.4) that requires a different C++ version and a lower deployment target. Here's what I've tried so far: Ensured that the C++ version is set to 17 as required. Cleared and reinstalled all pods (rm -rf ios/Pods ios/Podfile.lock followed by pod install). Confirmed that the deploymentTarget in the app.json is set correctly to 16.0. However, the error persists and the build continues to fail, pointing to a compatibility issue with the react-native-vision-camera pod. I'm not sure if there's a cache issue or a configuration step I'm missing. Environment: React Native version: 0.76.7 react-native-vision-camera version: 4.6.4 iOS deployment target: 16.0 Expo SDK version: 52.0.40 Attached: app.json, eas.json, package.json, and the error log screenshot. Error log screnshot: Files: app.json eas.json package.json Any insights or suggestions from the community or Apple engineers would be greatly appreciated. Thank you!

I have a sample SwiftUI iOS app. As shown in the screenshot below, my project has three configurations: Debug, MyDebug, Release. If I select the Debug or MyDebug scheme, I get a preview. But if I select the Release scheme, I get an error that says the following. ”***.app” needs -Onone Swift optimization level to use previews (current setting is -O) , where *** is the app name. It probably has nothing to do with the Preview error, but the Info.plist has a dictionary such that the key name is devMode, and the value is $(DEVMODE). And I have a user-defined setting as shown below. My ContentView has the following. import SwiftUI struct ContentView: View { @State private var state: String = "" var body: some View { VStack { Text("Hello, world!: \(state)") } .onAppear { if let devMode = Bundle.main.object(forInfoDictionaryKey: "devMode") as? String { print("Development mode: \(devMode)") state = devMode } if let path = Bundle.main.path(forResource: "Info", ofType: "plist") { if let dict = NSDictionary(contentsOfFile: path) { print("**** \(dict)") } } #if DEBUG print("Debug") #elseif MYDEBUG print("MyDebug") #else print("Que?") #endif } } } #Preview { ContentView() } So my question is how I get the preview for all three build schemes? Muchos thankos.

I am trying to run Xcode 15 on macOS 15.4. As we need to build framework with older versions of Xcode. Any work around for it?

macOS Version 15.3.2 (Build 24D81) After initiating via Shift/Command/0 the Developer Documentation Window, the indexing of v277 index structure is starting /Users/[name]/Library/Developer/Xcode/DocumentationCache/ ==> but unfortunately not ending! Activity Monitor reports during hours high CPU (~80%) for Xcode process, but the indexing does not stop or end. After hours it is still around 146 MB instead of about 550 MB as in previous releases. Indexing starts with 11 or more threads, but suddenly it drops to 10 threads and seems stopping, still using cpu. Also restarting Xcode does not help. Process restarts but after some minutes seems to hang or stuck around 200MB indexed. Also removing subfolders does not help. (NSOperatingSystemVersion(majorVersion/ 16, minorVersion/ 3, patchVersion/ 0) they are recreated but index still stucks after some time. No clue. will reverting back to 16.3 beta2 Reported via FB16926964