I did not change nothing in my code, but after iOS 14 and Xcode 12 I started to get the crashes. Previous build was on Xcode 11 and I didn't see the crashes, I tried to create same test cases for deferent iOS and Xcode, and I don’t see the crashes in previous build. I started to get the crashes, only for iOS 14 operating systems and after using Xcode 12.  My function, where I think I have the crash, but I don't understand where exactly, because I didn't change nothing. Maybe something changed in Core Data? (NSMutableArray *)getObjectsforEntity:(NSString *)strEntity sortBy:(NSString *)strSort isAscending:(BOOL)ascending predicate:(NSPredicate *)predicate {     NSFetchRequest *fetchRequest = [[NSFetchRequest alloc] initWithEntityName:strEntity];     if (strSort) {         NSSortDescriptor *sort = [[NSSortDescriptor alloc] initWithKey:strSort ascending:ascending];         [fetchRequest setSortDescriptors:[NSArray arrayWithObject:sort]];     }     if (predicate) {         [fetchRequest setPredicate:predicate];     }     NSError *error;     NSMutableArray *result = [[[[self managedObjectContext] executeFetchRequest:fetchRequest error:&error] mutableCopy ]autorelease];     if (result == nil) {         return [[NSMutableArray alloc] init];     }     return result; } I tried to caught it and this is what I found: ==13048==ERROR: AddressSanitizer: allocator is out of memory trying to allocate 0x1a0 bytes ==13048==FATAL: AddressSanitizer: internal allocator is out of memory trying to allocate 0x50 bytes AddressSanitizer report breakpoint hit. Use 'thread info -s' to get extended information about the report. (lldb)  thread info -s thread #1: tid = 0x12fa63, 0x00000001041961f8 libclangrt.asaniosdynamic.dylib`asan::AsanDie(), queue = 'SQLQueue 0x16572e2c0 for MyApp.sqlite', stop reason = AddressSanitizer detected: out-of-memory {   "accesssize": 0,   "accesstype": 0,   "address": 0,   "description": "out-of-memory",   "instrumentationclass": "AddressSanitizer",   "pc": 0,   "stoptype": "fatalerror" } This is what I see in log: self RMNDatabaseManager * 0x164416210 0x0000000164416210 NSObject NSObject isa _unsafeunretained Class RMNDatabaseManager 0x000021a1019b6131 predicate NSPredicate * 0x2d7143b90 0x00000002d7143b90 NSObject NSObject predicateFlags struct predicateFlags evaluationBlocked unsigned int 0 reservedPredicateFlags unsigned int 0 reserved uint32t 0 fetchRequest NSFetchRequest * 0x2ce26f2d0 0x00000002ce26f2d0 NSPersistentStoreRequest NSPersistentStoreRequest NSObject NSObject isa unsafeunretained Class 0x61a1fb9ef989 0x000061a1fb9ef989 error NSError * domain: nil - code: 1287 0x0000000102957960 NSObject NSObject isa _unsafeunretained Class 0x102957880 0x0000000102957880 reserved void * 0x10295792c 0x000000010295792c code NSInteger 1287 domain NSString * 0x303 0x0000000000000303 NSObject NSObject isa unsafeunretained Class 0x0 userInfo NSDictionary * 0x20ff 0x00000000000020ff NSObject NSObject isa unsafeunretained Class 0x0 result NSMutableArray * 0x2d5131420 0x00000002d5131420 NSArray NSArray NSObject NSObject isa _unsafeunretained Class 0x154000452 0x0000000154000452 Crashlog  details:  [[Crashed: 0 CoreData 0x000000019d9fb6b8 PFObjectIDFastHash64 + 36 (NSBasicObjectID.m:707) 1 CoreData 0x000000019d9fb6b4 PFObjectIDFastHash64 + 32 (NSBasicObjectID.m:706) 2 CoreFoundation 0x0000000197c1c10c CFBasicHashRehash + 996 (CFBasicHash.c:477) 3 CoreFoundation 0x0000000197c1fdf4 CFBasicHashRemoveValue + 2352 (CFBasicHash.c:1386) 4 CoreFoundation 0x0000000197b3e2f8 CFDictionaryRemoveValue + 224 (CFDictionary.c:471) 5 CoreData 0x000000019d94b8e8 -[NSManagedObjectContext(NSInternalAdditions) forgetObject:propagateToObjectStore:removeFromRegistry:] + 120 (NSManagedObjectContext.m:5088) 6 CoreData 0x000000019d92b450 -[PFManagedObjectReferenceQueue processReferenceQueue:] + 864 (NSManagedObjectContext.m:5077) 7 CoreData 0x000000019da43578 90-[NSManagedObjectContext(NSInternalNotificationHandling) registerAsyncReferenceCallback]blockinvoke + 68 (NSManagedObjectContext.m:8825) 8 CoreData 0x000000019da39b18 developerSubmittedBlockToNSManagedObjectContextPerform + 156 (NSManagedObjectContext.m:3880) 9 libdispatch.dylib 0x000000019782b280 dispatchclientcallout + 16 (object.m:559) 10 libdispatch.dylib 0x00000001977d3fa8 dispatchlaneserialdrain$VARIANT$mp + 612 (inlineinternal.h:2548) 11 libdispatch.dylib 0x00000001977d4a84 dispatchlaneinvoke$VARIANT$mp + 424 (queue.c:3862) 12 libdispatch.dylib 0x00000001977de518 dispatchworkloopworkerthread + 712 (queue.c:6590) 13 libsystempthread.dylib 0x00000001dc7005a4 pthreadwqthread + 272 (pthread.c:2193) 14 libsystempthread.dylib 0x00000001dc703874 startwqthread + 8]]

