It appears that our users with iOS 15 are experiencing a crash as soon as the app enters the background. I can replicate this while debugging in Xcode simply by swiping to view to the home screen and waiting a few seconds. Message from debugger: Terminated due to signal 9 The logs don't appear to show an error in the apps code: Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0 Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001b7752564 mach_msg_trap + 8 1 libsystem_kernel.dylib 0x00000001b7752bfc mach_msg + 76 (mach_msg.c:119) 2 CoreFoundation 0x0000000180c7a698 __CFRunLoopServiceMachPort + 372 (CFRunLoop.c:2646) 3 CoreFoundation 0x0000000180c7e98c __CFRunLoopRun + 1212 (CFRunLoop.c:3000) 4 CoreFoundation 0x0000000180c923c8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 5 GraphicsServices 0x000000019c4a338c GSEventRunModal + 164 (GSEvent.c:2200) 6 UIKitCore 0x00000001836380bc -[UIApplication _run] + 1100 (UIApplication.m:3457) 7 UIKitCore 0x00000001833b5be8 UIApplicationMain + 2124 (UIApplication.m:5013) 8 VaultRE 0x0000000101b40600 0x100f10000 + 12781056 9 dyld 0x00000001024f5a24 start + 520 (dyldMain.cpp:876) Funnily enough, if I disable the Debug executable option from the schema I no longer experience this crash. How/If this relates to the compiled executable is unclear to me Any ideas? Regards

Hello, the following code behaves different in debug and release mode. The debug output is correct while in release mode it seems that there is no integer overflow and instead the value is calculated with a 64 bit value. @ Apple: can you confirm it? #include <iostream> #include <string> //------------------------------------------------------------------------ int main () { signed long long checkSum {14120563136728876}; int i = 23342251; std::string theString {"\\"}; // one ch is working, one is not // compare by using the first one or the second one // unsigned char ch {0b01011100}; // 92 unsigned char ch = theString[0]; // 92 checkSum += (int)ch * (i + 1); // different result in Debug and Release Mode std::cout << checkSum << "\n"; return 0; }

Does enabling or disabling bitcode would affect the existing features of the app in any way ? For eg: If I choose to untick the option "Rebuild from bitcode" while sharing the ipa to QA team and on the other hand If I chose to enable bitcode when I am uploading the app to AppStore. Is there any possibility that the some test cases might go live untested ?

I've got a decent size project with 10 or so dependencies. I've just switched to Xcode 11 and moved all the modules I can from using Carthage to the new SPM support in Xcode.One of my dependencies is https://github.com/iwasrobbed/Down.git a common markdown parser. It includes libcmark, a C library. After cleaning my build folder, the only module map is./SourcePackages/checkouts/Down/Source/cmark/include/module.modulemapThe first build works, but now find returns./SourcePackages/checkouts/Down/Source/cmark/include/module.modulemap ./Build/Intermediates.noindex/Down.build/Debug/libcmark.build/libcmark.modulemapAfter making a change to the source code and recompiling, the same two modulemaps are there, but I get the error/Users/mlilback/Library/Developer/Xcode/DerivedData/Rc2Client-bqmhvrpuhrtqjdfbdeqbqzhmotdc/Build/Intermediates.noindex/GeneratedModuleMaps/macosx/libcmark.modulemap:1:8: error: redefinition of module 'libcmark' module libcmark { ^ /Users/mlilback/Library/Developer/Xcode/DerivedData/Rc2Client-bqmhvrpuhrtqjdfbdeqbqzhmotdc/SourcePackages/checkouts/Down/Source/cmark/include/module.modulemap:1:8: note: previously defined here module libcmark [system][extern_c] { ^This makes no sense to me. Why does it compile the first time? What can I do to avoid constantly having to clean the build folder and wait for a fresh build?

In our project we use these flags: OTHER_SWIFT_FLAGS = "-driver-time-compilation -Xfrontend -debug-time-compilation -Xfrontend -debug-time-function-bodies -Xfrontend -debug-time-expression-type-checking"; After Xcode updating from 12.4 to 12.5.1 we started receiving error : <unknown>:0: error: unknown argument: '-debug-time-compilation' Command CompileSwift failed with a nonzero exit code What could be the problem?

