Hello, I am facing an issue with NSTask (Process), NSPipe (Pipe) and NSFileHandle (FileHandle). I have an app that executes a child process (command line utility) and gets its output via Pipe instances set as standardI/O of Process instance. I can observe two logic flows: Once the child process exits, -[Process readabilityHandler] gets called where I gather the $0.availableData. Once the child process generates output (i.e. print() is executed by the child process), -[Process readabilityHandler] also gets called which makes sense. This is the case when exit() is not called by the child process (i.e. continuous execution). However, when LLDB is detached, #2 is false, i.e. -[Process readabilityHandler] is not called. Wrong behaviour also happens if I don't rely on readabilityHandler, but instead use Notification to receive changes in data availability. In such case, notification gets called continuously with empty data (even though child process does generate the output). If I don't create Pipe instance for standardI/O of the Process, then readabilityHandler does get called, but with an empty data continuously. I have created a DTS #756462540, since this doesn't make any sense. Prerequisites* app is not sandboxed Big Sur 11.0.1 (20B29) Xcode 12.3 (12C33)

We define an event handler for OpenURL NSAppleEventManager *appleEventManager = [NSAppleEventManager sharedAppleEventManager]; [appleEventManager setEventHandler:self andSelector:@selector(handleGetURLEvent:withReplyEvent:) forEventClass:kInternetEventClass andEventID:kAEGetURL]; And we handle it here: (void)handleGetURLEvent:(NSAppleEventDescriptor *)event            withReplyEvent:(NSAppleEventDescriptor *)replyEvent { // Handler type stuff } If I'm debugging in Xcode, I see a SIGCONT before the handler is called. When I continue from the SIGCONT, I enter the handler and everything is fine. This causes automated tests to break, and is generally a pain in the you-know-where. Outside of Xcode it's fine. How can I make it stop doing this? Is there some Xcode setting I've overlooked?

Hi, thanks for adding markdown support in SwiftUI's Text with Xcode 13 and iOS 15! :) Even formatting like strikethrough works! Text("Hello ~~World~~") So which specification is supported?? This goes apparently beyond Commonmark (as strikethrough is not part of Commonmark specification). Is it GitHub Flavored Markdown or even a different spec?

I'm trying the new markdown functionality in SwiftUI but it seems that trying to render markdown from an Attributed String inside a variable strips away any new lines. This isn't the case when placing the raw markdown directly in the Text View's initialiser, as shown in the preview below. Is this a bug or is there a way to retain new lines when using Attributed String? None of the options seem to help. Thanks! import SwiftUI struct markdown_test: View {     let attStr = try! AttributedString(markdown: """ Hello **World** 👋🏻      \n\n\n\n [This is a test](www.google.co.uk) """)     var body: some View {         VStack(alignment: .leading) {             Text(attStr)             Text("Hello **World** 👋🏻\n[This is a test](www.google.co.uk)")         }     } }

Hello, I'm having trouble saving the value of an NSURL object. The code bellow is used in a c++ project, however, this issue shouldn't be exclusive to this scenario. I want to use document picker, only to choose a file and get its url, which I would use on c++ side to read/write data. That I've managed to do successfully, by passing the url to c++ side by calling FileWasPicked(std::string) c++ method. However, since document picker allows us to choose files only from public folders, I need to call start/stopAccessingSecurityScopedResource, and to call them I need to pass an NSURL object, that I get from the document picker. I call startAccessingSecurityScopedResource method before leaving didPickDocumentsAtURLs method, however I can't do that with the stopAccessingSecurityScopedResource. I've tried to save the NSURL we get from document picker in a class variable @property NSURL *m_LastUsedURL;, however it's value changes after leaving didPickDocumentsAtURLs method. My guess, is that after leaving the before mention method, the value of the object that we save a pointer to gets deinitialized. Passing the string value back from c++ and converting it to an NSURL object doesn't work either. Is there any way to save NSURL object value in this case, or call the stopAccessingSecurityScopedResource method in a different manner? I attach my current code: @implementation DocumentPicker //In a DocumentPicker.mm file //We call this method from c++, to open document picker - (void)openDocumentPicker:(NSString*)pickerType //We pass the picker type from c++ { //Find the current app window, and its view controller object UIApplication* app = [UIApplication sharedApplication]; UIWindow* rootWindow = app.windows[0]; UIViewController* rootViewController = rootWindow.rootViewController; UIDocumentPickerViewController *documentPicker = [[UIDocumentPickerViewController alloc] initWithDocumentTypes:@[pickerType] inMode:UIDocumentPickerModeOpen]; documentPicker.delegate = self; documentPicker.modalPresentationStyle = UIModalPresentationFormSheet; [rootViewController presentViewController:documentPicker animated:YES completion:nil]; } //Callback, that gets called after user successfully chooses a file - (void)documentPicker:(UIDocumentPickerViewController *)controller didPickDocumentsAtURLs:(NSArray<NSURL *> *)urls { //Start accessing file, that the user have picked if ( [urls[0] startAccessingSecurityScopedResource] ) { _m_LastUsedURL = urls[0]; //Pass the url and exit this method, to do actions in c++ GlobalCppClass->FileWasPicked(urls[0].absoluteString.UTF8String); } else { NSLog(@"startAccessingSecurityScopedResource failed"); } } //This would be called, after we finish reading the file in c++ -(void)stopAccesingFile { [_m_LastUsedURL stopAccessingSecurityScopedResource]; } @end

Hello, tldr; relaunch for background uploads isn't working as expected. I'm testing my code on iPad OS 14.6 and XCode 12.5.1. Background app refresh is ON on my device for my app. A background file upload is being setup with URLSession. The URL session is created as soon as the app starts up and not lazily created. See URL session configuration below. I have followed the test instructions as outlined here: https://developer.apple.com/forums/thread/14855, specifically launching my app not via Xcode but from the home screen and adding an exit() call after the app enters the background in the AppDelegate callback method applicationDidEnterBackground. The file transfer is initiated before the app enters the background. Here's the configuration code I'm using: let configuration = URLSessionConfiguration.background(withIdentifier: <unique_identifier>)     configuration.sessionSendsLaunchEvents = true     configuration.sharedContainerIdentifier = <container group identifier>     configuration.isDiscretionary = false     configuration.timeoutIntervalForResource = 3600 * 24 * 2 // wait for 2 days before timing out connections                urlSession = URLSession(configuration: configuration, delegate:self, delegateQueue: nil) The file in fact finishes uploading but the app isn't relaunched as one would expect. As soon as I re-open the app from the home screen, I get the requisite callbacks about the upload having completed properly. In the past when I have tested my code, the method AppDelegate:handleEventsForBackgroundURLSession used to be called after the upload finishes. That appears to no longer be the case. Any guidance/help will be hugely appreciated! Thanks Krishna

Hi, I have an app that has been online for a long time, but a very small number of users will respond with "-1009, the internet connection appears to be offline" error, but most users are normal, which may indicate that it is a device problem. The user's network uses 4G, and the user indicates that it is normal to connect to other apps. In my opinion, if my App uses URLSession to get this Error, other apps should also get it, and all apps cannot make network requests, but it is not. Currently I always ask users to restart the network or use wifi, but this may not solve this problem. Maybe the device has other network settings that can cause this problem? (The user did not use the flight mode) Anyone know any solutions or know this problem?