Hello all. I am wondering if anyone has had issues running their WatchOS application on a real device from Xcode/knows a way around this. It is painful whenever I try to run my watchOS application on a real device. Most of the time it doesn't even run. The times it does successfully install and run on my device, it usually takes 5-15 minutes to finish. I didn't have these issues a couple of years ago on earlier versions of Xcode and WatchOS. This issue has only been occurring recently. Im using a MacBook Pro 2018, an Apple Watch Series 5, and Xcode 12 Beta 2 (I had the same issues on Xcode 11 too). Any help would be greatly appreciated. Thank you.

My issue is similar to: https://developer.apple.com/forums/thread/672939 Except on the software I wish to install my specific log message when I try to execute the command: "cmake .." The result is: " The output was: 1 ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libSystem.tbd' for architecture x86_64 clang-10: error: linker command failed with exit code 1 (use -v to see invocation) Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed. Compiler: /Users/ME/miniconda3/bin/x86_64-apple-darwin13.4.0-clang++ Build flags: -march=core2;-mtune=haswell;-mssse3;-ftree-vectorize;-fPIC;-fPIE;-fstack-protector-strong;-O2;-pipe;-stdlib=libc++;-fvisibility-inlines-hidden;-std=c++14;-fmessage-length=0;-isystem;/Users/ME/miniconda3/include Id flags: The output was: 1 ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libSystem.tbd' for architecture x86_64 clang-10: error: linker command failed with exit code 1 (use -v to see invocation) Detecting C compiler ABI info failed to compile with the following output: Change Dir: /Users/ME/Documents/Geant4/geant4.10.07.p02/examples/basic/B1/build/CMakeFiles/CMakeTmp "

clang: error: unable to execute command: Killed: 9 clang: error: clang frontend command failed due to signal (use -v to see invocation) Apple LLVM version 10.0.1 (clang-1001.0.46.4) Target: x86_64-apple-darwin18.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script. clang: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: /var/folders/81/7q0zzk113j7_tncvn69jv7v00000gn/T/dsu-cd7d8a.cpp clang: note: diagnostic msg: /var/folders/81/7q0zzk113j7_tncvn69jv7v00000gn/T/dsu-cd7d8a.sh clang: note: diagnostic msg: Crash backtrace is located in clang: note: diagnostic msg: /Users/pawangupta/Library/Logs/DiagnosticReports/clang__.crash clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash) clang: note: diagnostic msg: [Finished in 68.4s with exit code 254] [cmd: ['bash', '-c', "g++ -std=c++14 -Wall '/Users/pawangupta/Desktop/dsu.cpp' -o '/Users/pawangupta/Desktop/dsu' && '/Users/pawangupta/Desktop/dsu'"]] [dir: /Users/pawangupta/Desktop]

when I run my program this message appears

error testflight apple: no esta disponible por ahora intente mas tarde

Hi, When I launch my app via XCode on my own iPad, everything works fine. When I launch my app on an iPhone simulator, everything's fine too. But when I want to launch the app on my own iPhone, it stops at a white screen and this error is displayed in the console: dyld[345]: Symbol not found: _$s7SwiftUI14NavigationLinkV11destination5labelACyxq_Gq_yXE_xyXEtcfC  Referenced from: /private/var/containers/Bundle/Application/626260C6-064F-4468-A469-0027FCF41298/Tect.app/Tect   Expected in: /System/Library/Frameworks/SwiftUI.framework/SwiftUI Symbol not found: _$s7SwiftUI14NavigationLinkV11destination5labelACyxq_Gq_yXE_xyXEtcfC   Referenced from: /private/var/containers/Bundle/Application/626260C6-064F-4468-A469-0027FCF41298/Tect.app/Tect   Expected in: /System/Library/Frameworks/SwiftUI.framework/SwiftUI (lldb)  Does anybody know why this only occurs on my iPhone but not the other devices? And how do I fix it? Thanks in advance, Flex

