Post not yet marked as solved
I'm trying to debug a couple of crash reports for a Mac Catalyst app and seem to be unable to symbolicate my crash reports. In the Xcode Organizer, I see unsymbolicated lines for my app, despite having the original archive for the build in question. A search for the relevant dSYM (using the process from https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Locate-a-dSYM-Using-Spotlight) yields no results.
Unlike iOS builds, the "Download dSYMs" button isn't present in the organizer, nor is the option to download dSYMs from App Store Connect. I assume this is because macOS apps don't use bitcode.
The app's Debug Information Format is set to DWARF with dSYM File.
Has anyone else run into this issue? Any ideas about how I can symbolicate the crash logs?
Post not yet marked as solved
Dear Apple Apple Engineer:
An exception has occurred in my application.
Here is the crash report：
42183A4C-7A9C-36F9-B29A-A28577CE39B7 0x0000000100ecc000 caused by:Application received signal 5 callStackSymbols: { 0 libdispatch.dylib 0x000000018888c768 0x0000000188853000 + 235368 1 libdispatch.dylib 0x0000000188858344 0x0000000188853000 + 21316 2 libdispatch.dylib 0x00000001888564b4 0x0000000188853000 + 13492 3 iIndustrial 0x00000001031cb09c 0x0000000100ecc000 + 36696220 4 libobjc.A.dylib 0x000000019d79fcd8 0x000000019d79a000 + 23768 5 libobjc.A.dylib 0x000000019d7b7148 0x000000019d79a000 + 119112 6 libobjc.A.dylib 0x000000019d7be5c4 0x000000019d79a000 + 148932 7 libsystem_blocks.dylib 0x00000001d48c1764 0x00000001d48c0000 + 5988 8 libdispatch.dylib 0x000000018885781c 0x0000000188853000 + 18460 9 libdispatch.dylib 0x000000018885a968 0x0000000188853000 + 31080 10 libdispatch.dylib 0x0000000188868fe0 0x0000000188853000 + 90080 11 libdispatch.dylib 0x00000001888697d8 0x0000000188853000 + 92120 12 libsystem_pthread.dylib 0x00000001d492e768 0x00000001d492b000 + 14184 }
This is my crash func,
- (GMRZUACStatus)FPCodeConvertUACCode:(FidoStatus)status
{
GMRZUACStatus retStatus = GMRZUACStatus_FAILED;
switch (status) {
case SUCCESS:
retStatus = GMRZUACStatus_SUCCESS;
break;
case FAILURE:
retStatus = GMRZUACStatus_FAILED;
break;
case CANCELED:
retStatus = GMRZUACStatus_CANCELED;
break;
case NO_MATCH:
retStatus = GMRZUACStatus_NO_MATCH;
break;
case PROTOCOL_ERROR:
retStatus = GMRZUACStatus_PROTOCOL_ERROR;
break;
case BIOIDINVALID:
retStatus = GMRZUACStatus_BIOID_INVALID;
break;
case BIOID_HAS_CHANGED:
retStatus = GMRZUACStatus_BIOID_CHANGED;
break;
case CURRENT_BIO_NOT_AVAILABLE:
retStatus = GMRZUACStatus_BIOID_NOT_AVAILABLE;
break;
case WAIT_USER_ACTION:
retStatus = GMRZUACStatus_WAIT_USER_ACTION;
break;
case UNKNOWN_ERROR:
retStatus = GMRZUACStatus_UNKNOWN_ERROR;
break;
case USER_REGISTED:
retStatus = GMRZUACStatus_USER_REGISTED;
break;
case TOUCHID_NOT_SUPPORT:
retStatus = GMRZUACStatus_TOUCHID_NOT_SUPPORT;
break;
case FACEID_NOT_SUPPORT:
retStatus = GMRZUACStatus_FACEID_NOT_SUPPORT;
break;
case FACEID_NOT_PERMISSION:
retStatus = GMRZUACStatus_FACEID_NOT_PERMISSION;
break;
default:
break;
}
return retStatus;
}
I don't know why this method is broken, can you help me？
Best wishes
I'm trying to upload my MacOS app to Appstore via command line, and after solving some signing and certificates issues, I'm a bit stuck on package validation.
After exporting the archive to a .pkg file, I run the following command:
xcrun altool --validate-app -f ${filename}.pkg -t macOS -u $username -p $password --output-format json
And then I get a message with this feedback:
Could not find the main bundle or the Info.plist is missing a CFBundleIdentifier in ‘MyApp.pkg’.
The problem is my Info.plist looks valid, and it does have a CFBundleIdentifier key. Besides that, uploading to Appstore through Xcode organizer works fine, so I don't really know what I'm missing here.
So, I have the following doubts:
Am I in the right direction to upload the app to the store via command line?
Do I really needs this --validate-app step?
Is it correct to try to validate a pkg file?
Please let me know if there is more information I could give.
Any help would be appreciated.
Post not yet marked as solved
Is there a simple way to convert the 'new-style' JSON crash report into a human readable format through Terminal? Similar to how viewing it directly in Xcode or Console reverts it to the old-format.
I want to update my automation scripts to utilize the new CrashSymbolicator.py utility, but I'm having trouble easily reading its output.
Hi,
on my macOS app I would like to set the window background color as the titlebar background color such a way to get a unique color all over the window on both light and dark mode.
But I cannot find the way to read the titlebar background color nor I found a standard color name for that. How can I do that?
Post not yet marked as solved
Hello team ,
I have react native app, its countinuosly rejected by apple team in review by specifing , its crashes.
I have tested the app on many real devices using test flight and also on simulators. Even I have tested on the same device and version that was speified in the crash reason.
Please suggest any solution because i cant able to regenrate the crash in the app that was provided by the apple.
Attached crash report by apple.
attachment.crashlog-7423E0D4-45B1-4E6B-92D7-C853EE9BD006.txt
Post not yet marked as solved
Xcode Version 13.3.1 (13E500a)
I was distributing my flutter app for TestFlight and this message came out, saying Error Analyzing App Version, without providing any details.
Here's the last part of the logs that I've gotten from "Show Logs", but I can't find any useful message from it.
"1.2.840.113635.100.6.1.12",
"1.2.840.113635.100.6.1.2"
), issueDate='2022-01-25 01:01:09 +0000''> for <DVTFilePath:0x7fbd220ebc70:'/Users/chan/Library/Developer/Xcode/Archives/2022-05-10/Runner 10-05-2022, 5.16 PM.xcarchive/Products/Applications/Runner.app/Frameworks/video_player_avfoundation.framework'>
2022-05-10 09:26:35 +0000 App Store Connect request for store configuration response: <DVTITunesConnectConfigurationResponse: 0x7fbd610319a0; isSuccessful='1', configuration='{
WPYRSFU994 = {
"com.apple.platform.appletvos" = {
architectures = {
defaultArch = {
defaultProductType = {
format = {
bitCode = {
supportLevel = required;
};
compiledCode = {
supportLevel = deprecated;
};
};
};
};
};
iconSource = {
largeAppIcon = carInBinary;
primaryIcons = carInBinary;
};
onDemandResources = {
sizeLimits = {
assetPack = 512000000;
total = 20000000000;
};
supportLevel = supported;
};
};
"com.apple.platform.iphoneos" = {
architectures = {
defaultArch = {
defaultProductType = {
format = {
bitCode = {
supportLevel = supported;
};
compiledCode = {
supportLevel = deprecated;
};
};
};
};
};
iconSource = {
largeAppIcon = unsupported;
primaryIcons = pngInBinary;
};
onDemandResources = {
sizeLimits = {
assetPack = 512000000;
total = 20000000000;
};
supportLevel = supported;
};
};
"com.apple.platform.macosx" = {
architectures = {
defaultArch = {
defaultProductType = {
format = {
bitCode = {
supportLevel = unsupported;
};
compiledCode = {
supportLevel = required;
};
};
};
};
};
iconSource = {
largeAppIcon = pngInBinary;
primaryIcons = pngInBinary;
};
onDemandResources = {
supportLevel = unsupported;
};
};
"com.apple.platform.watchos" = {
architectures = {
defaultArch = {
defaultProductType = {
format = {
bitCode = {
supportLevel = required;
};
compiledCode = {
supportLevel = deprecated;
};
};
};
};
};
iconSource = {
largeAppIcon = unsupported;
primaryIcons = pngInBinary;
};
onDemandResources = {
supportLevel = unsupported;
};
};
configModelVersion = "1.1";
};
preflight = (
WPYRSFU994
);
}', alertMessage='(null)', errors='(
)', warnings='(
)', infoMessages='(
)'>
2022-05-10 09:26:35 +0000 App Store Connect team IDs for account karhoong@the-oaks.my are (
WPYRSFU994
)
I am trying to upload my app to AppStore using Xcode. The app uses widgets, and after archiving the app, I run the validation. It reports two errors.
Invalid directory. The bundle Payload/……/…WidgetExtension.appex is not contained in a correctly named directory. It should be under "Plugins".
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value '…widget' under the iOS application.
I suspect that the two are linked issues, and that whilst trying to debug the widget in a simulator I may have duplicated any entry somewhere in the settings, but I am not clear where to look, as widget appears in several places, to fix the issue - info.plist, Build settings, General tab, other?
The widget also appears in the 'Products' list along with the app. I am not sure if the widget should be there, and if not how to remove it from the 'Products' list, but still make it available in the app.
Post not yet marked as solved
Hey there,
My XCode project keeps crashing (I'm still learning how to use it, literally crashes after I make the simulator run a text on the screen).
It just says my mac isn't compatible with the program.
I tried everything: I have downloaded the XCode version that's compatible with my Mac, I updated the Mac to the latest version, reinstalled XCode, deleted the project, and started a new one. I don't know what I should do by now.
I have a project to hand in late May and I need it to run :(
Please help!!
Post not yet marked as solved
I created a new app in the App Store and when i upload a new build it doesnt appear in the testFlight tab (see image).
But when i tried to upload the same bundle it shows me an error that a bundle was allready uploaded.
Post not yet marked as solved
I am a Window user, I don't have MacOS. So to participate in the challenge, which tool (IDE, etc) is recommended for Window to build the app? Thanks!
Post not yet marked as solved
Hello,
I'm investigating a crash where keyWindow is nil when I don't expect it to be nil.
I would like to understand when this can happen. Indeed,I could make a fix by guarding for nil values, but this would lead to an invalid state.
Context
We want to return quickly from application(didFinishLaunchingWithOptions:), so:
We set a view controller as a splash screen rootViewController => we mark the window with makeKeyAndVisible().
We queue initializations asynchronously on the main queue.
=> Basically, while the app is initializing starting, we're displaying a splash screen view controller.
When the app is done initializing, it needs to present the actual UI. A last asynchronous task on the main queue does this. We get keyWindow from UIApplication to set the new view controller with the actual UI. That's where we assume that it shouldn't be nil and force-unwrap it, but alas, in some instances it's nil.
Misc
This crash only happens when app built with Xcode 13.x, running on iOS 15.
I cannot reproduce this bug, and it has fairly little occurrence. (100s over 100000 of sessions)
I also attached a sample crash
Questions
Given that I made the window "key and visible" in step 1, what could cause the window to stop becoming "key".
What would be the correct way to get the window to set the new root view controller ?
I don't really want to guard against a nil value because then it means that I wouldn't be able to set my new rootViewController and the app would be stuck on the launch screen.
2021-12-01_18-16-29.7629_-0700-9b5855582b13262f154acae64dd3140ad49c84f3.crash
Thanks a lot!
Bruno
Post not yet marked as solved
I spent many hours to figure out why my app is now other item not the iOS app
you will see the Distribute Content instead of Distribute App
Version and Identifier are now gone
I test it on Xcode 13.3
the last archive you will see in the image is the one that Creation Date is 3 Apr 2022 17:55
I try to build with the previous version (Xcode 13.2.1)
The error appears Package.resolved file is corrupted or malformed
I delete the Package.resolved
Then the error is gone
I try to archive again and it works
Creation Date is 3 Apr 2022 18:30
The problem seems to occur when using an older Xcode project opened with the current version of Xcode (13.3).
Post not yet marked as solved
sudo python3 /Applications/Xcode.app/Contents/SharedFrameworks/CoreSymbolicationDT.framework/Versions/A/Resources/CrashSymbolicator.py 38.json -d 38.app.dSYM -o result.txt
Run this command, i got the error: Crash log is missing bug_type field. Stopping symbolication.
Thanks.
Post not yet marked as solved
I have tried everything. Unplug, plug, connect, forget connection, resetting iPhone, re-installing Xcode.
Tried everything listed in this stack overflow question
Let it alone for 24 hours and nothing.
Tried with an Iphone se 2020 and it runs perfectly, but on my iPhone 7 nothing happens besides being stuck on "making iPhone ready for development"
Ios version = 15.4
Xcode version = 13.3
Mac version = monterey 12.3
Notes:
On Xcode it shows 2 equal messages "Making iPhone de Gustavo ready for development" every time that I connect
iPhone 7 doesn't show "developer" option on settings, but iPhone SE shows.
Stack overflow question
Post not yet marked as solved
This is a Unity APP that uses the Apple Lidar camera to record 3D Human movement. Was looking for an extra set of eyes to review the logs.
When running the App we have about 300 MB of free memory on the IPAD Pro 8 GB. The Crash logs are consistent. Is this a memory resource issue? Could we extend the memory to beyond 5 GB to help with this issue?
Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000104 x1: 0x0000000000000000 x2: 0x0000000000008400 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x00000000000000a0 x6: 0x0000000000000000 x7: 0x0000000000000000
x8: 0x000000016f064098 x9: 0x0000000000008401 x10: 0x0000000130421820 x11: 0x0000000000000002
x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000001
x16: 0x0000000000000131 x17: 0x0000000000000000 x18: 0x000000013dd2486c x19: 0x0000000130421808
x20: 0x0000000130421848 x21: 0x00000001010b4660 x22: 0x0000000000000000 x23: 0x0000000000000000
x24: 0x0000000000008400 x25: 0x0000000000008401 x26: 0x0000000000008500 x27: 0x00000000000003e8
x28: 0x00000000000f4240 fp: 0x000000016f064110 lr: 0x00000001f2e3a254
sp: 0x000000016f064080 pc: 0x00000001b973df90 cpsr: 0x60001000
esr: 0x56000080 Address size fault
crashlog.crash
Post not yet marked as solved
Currently working on a project these past couple of days but today when I opened Xcode and selected my project it would not display my stimulater phone and would keep refreshing showing the last successful build was sometime yesterday.
Post not yet marked as solved
When an application is frequently killed and restarted, it may crash without display its launchScreen page. This situation only exit on iOS 15 or above system device.
I have try to delete all the code but the appDelegate, only show "Hello World" in a blank viewController. But the app still crash again.
The probability of this situation is not hight, maybe once in a dozen, maybe happen every few times.
Anybody can help me solve this problem, many thanks!
Post not yet marked as solved
I am getting this crash from crash report some times "pmap_enter failed with resource shortage". and there's no description about error.
It happens on main with "SIGKILL"
Here is crash log. Can you help me with this?
Hardware Model: iPhone11,6
Process: avie-ios [14566]
Path: /private/var/containers/Bundle/Application/avie-ios.app/avie-ios
Identifier: AvieAIApp
Version: 2.0 (4)
AppStoreTools: 13C90b
AppVariant: 1:iPhone11,6:15
Beta: YES
Code Type: ARM-64 (Native)
Role: Non UI
Parent Process: launchd [1]
Coalition: AvieAIApp [1470]
Date/Time: 2021-12-31 17:00:50.1259 +0100
Launch Time: 2021-12-31 17:00:46.3168 +0100
OS Version: iPhone OS 15.0.2 (19A404)
Release Type: User
Baseband Version: 4.00.00
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - Fault was interrupted
VM - Fault was interrupted
Thread 0 name:
Thread 0 Crashed:
0 avie-ios 0x000000010243c598 type metadata accessor for SuggestionSettings + 0 (<compiler-generated>:0)
1 libswiftCore.dylib 0x000000018700a190 (anonymous namespace)::DecodedMetadataBuilder::createBoundGenericType(swift::TargetContextDescriptor<swift::InProcess> const*, __swift::__runtime::llvm::ArrayRef<swift::TargetMetadata<swift::InProc... + 332 (Metadata.h:3806)
2 libswiftCore.dylib 0x0000000187005070 swift::Demangle::__runtime::TypeDecoder<(anonymous namespace)::DecodedMetadataBuilder>::decodeMangledType(swift::Demangle::__runtime::Node*) + 2072 (MetadataLookup.cpp:1391)
3 libswiftCore.dylib 0x000000018700534c swift::Demangle::__runtime::TypeDecoder<(anonymous namespace)::DecodedMetadataBuilder>::decodeMangledType(swift::Demangle::__runtime::Node*) + 2804 (TypeDecoder.h:976)
Post not yet marked as solved
We have some crash which we cannot reproduce in our builds.
I can see the one of this crashes in TestFlight and want to research it.
I click "open in Xcode" in TestFlight. The crash is supposed to be opened in Xcode's organizer. But the crash opened by Xcode has another build number.
I know I can list crashes by the small control on the bottom of the organizer. There is no one crash with the same build number that noted in TestFlight. So it's look like crash never downloaded to the Xcode.
It looks like for some reason Xcode does not see crashes listed in TestFlight.
I've also check all crashes Xcode knows about. It looks like Xcode does not see the big part of crashes listed in TestFlight.
What could it be?
tschmitz.