In file included from /Users/xx/Desktop/xx/Pods/xx/xx/Classes/xx/Utils/xx/xx.mm:9: In file included from /Users/xx/Desktop/xx/Pods/xx/xx/Classes/xx/Utils/xx/xx.h:13: In file included from /Users/tang/Desktop/xx/Pods/Headers/Private/GPUImage/GPUImage.h:7: In file included from /Users/tang/Desktop/xx/Pods/Headers/Private/GPUImage/GPUImageVideoCamera.h:2: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVFoundation.h:23: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVFCapture.h:21: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVDepthData.h:11: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVCameraCalibrationData.h:12: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/simd/matrix_types.h:33: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/simd/vector_make.h:5310: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/c++/v1/tuple:149: /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/c++/v1/__tuple:24:1: error: templates must have C++ linkage template struct _LIBCPP_TEMPLATE_VIS tuple_size; ^~~~~~~~~~~~~~~~~~~~ In file included from /Users/tang/Desktop/xx/Pods/xx/xx/Classes/xx/Utils/xx/xx.mm:9: /Users/tang/Desktop/xx/Pods/xx/xx/Classes/xx/xx/xx/xx.h:11:1: note: extern "C" language linkage specification begins here extern "C" { ^ In file included from /Users/xx/Desktop/xx/Pods/xx/xx/Classes/xx/Utils/xx/xx.mm:9: In file included from /Users/tang/Desktop/xx/Pods/TempBase/TempBase/Classes/xx/Utils/xx/xx.h:13: In file included from /Users/tang/Desktop/xx/Pods/Headers/Private/GPUImage/GPUImage.h:7: In file included from /Users/tang/Desktop/xx/Pods/Headers/Private/GPUImage/GPUImageVideoCamera.h:2: In file included from /Users/xx/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVFoundation.h:23: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVFCapture.h:21: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVDepthData.h:11: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/System/Library/Frameworks/AVFoundation.framework/Headers/AVCameraCalibrationData.h:12: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/simd/matrix_types.h:33: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/simd/vector_make.h:5310: In file included from /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/c++/v1/tuple:149: /Users/tang/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/include/c++/v1/__tuple:27:1: error: templates must have C++ linkage template <class _Tp, class...>

I have a new warning per every target after upgrading to Xcode 11.4:Invalid debug info found, debug info will be strippedThis has never been the case for my code base before. Anything I can do to resolve these warning? Am I safe to release to the AppStore with these warnings? For one of the targets detailed info is:mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !137) #2, !dbg !203 label %138 double (i8*)* @"\01__hidden#1918_" !137 = !DILabel(scope: !138, name: "zulu_time", file: !10, line: 196) !138 = distinct !DISubprogram(name: "parseTimezone", scope: !10, file: !10, line: 161, type: !139, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !196) !203 = !DILocation(line: 196, column: 1, scope: !100, inlinedAt: !101) !100 = distinct !DISubprogram(name: "__hidden#1928_", scope: !10, file: !10, line: 161, type: !11, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !347), !dbg !371 label %55 i32 (i8*, ...)* @"\01__hidden#1920_" !347 = !DILabel(scope: !348, name: "end_getDigits", file: !10, line: 140) !348 = distinct !DISubprogram(name: "getDigits", scope: !10, file: !10, line: 109, type: !349, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !351) !371 = !DILocation(line: 140, column: 1, scope: !315) !315 = distinct !DISubprogram(name: "__hidden#1922_", scope: !10, file: !10, line: 109, type: !11, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) DICompileUnit not listed in llvm.dbg.cu !171 = distinct !DICompileUnit(language: DW_LANG_C99, file: !7, producer: "Apple clang version 11.0.3 (clang-1103.0.32.29)", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug, enums: !12, retainedTypes: !172, imports: !180, nameTableKind: None) ld: warning: Invalid debug info found, debug info will be stripped !dbg attachment points at wrong subprogram for function !126 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, s: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11) double (%0*, i8*, %0*, i32)* @"\01__hidden#2776_" br i1 %41, label %42, label %90, !dbg !152, !llvm.loop !155 !156 = !DILocation(line: 283, column: 3, scope: !157) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) ld: warning: Invalid debug info found, debug info will be stripped mismatched subprogram between llvm.dbg.label label and !dbg attachment

Hi All, I am facing the issue "No Such Module *******" This issue comes in every 3 to 4 weeks. It's always fixed after a 3 to 4-day long struggle but the same solution does not work for next time, which worked earlier, so there is no proper way to resolve this issue.

Hi, I've set the C++ language dialect in my project to c++2a. Than it failed on compiling .mm file which has the following line @import AppKit; But if replace it with the following line and link with framework from project build phases, than it works. #import <AppKit/AppKit.h> My .mm file is including for adapter swift header file (*-Swift.h) which is auto generated and has this @import directive. is it a known issue, should I file a bug ?

Hi,I created a static swift library, which I'm trying to use from another project. When trying to build the project where I added it as a dependency, I receive the following error:ld: library not found for -lswiftSwiftOnoneSupport for architecture x86_64Tried to fix it by setting ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to true. Did not help.Do you have any ideas? What other information should I provide?Thanks,Mark

Hi, I am trying to update our ECLiPSe CLP system for Mac OS X. I am using an iMac from 2010, with Mac OS X 10.12.6. Our system is multi-platform, and on the Mac, we build the system like on other Unix platforms, from a shell, and not directly in Xcode. I am having problems updating a C++ program. `g++ -dynamiclib ... -mmacosx-version-min=10.5 install_name,@rpath/seosiclpcbc.dylib ,,, -lgmp -o x86_64_macosx/seosiclpcbc.dylib ` (I have missed out some detail with ..., to shorten it) This links, but I get a warning `warning: [0mlibstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 [-Wdeprecated] ` When I change -mmacosx-version-min to 10.9, I get many undefined symbol errors like `Undefined symbols for architecture x86_64: "OsiClpSolverInterface::setColName(int, std::__1::basic_string<char, std::__1::cha\ r_traits<char>, std::__1::allocator<char> >)", referenced from:` It looks to me like the system is not linking in a C++ lib. I tried adding -lc++, but this does not help.Does anyone know what the problem is? Thanks in advance for any help! Kish Shen

Hi, When I use Xcode to build, It will generate xcactivitylog. But When I use xcodebuild, For example xcodebuild -workspace xx.xcworkspace -scheme xx -sdk iphoneos -showBuildTimingSummary -resultBundlePath ./a/a -derivedDataPath ./a clean build it will generate two xcactivitylog, One is a clean job log, and one is a build job log. But the build job log is not a valid gzip. I have to wait one day, but nothing changes. So, Is it possible to crash in generate xcactivitylog？ If I use hmap to replace the header search path, it works fine. So I think it may be argument too long lead to generating log failed. One more thing, it only failed in a large Xcode project.