Cannot Preview in this file- Landmark Crashed

I have written an app that returns an error in the terminal, the error is: nw_endpoint_handler_set_adaptive_write_handler [C114.1 104.16.101.13:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: ipsec5, ipv4, dns)] unregister notification for write_timeout failed, I notice this is given when it transits from one view to another through a NavigationView. I tried to isolate what causing this to give such errors but with no success. is this a bug in XCode because my app runs ok.

Showing Recent Messages Undefined symbol: OBJC_CLASS$_FIRAnalytics steps to reproduce create dynamic framework included firebase frameworks build framework success added dynamic framework in project trying to build but getting compilation errors

Hi I'm using Flutter to do an IOS app using Xcode. I'm currently using version 12.4 on my MacBook Pro mid 2012. When I try to run it on the IOS App simulator, I'm getting a long error message. here is a snippet of it Xcode's output: ↳     ld: warning: Could not find or use auto-linked library 'swiftSwiftOnoneSupport'     ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'     ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'     ld: warning: Could not find or use auto-linked library 'swiftCompatibility50'     ld: warning: Could not find or use auto-linked library 'swiftDarwin'     ld: warning: Could not find or use auto-linked library 'swiftUIKit'     ld: warning: Could not find or use auto-linked library 'swiftQuartzCore'     ld: warning: Could not find or use auto-linked library 'swiftCore'     ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'     ld: warning: Could not find or use auto-linked library 'swiftCompatibility51'     ld: warning: Could not find or use auto-linked library 'swiftFoundation'     ld: warning: Could not find or use auto-linked library 'swiftCoreImage'     ld: warning: Could not find or use auto-linked library 'swiftCompatibilityDynamicReplacements'     ld: warning: Could not find or use auto-linked library 'swiftMetal'     ld: warning: Could not find or use auto-linked library 'swiftDispatch'     ld: warning: Could not find or use auto-linked library 'swiftCoreMedia'     ld: warning: Could not find or use auto-linked library 'swiftCoreAudio'     Undefined symbols for architecture x86_64: Try doing research and think it might be linked to framework issue but not sure. Can anyone possibly advise? Thanks Eddie

When I enabled Thread Sanitizer runtime checking, my macOS app fails to build - despite compiling successfully when this diagnostic is disabled. I get several Uncategorized errors when compiling three Swift packages (AXSwift, Cryptor and Socket) that I have imported using SwiftPM. Uncategorized: Command CompileSwift failed with a nonzero exit code. Any ideas on what is going wrong? I'm on macOS Catalina 10.15.7 (19H2) using Xcode 11.3.1 (11C505).

I tried running a cpp programme straight from the terminal, then using VSCode, and finally from Eclipse's C++ extension, but I kept receiving the same issue. Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) These are all the things I have installed till now is which are needed for running cpp programs, I think ~ % c++ -v Apple clang version 12.0.5 (clang-1205.0.22.9) Target: x86_64-apple-darwin20.5.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin ~ % g++ -v                     Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1 Apple clang version 12.0.5 (clang-1205.0.22.9) Target: x86_64-apple-darwin20.5.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin ~ % make -v                    GNU Make 3.81 Copyright (C) 2006  Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-apple-darwin11.3.0 What should I do now? I can't program in cpp now anymore And can someone please suggest a IDE for C++ programs and not Xcode(because it takes up a lot of space)

Given: So there is this main app repo XYZ where TargetA is a target which contains an enum EnumB. Now there is another static library StaticLibC in a separate repository which contains a protocol ProtocolD. EnumB conforms to ProtocolD. When: let abc: ProtocolD = EnumB.some(...) The above line crashes with below error: Could not cast value of type 'TargetA.EnumB' to 'StaticLibC.ProtocolD' Can someone please help here ?

I downloaded Xcode 3 days ago and it ran fine until this evening; the app constantly hangs up and I am unable to work with it at all. People on the internet recommend disabling “connect via network” in Devices & Simulators” but the option to do so doesn't even show up for me. I have also tried reinstalling the application to no avail. I am also really concerned about how warm my device get's when running the app - the fans honestly sound like they the only thing preventing my computer from spontaneously combusting on the spot. If anyone has any suggestions, please, please let me know!