My test flight application crashed while doing a disk writing operation. I saw the following error in crash log
1073.76 MB of file backed memory dirtied over 705 seconds (1522.14 KB per second average), exceeding limit of 12.43 KB per second over 86400 seconds\
After a little bit of research I found from Apple documentation that System will throw an exception if disk writes from the app exceeds a certain limit in 24 hours window
[https://developer.apple.com/documentation/xcode/reducing-disk-writes)
But the threshold is not documented. But looking at the crash log we can reverse calculate this threshold as 12.43KB * 86400 ~ 1 GB
Does this means that iOS application won't be able to write data more than this limit (1 GB) per day?
Organizer Window
RSS for tagUpload apps and view performance metrics and diagnostics in the Organizer window in Xcode.
Posts under Organizer Window tag
63 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
The latest build of my iOS app in TestFlight does not show a "Download DSYM" link in the build metadata tab. When I uploaded the build to App Store Connect I had "enable bitcode" turned on, and I can see "Include Symbols" is set to yes in the build metadata. But no link is next to it like my other recent builds.
The last few builds I've submitted in the same manner have all generated the DSYM download links no problem. For some reason this particular build has not.
Has anyone else experienced this same issue? Any tips of how to fix this? I'd like to avoid submitting a new build if possible
Cheers
I'm getting this error when trying to distribute/validate my app (every version of it):
I have a developer account and a distribution certificate, and have had no problems uploading many versions of my app until today.
Has anyone experienced this before?
General:
DevForums tags: Debugging, LLDB, Graphical Debugger
Xcode > Debugging documentation
Diagnosing memory, thread, and crash issues early documentation
Diagnosing issues using crash reports and device logs documentation
Choosing a Network Debugging Tool documentation
Testing a release build documentation
Isolating Code Signing Problems from Build Problems DevForums post
What is an exception? DevForums post
Language Exception from RCTFatal DevForums post
Standard Memory Debugging Tools DevForums post
Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem DevForums post
Posting a Crash Report DevForums post
Implementing Your Own Crash Reporter DevForums post
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
I am trying to archive xcode build in network drive(file share). But we unable to archive xcode build.
Note: Same xcode build works fine in mac disk instead of network drive. I am very curious about why we facing issue if we use network drive
Xcode version: V13.2
Can someone tell me It is possible to archive xcode build in network drive instead of Mac disk?
Getting issue in. uploading build from Xcode 14.1. My OS is Ventura 13.0.
I am getting following error wile uploading app.
Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion in Corey Health [Payload/Corey.app]. (ID: 9726552c-a8a0-4e23-aec7-a5e20ac2ce1f).
Please help
After creating a basic table the application crashed while running a select query.
Translated Report (Full Report Below)
Process: MySQLWorkbench [1687]
Path: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier: com.oracle.workbench.MySQLWorkbench
Version: 8.0.32.CE (1)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-02-02 11:58:46.6293 +0530
OS Version: macOS 13.2 (22D49)
Report Version: 12
Anonymous UUID: 7B20408B-A4BE-478D-8402-4595E3D3D9C4
Time Awake Since Boot: 880 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [1687]
Application Specific Backtrace 0:
0 CoreFoundation 0x00007ff8141d3cb3 __exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007ff813d2210a objc_exception_throw + 48
2 CoreFoundation 0x00007ff81426abbe -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x00007ff81413eab0 forwarding + 1324
4 CoreFoundation 0x00007ff81413e4f8 _CF_forwarding_prep_0 + 120
5 WBExtras 0x0000000109c371a1 -[MResultsetViewer tableView:willDisplayCell:forTableColumn:row:] + 393
6 AppKit 0x00007ff81753282e -[NSTableView _delegateWillDisplayCell:forColumn:row:] + 104
7 AppKit 0x00007ff817477676 -[NSTableView preparedCellAtColumn:row:] + 1835
8 MySQLWorkbench 0x0000000100bdfa98 -[MGridView preparedCellAtColumn:row:] + 54
9 AppKit 0x00007ff817476e41 -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 42
10 AppKit 0x00007ff817476ac1 -[NSTableView drawRow:clipRect:] + 1638
11 AppKit 0x00007ff81747613c -[NSTableView drawRowIndexes:clipRect:] + 707
12 AppKit 0x00007ff817401cc4 -[NSTableView drawRect:] + 1670
13 AppKit 0x00007ff817334144 _NSViewDrawRect + 121
14 AppKit 0x00007ff817b193c3 -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1810
15 AppKit 0x00007ff817333870 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 753
16 QuartzCore 0x00007ff81c16db59 CABackingStoreUpdate_ + 254
17 QuartzCore 0x00007ff81c1d13c1 ___ZN2CA5Layer8display_Ev_block_invoke + 53
18 QuartzCore 0x00007ff81c16cd66 -[CALayer _display] + 2275
19 AppKit 0x00007ff8173334c5 -[_NSBackingLayer display] + 462
20 AppKit 0x00007ff8172ab455 -[_NSViewBackingLayer display] + 554
21 QuartzCore 0x00007ff81c16bd08 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 900
22 QuartzCore 0x00007ff81c2e56c6 _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 648
23 QuartzCore 0x00007ff81c14cb35 _ZN2CA11Transaction6commitEv + 725
24 AppKit 0x00007ff81734496f __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
25 AppKit 0x00007ff817b5c767 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
26 CoreFoundation 0x00007ff81415b3e1 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
27 CoreFoundation 0x00007ff81415b309 __CFRunLoopDoObservers + 482
28 CoreFoundation 0x00007ff81415a866 __CFRunLoopRun + 877
29 CoreFoundation 0x00007ff814159e7f CFRunLoopRunSpecific + 560
30 HIToolbox 0x00007ff81dfec766 RunCurrentEventLoopInMode + 292
31 HIToolbox 0x00007ff81dfec576 ReceiveNextEventCommon + 679
32 HIToolbox 0x00007ff81dfec2b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
33 AppKit 0x00007ff8171e5293 _DPSNextEvent + 909
34 AppKit 0x00007ff8171e4114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
35 AppKit 0x00007ff8171d6757 -[NSApplication run] + 586
36 AppKit 0x00007ff8171aa797 NSApplicationMain + 817
37 dyld 0x0000000200ff6310 start + 2432
Kernel Triage:
VM - pmap_enter retried due to resource shortage
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AppKit 0x7ff81754dc26 -[NSApplication _crashOnException:] + 287
1 AppKit 0x7ff817344bab __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 857
2 AppKit 0x7ff817b5c767 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
3 CoreFoundation 0x7ff81415b3e1 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
4 CoreFoundation 0x7ff81415b309 __CFRunLoopDoObservers + 482
5 CoreFoundation 0x7ff81415a866 __CFRunLoopRun + 877
6 CoreFoundation 0x7ff814159e7f CFRunLoopRunSpecific + 560
7 HIToolbox 0x7ff81dfec766 RunCurrentEventLoopInMode + 292
8 HIToolbox 0x7ff81dfec576 ReceiveNextEventCommon + 679
9 HIToolbox 0x7ff81dfec2b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
10 AppKit 0x7ff8171e5293 _DPSNextEvent + 909
11 AppKit 0x7ff8171e4114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
12 AppKit 0x7ff8171d6757 -[NSApplication run] + 586
13 AppKit 0x7ff8171aa797 NSApplicationMain + 817
14 dyld 0x200ff6310 start + 2432
Thread 1:: com.apple.rosetta.exceptionserver
0 runtime 0x7ff7ffc73614 0x7ff7ffc6f000 + 17940
1 runtime 0x7ff7ffc7f530 0x7ff7ffc6f000 + 66864
2 runtime 0x7ff7ffc80f30 0x7ff7ffc6f000 + 73520
Thread 2:
0 runtime 0x7ff7ffc9187c 0x7ff7ffc6f000 + 141436
Hi!
We've recently released an usual app-update, but suddenly got a bunch of crashes in App Store Connect and almost none in Firebase Crashlytics.
According to customer support, for some users the app insta-crashes. A white screen appears for a flash and then they're returned to the home screen. The app always insta-crashes, only a reinstall fixes it.
It makes sense while Crashlytics isn't reporting any crashes, because it doesn't even get a chance to run and upload the crash reports to their server.
The Xcode organizer does show a bunch of crashes, but with no stack trace. It just says MyApp: NO_CRASH_STACK. Looking at the explicit 'xccrashpoint' in Finder reveals a couple of crash reports, that I've attached, but they're not that useful.
As far as I can tell, the app crashes while it's trying to load the Swift core, that's embedded in the app, but I'm not sure why that would cause a crash. Maybe it was supposed to use the library embedded in iOS (/usr/lib/swift/libswiftCore.dylib)?
Any help would be greatly appreciated 🍺!
report.crash
I have move to an M2 sillicon, was on 14.3 downgraded to 14.2 as I saw on other posts, but i cannot archive either with xcode or fastlane my project I get :
error: Could not complete submission of dSYM at /Users/me/Library/Developer/Xcode/DerivedData/MyApp-dgiquvsgpvkjfjcvhtcnrnpbekbj/Build/Intermediates.noindex/ArchiveIntermediates/HangersPro/BuildProductsPath/Release-iphoneos/MyApp.app.dSYM: Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=2 "File no longer exists at (null)" UserInfo={NSLocalizedFailureReason=File no longer exists at (null)}
... i ve been stuck for 3 weeks this is really hurting my business we cannot deploy since. any one has alternative idea ?
Hello All,
I am stuck in this error for a week. I tried reinstalling Xcode 14.1, adding '-f' in frameworks.sh but neither worked. Below is the error. I would really appreciate if you can help.
Also, build gets succeeded and also I can run the app on the simulator, but I cannot archive it.
Error
PhaseScriptExecution [CP]\ Embed\ Pods\ Frameworks /Users/dhiralpanjwani/Library/Developer/Xcode/DerivedData/Lupus_Decision_Aid-haxtkzwojyytuwedvxiexocoohxi/Build/Intermediates.noindex/ArchiveIntermediates/Lupus\ Decision\ Aid/IntermediateBuildFilesPath/Lupus\ Decision\ Aid.build/Release-iphoneos/Lupus\ Decision\ Aid.build/Script-570BD887603D2E782013C015.sh (in target 'Lupus Decision Aid' from project 'Lupus Decision Aid')
cd /Users/dhiralpanjwani/Downloads/iOS/Lupus\ Decision\ Aid\ copy
/bin/sh -c /Users/dhiralpanjwani/Library/Developer/Xcode/DerivedData/Lupus_Decision_Aid-haxtkzwojyytuwedvxiexocoohxi/Build/Intermediates.noindex/ArchiveIntermediates/Lupus\\ Decision\\ Aid/IntermediateBuildFilesPath/Lupus\\ Decision\\ Aid.build/Release-iphoneos/Lupus\\ Decision\\ Aid.build/Script-570BD887603D2E782013C015.sh
mkdir -p /Users/dhiralpanjwani/Library/Developer/Xcode/DerivedData/Lupus_Decision_Aid-haxtkzwojyytuwedvxiexocoohxi/Build/Intermediates.noindex/ArchiveIntermediates/Lupus Decision Aid/BuildProductsPath/Release-iphoneos/Lupus Decision Aid.app/Frameworks
/Users/dhiralpanjwani/Downloads/iOS/Lupus Decision Aid copy/Pods/Target Support Files/Pods-Lupus Decision Aid/Pods-Lupus Decision Aid-frameworks.sh: line 43: source: unbound variable
Command PhaseScriptExecution failed with a nonzero exit code
I am trying to get crash logs.
organizer is showing "Downloading... " indefinitely.
Internet connection is fine.
Xcode Organizer:
My build version is 25933, I could not show this info because appstoreconnect website and App Store history version did no show build version, I am pretty sure the build version is 25933.
Hello, I have uploaded archives successfully on Appstoreconnect from xcode14. But in TestFlight I am not able to see archive. I have update info plist with App Uses Non-Exempt Encryption and set value NO. But still facing issue. Please help me how I can resolve this issue ?
xcode→Archive
→result
his bundle is invalid. The value of the CFBundleDocumentTypes key in the Info.plist must be an array of dictionaries, with each dictionary containing at least the CFBundleTypeName key. (ID: (something))
My Xcode versions 14
What do I this error?
(I'm a Japanese.I'm sorry that it was hard to understand.)
Hi,
I'm writing here in order to make sense of how Xcode Organizer Crashes Report works.
In particular, I'm experiencing strange behaviors when I switch among filters (date, version, builds, etc.):
if I select, for example, "Last Two Weeks" filter, the latest version of the app, "All Builds" and "App Store", I see additional crashes (new crash entries) compared to using a specific build (we just have one single build for that version that is published in the App Store). I'm noticing the same behavior when, for example, I select "App Store or Test Flight" filter without selecting the specific build ("All Builds" is set).
furthermore, I would like to know if a crash that is reported in a previous version will be available in the latest one if not fixed or not experienced anymore by users.
Waiting for a reply I thank you for your feedback.
All the best,
Lorenzo
Hi,
In XCode organizer, under reports section, Crashes info shows fine with call stacks but Disk writes, Energy and Hang reports sections are broken recently. When I try to access any of these sections it says "The operation couldn't be completed. ((extension in DVT Products):....[Attached error screenshot]"
How to fix this error and get the reports under Disk writes, Energy and Hang reports section?
Regards,
Eshwar
We are able to see crashes in TestFlight, as well as AppHangs in our error analytics tool - Sentry.
But when trying to see the same in XCode Organizer, it shows an empty list.
How do we fix this?
Hi, developers
I've been wasting several days with upload failure issues since upgrading to Xcode 15. I would like to ask for advice from those with experience.
I upload the archive using auto signing as usual, but after printing the phrase "Waiting for App Store Connect SPI analysis responses...", the following Asset Validation Failed error occurs.
It seemed like a code signing issue, so I deleted all the certs and recreated them, and tried signing them manually, but none of them worked. I'm going crazy. Please help.
I recently updated to Xcode 15.0 and seem to be encountering permissions related errors after using the Replace Container function to replace an app container. Similarly, editing the current run scheme and choosing a new App Data container fails with an identical error.
It seems like the Documents directory and other similar directories are blocked from being able to write. Here is an example of what appears in the log after replacing the container:
Failed to create directory /var/mobile/Containers/Data/Application/A3C32E7A-34F3-4C69-B037-478027F2A4AC/Library/Preferences because of 13.
Couldn't write values for keys (
"/google/measurement/app_instance_id"
) in CFPrefsPlistSource<0x280a82760> (Domain: com.google.gmp.measurement, User: kCFPreferencesCurrentUser, ByHost: No, Container: (null), Contents Need Refresh: No): Directory needed
os_unix.c:47395: (13) lstat(/private/var/mobile/Containers/Data/Application/A3C32E7A-34F3-4C69-B037-478027F2A4AC/Documents)
- Permission denied os_unix.c:47395: (13) lstat(/private/var/mobile/Containers/Data/Application/A3C32E7A-34F3-4C69-B037-478027F2A4AC/Documents/<redacted>.sqlite)
- Permission denied os_unix.c:46898: (13) statfs(/private/var/mobile/Containers/Data/Application/A3C32E7A-34F3-4C69-B037-478027F2A4AC/Documents/<redacted>.sqlite)
- Permission denied
Steps to reproduce:
Create a new app and replace -viewDidLoad: with the following. This will write a string to a new file and read that string:
NSFileManager * const fileManager = [NSFileManager defaultManager];
NSURL * const documentsDirectoryURL = [[fileManager URLsForDirectory:NSDocumentDirectory inDomains:NSUserDomainMask] lastObject];
if (!documentsDirectoryURL) {
[NSException raise:@"DocumentsDirectoryException" format:@"Application documents directory URL is nil"];
}
NSURL * const fileURL = [documentsDirectoryURL URLByAppendingPathComponent:@"test.txt"];
if ([fileManager fileExistsAtPath:[fileURL path]]) {
NSError *error;
if (![[NSFileManager defaultManager] removeItemAtPath:[fileURL path] error:&error]) {
[NSException raise:@"DocumentsDirectoryException" format:@"Encountered error removing file: %@",error];
}
}
NSString * const fileContents = [NSString stringWithFormat:@"Date: %@",[NSDate date]];
NSError *error;
if (![[fileContents dataUsingEncoding:NSUTF8StringEncoding] writeToURL:fileURL options:0 error:&error]) {
[NSException raise:@"DocumentsDirectoryException" format:@"Encountered error writing to file: %@",error];
}
NSString * const writtenFileContents = [[NSString alloc] initWithData:[NSData dataWithContentsOfURL:fileURL] encoding:NSUTF8StringEncoding];
NSLog(@"Written file contents: %@", writtenFileContents);
Run the app and observe the log message "Written file contents: ..."
Save the app container via Window > Devices & Simulators by clicking the app, clicking the "(...)" button, and then clicking "Download Container..."
Use the same procedure in step 3 but instead, click "Replace Container..." and choose the existing app container that was downloaded
Run the app again and observe that it fails with the following exception message:
*** Terminating app due to uncaught exception 'DocumentsDirectoryException', reason: 'Encountered error writing to file: Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “test.txt” in the folder “Documents”." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/CF1E09C8-7BE2-4D87-8AD2-648AFBE038A5/Documents/test.txt, NSUnderlyingError=0x2831d4d50 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}'
Is anyone else encountering this issue and can confirm? Are my next steps to create a bug report? Is there a manner to escalating the bug report? This is a pretty core piece of functionality for QA and testing apps.
So I've been working on a React Native App recently using Expo. Before the official release of XCode 15 and iOS 17, I had a janky workaround where I would archive the app in XCode 15 and then deploy it in XCode 14. Or maybe it was the other way around.
But now I can't find any way to deploy my IPA to my iPhone for local testing. The app runs just fine when running locally. The steps that I'm currently going through are as follows:
npx expo prebuild --platform ios --clean
npx pod-install
Open the [App].xcworkspace (XCode 15)
Choose my signing team (Why do I have to do this every time?)
Menu > Product > Archive (Succeeds!)
Open the Organizer (Windows > Organizer)
Run Validate (Just because I'd expect this to catch any errors) (Succeeds!)
Distribute App > Debugging (I've tried Release Testing too)
Open Devices
My iPhone > Installed Apps > + > (The new build's IPA)
And the output is always some variant pretty close to what's copied below. I'm sort of at my wits end here. Anyone got any insight or advice? Thanks!
Error installing '/Users/[path]/app.ipa', ERROR: Error Domain=com.apple.dt.CoreDeviceError Code=3002 "Failed to install the app on the device." UserInfo={NSURL=file:///Users/[path]/[App].ipa, NSLocalizedDescription=Failed to install the app on the device., NSUnderlyingError=0x60000e28aaf0 {Error Domain=com.apple.dt.CoreDeviceError Code=3000 "The item at [App].ipa is not a valid bundle." UserInfo={NSURL=file:///[Path]/[App].ipa, NSLocalizedFailureReason=Failed to read the bundle., NSLocalizedDescription=The item at [App].ipa is not a valid bundle.}}}