Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Xcode to App Store Connect Processing Issue
Hi Please when we upload our App from Xcode to App Store Connect, we do receive upload message but when we go to App store Connect interface, there we see our app being in process but it gets disabled and never goes to next step, and we waited for more than 2 hours, also we haven't received any email when we upload the app and when we refresh the page, the build in processing gets disappeared.
0
0
36
2w
Code signing issues when attempting to validate or upload for flighttest
I'm developing this app that uses python (pythonkit) to access certain python tools. It works fine locally but I was trying to validate it in order to upload it for the final testing and submission but I'm getting this signing error: codesign command failed (/var/folders/w0/9xsxryw94ps9n139w7g9q3gh0000gp/T/XcodeDistPipeline.~~~jO0urX/Root/Applications/RubyEyes.app/Contents/Frameworks/Python.framework/Versions/3.13/lib/python3.13/config-3.13-darwin/python.o: operation inapplicable or not supported for this type of code ) can someone help me?
2
0
118
2w
Error Loading Products (In-App Purchases)
I coded my mobile app using Cursor and have recently been building and submitting for TestFlight using XCode version 16.1. I am testing using my Iphone via the downloaded build from TestFlight. My onboarding flow goes smoothly, but when I reach the checkout page I receive an error that says "Error Loading Products". When I select "OK" and then try to click one of my available products I receive another error that says "Products Not Available". I am signed out of my main Apple ID and signed into a Sandbox user that is valid. I have all of my application agreements signed and valid. I believe everything is configured properly, but I have been receiving purchase errors for the past week with no progress. I had one semi-successful attempt where the Apple payment screen appeared, but have not had that since. Even on that attempt, there was a payment failure afterwards as well. Any help would be greatly appreciated. I would like to get a build submitted for app store review as soon as possible. I've attached screenshots to this ticket showing the error messages in more detail.
0
0
55
2w
Unable to launch any simulators in Xcode, XPC error talking to liblaunch_sim.dylib could not be opened
Hello, been beating my head against the wall for a few days with this. Originally got the error in Xcode 16, through the course of troubleshooting uninstalled and reinstalled Xcode multiple times, upgraded Xcode to 23 - same result. Create a different user on my computer and try, same result. Xcode > Settings > Components show both iOS 26.0 and iOS18.6 simulator, however no simulators show in Xcode, and Xcode hangs when you try to create one. 'xcrun simctl list runtimes' shows this: iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6 (unavailable, liblaunch_sim.dylib could not be opened) iOS 26.0 (26.0 - 23A343) - com.apple.CoreSimulator.SimRuntime.iOS-26-0 (unavailable, liblaunch_sim.dylib could not be opened). Does anyone have any ideas on what the issue could be?
0
0
198
3w
macOS 26.0 Tahoe + Xcode 26.0.1 Simulator causes system-wide audio distortion
After upgrading to macOS 26.0 Tahoe and Xcode 26.0.1, I’ve noticed an issue with audio playback whenever the iOS Simulator is running. Device: MacBook Pro 13" (2020, Intel, 16GB RAM, 500GB SSD) Issue: Any sound played on the Mac (system sounds, music, videos) begins to break/distort once the Simulator is active. App Sounds: If the app running inside the Simulator plays audio, that audio also breaks/distorts. Previous Version: This issue did not occur on macOS Sequoia 15 or with Xcode 16. Everything was working fine before the upgrade.
2
3
360
2w
Use of undeclared identifier 'malloc_type_zone_malloc_with_options_backdeploy'
I'm attempting to compile my app (on macOS 26), opting into the "Enhanced Security" (Xcode Version 26.0.1 (17A400)). Following Apple's documentation I enabled the capability via Xcode and clicked "Enable Build Settings" though now compilation fails: Use of undeclared identifier 'malloc_type_zone_malloc_with_options_backdeploy'; did you mean 'malloc_type_zone_malloc_with_options'? The (AI-based?) "Generate Fix for Issue" throws an error too 😅 See attached screenshots
1
1
167
1w
ENABLE_ENHANCED_SECURITY module file not found
When I tried turning on ENABLE_ENHANCED_SECURITY = YES in an Xcode 26.1 beta project, I got a bunch of "module file not found" errors like this: While building module 'CoreServices': In file included from <module-includes>:1: /Applications/Xcode26.1-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:19:2: fatal error: module file '/Volumes/Work/Xcode-derived/PlainCalc3-gixjfymjqamwmufdwcseugzjehqa/Build/Intermediates.noindex/ExplicitPrecompiledModules/CoreFoundation-5POB3HW0BHFSPWLD7DOOKAULM.pcm' not found: module file not found 19 | #include <CoreFoundation/CoreFoundation.h> | ^ I tried deleting the project's derived data. Is this a known issue?
0
0
41
3w
new font warnings spamming my logs
Hi, I recently upgraded my device OS to 26.0 and XCode is on Version 26.0.1 (17A400) My XCode log is getting spammed with these types of errors all of a sudden. And filtering is so limited (filter a single item at a time) I can't remove them. It says to file a bug, can you folks PLEASE fix this it is making debugging really hard with all its noise. Unable to update Font Descriptor's weight to Weight(value: 0.3): UICTFontDescriptor <0x110e40180> = { NSFontNameAttribute = "SF Pro Display"; NSFontSizeAttribute = 16; } - SwiftUICore/Logging.swift:84 - please file a bug report. and UICTFontDescriptor <0x1181062e0> = { NSFontNameAttribute = "Inter Display"; NSFontSizeAttribute = 28; } - SwiftUICore/Logging.swift:84 - please file a bug report.
1
0
166
2w
How di
Hi. I have been trying to figure out the code for this program for weeks now and can't figure it out. I apologize for the repeated postings. I have the following code. I am trying to find distance and velocity in the following program. I keep getting error messages. Any help would be very much appreciated! Thank you! import UIKit import CoreMotion let motion = CMMotionManager() class ViewController: UIViewController { @IBOutlet var xaxis: UILabel! @IBOutlet var yaxis: UILabel! @IBOutlet var zaxis: UILabel! let movementManager = CMMotionManager() override func viewDidLoad() { super.viewDidLoad() movementManager.startAccelerometerUpdates() movementManager.accelerometerUpdateInterval = 0.1 if let data = self.movementManager.accelerometerData { self.xaxis.text = String(data.acceleration.x) //OLD - self.yaxis.text = String(data.acceleration.y) //OLD - self.zaxis.text = String(data.acceleration.z) var xoutput = self.xaxis.text var distance: Double = 0.0 var velocityi: Double = 0.0 var velocityf: Double = 0.0 var x: Int = 1 while x == 1 { distance = velocityi * 0.1 + (1/2) * xoutput * pow(0.1, 2) velocityf = velocityi + xoutput * 0.1 velocityi = velocityf } } } }
4
0
172
2w
Long loading time when showing/hiding the Code Review window in Xcode 26.0.1
When showing or hiding the Code Review window in Xcode 26.0.1, a loading screen appears and Xcode freezes. The loading screen appears for about 30 seconds, then disappears and the Code Review window appears. During this time, Xcode also freezes and cannot function. It doesn't seem to be an error or bug, but people who frequently switch between Code Review windows find the long loading time inconvenient. Is there any way to improve this? (MacBook Pro 16, M2 Max, 64GB memory, macOS 26.0 (25A354))
0
0
104
3w
Xcode 26 macOS 26 mac app UI Testing issues
Testing is hit or miss since I've tried testing my mac App using Xcode 26 on macOS 26. Instrumenting my code shows this when things work Various App state variables initialized correctly ContentView onAppear runs App Delegate's applicationDidFinishLaunching runs When things don't work I see that the ContentView onAppear code was not executed and the app's window does not appear on my display. What would cause that to happen? This ONLY happens when testing the app in Xcode, either selecting individual tests or groups of tests or using cmd-U to run all tests.
0
0
121
3w
Xcode 26 Debug Error Display Issue
I recently installed Xcode 26.0.1. (MacBook Pro 16, M2 Max, 64GB memory, macOS 26.0 (25A354)) Normally, when debugging, a red error appears in the left-hand Issues navigation, and you can click on it to access the location of the error. However, currently, when debugging, the red error does not appear in the "Issue Navigation" on the left-hand side of the Xcode screen. There is an error, but it isn't displayed. It does appear, but disappears after 1 second. (It disappears before I can click on it.) The error doesn't appear or disappears after 1 second, so I can't pinpoint the exact location. Please help me resolve this issue. Additionally, I deleted all Xcode development-related files inside my Mac and restarted my MacBook, but the symptom still persists.
3
0
150
3w
The Xcode simulator list doesn't show the iPhone 17 simulator.
I have installed the iOS 26 simulator, and the iPhone 17 device is listed in the simulator list. However, when I set the "Excluded Architectures" to arm64, the iPhone 17 doesn't appear in the list of available target devices. When I leave "Excluded Architectures" blank, the iPhone 17 does appear in the list, but when I try to build, I get an error: "Building for 'iOS-simulator', but linking in object file (/Users/jimmy/Documents/nodejs/work/georapp/node_modules/@uiw/react-native-alipay/ios/AlipaySDK.framework/AlipaySDK) built for 'iOS'." How can I fix this so that the iPhone 17 is listed and the build process works correctly?
0
0
69
3w
Used Xcode AI to Clear 100+ Sendable Warnings
I have two apps in which I have fixed warnings on Sendable, however there's one app where I did not and it looks like the rent's come due with Xcode 26.0, as I am getting over 100 warnings about Sendable. On a lark, I let the AI work on the warnings. There were so many that I ran out of free ChatGPT time and had to wait 24 hours. But today I cleared every remaining warning, but did the app still work? I figured I'd have to trash this code and do it by hand. But to my surprise, the app is working properly so far. More testing needs to be done and I need to dig into the code to make sure it's right, but so far, so good.
1
0
73
3w
MissingEntitlement Error with Keychain Access in Mac Catalyst App
My Mac Catalyst app fails with a "MissingEntitlement" error when accessing keychain/secure storage, while the same code works perfectly on iOS. I have tested this extensively on macOS using Visual Studio Code on a MacBook, trying both automatic and manual provisioning approaches - both result in the same MissingEntitlement error during keychain operations. Error Message: "An error occurred during OTP verification: Error adding record: MissingEntitlement" Environment : Platform: Mac Catalyst (.NET 9.0) Issue: Keychain access fails on macOS, works on iOS Development: Using .NET MAUI What I've Tried : Entitlements Configuration Added keychain-access-groups to Entitlements.plist: xml <key>keychain-access-groups</key> <array> <string>$(AppIdentifierPrefix)com.example.myapp</string> </array> Project Signing Setup (.csproj configuration) : <PropertyGroup Condition="'$(TargetFramework)'=='net9.0-maccatalyst'"> <EnableCodeSigning>true</EnableCodeSigning> <ProvisioningType>manual</ProvisioningType> <DevelopmentTeam>TEAM_ID</DevelopmentTeam> <CodesignKey>Apple Development: Name (XXXXXXXXXX)</CodesignKey> <ProvisioningProfile>PROVISIONING_PROFILE_UUID</ProvisioningProfile> <CodesignEntitlements>Platforms/MacCatalyst/Entitlements.plist</CodesignEntitlements> <UseHardenedRuntime>true</UseHardenedRuntime> </PropertyGroup> Has anyone encountered similar issues with Mac Catalyst keychain access? Any insights on proper entitlement configuration would be greatly appreciated!
0
0
28
3w
iOS Simulator App Installation Failure - "Failed to create promise. Underlying error (domain=IXErrorDomain, code=2)
I'm experiencing a persistent iOS Simulator app installation failure when running automated tests using Appium/XCUITest. The error occurs consistently across different simulator configurations and appears to be related to metadata handling during app installation. Error Details Primary Error: An error was encountered processing the command (domain=IXErrorDomain, code=2): Simulator device failed to install the application. Failed to create promise. Underlying error (domain=IXErrorDomain, code=2): Failed to set metadata for org.adblockplus.AdblockPlusSafari Failed to create promise. Host info: host: 'Client641', ip: 'fe80:0:0:0:18b4:d9ba:1e92:bc37%en0' Build info: version: '4.26.0', revision: '8ccf0219d7' System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '26.0', java.version: '22.0.2' Driver info: io.appium.java_client.ios.IOSDriver Command: [null, newSession {capabilities=[Capabilities {appium:app: /Users/n.bhadoria/IdeaProje..., appium:automationName: XCUITest, appium:deviceName: iPhone 16 Pro, appium:fullReset: true, appium:includeSafariInWebviews: true, appium:isHeadless: false, appium:language: en, appium:locale: EN, appium:newCommandTimeout: 60, appium:platformVersion: 18.6, appium:processArguments: {env: {featureFlags: login=false,subscription=false, testPagesEnabled: true}}, appium:wdaLaunchTimeout: 120000, platformName: IOS}]}] Capabilities {appium:app: /Users/n.bhadoria/IdeaProje..., appium:automationName: XCUITest, appium:deviceName: iPhone 16 Pro, appium:fullReset: true, appium:includeSafariInWebviews: true, appium:isHeadless: false, appium:language: en, appium:locale: EN, appium:newCommandTimeout: 60, appium:platformVersion: 18.6, appium:processArguments: {env: {featureFlags: login=false,subscription=false, testPagesEnabled: true}}, appium:wdaLaunchTimeout: 120000, platformName: IOS} Environment Information Hardware & OS: Mac: Apple Silicon (M2 Pro) macOS: 26.0 (Sequoia) Xcode: 16.0 & Version 26.0.1 (17A400) iOS Simulator: Multiple configurations tested Affected iOS Versions: iOS 18.6 (iPhone 16 Pro) iOS 26.0 (iPhone 17 Pro) Issue appears consistent across iOS versions Development Setup: Project: iOS Safari Extension app (Adblock Plus) Bundle ID: org.adblockplus.AdblockPlusSafari App Type: Safari Extension with main app component Test Framework: Appium 2.18.0 with XCUITest driver 9.3.1 Language: Swift/Kotlin (test automation) Build Configuration: App built from Xcode DerivedData Valid development signing App installs and runs normally when launched directly from simulator Issue only occurs during automated installation via Appium/XCUITest Reproduction Steps Start iOS Simulator (tested on iPhone 16 Pro iOS 18.6, iPhone 17 Pro iOS 26.0) Launch Appium server (version 2.18.0) Attempt to install app via XCUITest driver with capabilities: platformName: iOS deviceName: iPhone 16 Pro (or iPhone 17 Pro) platformVersion: 18.6 (or 26.0) automationName: XCUITest app: /path/to/AdBlock_for_Apps.app bundleId: org.adblockplus.AdblockPlusSafari fullReset: true 4. Installation fails with metadata error Additional Context What works: Manual app installation through Xcode Manual app launch from simulator home screen App functionality when installed manually Works consistently on both iOS 18.6 and 26.0 when installed manually What fails: Automated installation through Appium/XCUITest on iOS 18.6 Automated installation through Appium/XCUITest on iOS 26.0 Occurs consistently across clean simulator instances Happens with both fresh simulators and existing ones Cross-Version Testing: Tested on multiple iOS simulator versions (18.6, 26.0) Same error occurs regardless of iOS version Different device types show same behavior (iPhone 16 Pro, iPhone 17 Pro) Troubleshooting Attempted: Clean simulator reset on both iOS versions Different iOS versions (18.2, 18.6) Verified app signing and provisioning profiles Checked simulator logs for additional details Tested with different Appium capabilities Business Impact This is blocking our automated test suite for iOS Safari Extension across multiple iOS versions, which is critical for regression testing and CI/CD pipeline. The app works perfectly when installed manually on all tested iOS versions, but automated testing infrastructure cannot proceed on any iOS version. Any insights or workarounds would be greatly appreciated. Happy to provide additional logs, configurations, or testing if needed. Xcode Version: 16.0 (16A242d) iOS Simulator Versions: iOS 18.6, iOS 26.0 Relevant SDKs: iOS 18.0, iOS 26.0, Safari Extensions
0
1
49
3w
Watchdog crash issue(0x1e71f96c8)
The app I'm developing is experiencing the following watch dog crash issue. This issue appears to be internal to the OS. Incident Identifier: 989945DB-39FA-45B7-B659-764B8DAF5166 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-23 10:28:24.4515 +0900 Launch Time: 2025-09-23 10:23:28.3571 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: app<(539E942D-7AC6-43F0-9BBC-98C5CBB3D8F9)>:340 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 14.700 (user 4.730, system 9.970), 22% CPU", "Elapsed application CPU time (seconds): 10.995, 17% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive> Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1e71f96c8 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1e71fcec8 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x1e71fcde0 mach_msg_overwrite + 436 3 libsystem_kernel.dylib 0x1e71fcc20 mach_msg + 24 4 CoreFoundation 0x19e56cf3c __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19e56c5e0 __CFRunLoopRun + 1208 6 CoreFoundation 0x19e56bcb8 CFRunLoopRunSpecific + 608 7 GraphicsServices 0x1e2fc11a8 GSEventRunModal + 164 8 UIKitCore 0x1a0ba6ae8 -[UIApplication _run] + 888 9 UIKitCore 0x1a0c5ad98 UIApplicationMain + 340 10 UIKitCore 0x1a0dd4504 0x1a079c000 + 6522116 11 MyApp 0x103b1402c 0x102aa4000 + 17236012 12 dyld 0x1c1d4c154 start + 2356
0
0
38
3w
Watchdog crash issue(Combine)
I'm having a watchdog crash issue in the app I'm developing, and it seems to be occurring from inside the combine module. Incident Identifier: 498E4709-01D9-4334-8218-4F5CAB99B504 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-22 10:55:30.4415 +0900 Launch Time: 2025-09-22 10:34:41.0221 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001a4459c38 Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [4209] Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 Combine 0x1a4459c38 Publishers.Catch.Inner.receivePre(_:) + 284 1 Combine 0x1a4459b10 Publishers.Catch.Inner.UncaughtS.receive(_:) + 24 2 MyApp 0x10cda2040 0x1043d4000 + 144498752 3 MyApp 0x10cdaf384 0x1043d4000 + 144552836 4 Combine 0x1a44bf1bc ClosureBasedAnySubscriber.receive(_:) + 28 5 Combine 0x1a44c0550 protocol witness for Subscriber.receive(_:) in conformance AnySubscriber<A, B> + 56 6 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 7 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 8 Combine 0x1a454c500 Publishers.TryCatch.Inner.receivePre(_:) + 176 9 Combine 0x1a454c444 Publishers.TryCatch.Inner.UncaughtS.receive(_:) + 24 10 Combine 0x1a445a100 Publishers.SwitchToLatest.Outer.receiveInner(_:_:) + 372 11 Combine 0x1a4459f80 Publishers.SwitchToLatest.Outer.Side.receive(_:) + 24 12 Combine 0x1a4459bd0 Publishers.Catch.Inner.receivePre(_:) + 180 13 Combine 0x1a4459b10 Publishers.Catch.Inner.UncaughtS.receive(_:) + 24 14 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 15 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 16 Combine 0x1a445a100 Publishers.SwitchToLatest.Outer.receiveInner(_:_:) + 372 17 Combine 0x1a4459f80 Publishers.SwitchToLatest.Outer.Side.receive(_:) + 24 18 Combine 0x1a4449014 Publishers.Map.Inner.receive(_:) + 204 19 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 20 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 21 Combine 0x1a4469484 Future.Conduit.fulfill(_:) + 1952 22 Combine 0x1a445443c Future.Conduit.offer(_:) + 340 23 Combine 0x1a44542d8 partial apply for closure #1 in Future.promise(_:) + 68 24 Combine 0x1a4451f50 ConduitList.forEach(_:) + 276 25 Combine 0x1a4451aa0 Future.promise(_:) + 1312 26 Combine 0x1a444c3c4 partial apply for closure #1 in Future.init(_:) + 28 27 MyAppCore 0x119d5ca68 0x117414000 + 43289192 28 ReactiveSwift 0x113a8e078 0x113a84000 + 41080 29 ReactiveSwift 0x113abee3c 0x113a84000 + 241212 30 ReactiveSwift 0x113abef58 0x113a84000 + 241496 31 ReactiveSwift 0x113ab2dc0 Signal.Observer.send(_:) + 20 32 ReactiveSwift 0x113aa37c4 0x113a84000 + 128964 33 ReactiveSwift 0x113abecec Signal.Observer.send(value:) + 136 34 ReactiveSwift 0x113af4d88 0x113a84000 + 462216 35 ReactiveSwift 0x113ade670 0x113a84000 + 370288 36 ReactiveSwift 0x113ab2dc0 Signal.Observer.send(_:) + 20 37 ReactiveSwift 0x113a8c544 0x113a84000 + 34116 38 ReactiveSwift 0x113abecec Signal.Observer.send(value:) + 136 39 MyAppCore 0x11755fbb4 0x117414000 + 1358772 40 ReactiveSwift 0x113ae3b30 0x113a84000 + 391984 41 ReactiveSwift 0x113ae4528 0x113a84000 + 394536 42 libdispatch.dylib 0x1a2f2d13c _dispatch_call_block_and_release + 32 43 libdispatch.dylib 0x1a2f2edd4 _dispatch_client_callout + 20 44 libdispatch.dylib 0x1a2f3d5a4 _dispatch_main_queue_drain + 988 45 libdispatch.dylib 0x1a2f3d1b8 _dispatch_main_queue_callback_4CF + 44 46 CoreFoundation 0x19b0576f0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 47 CoreFoundation 0x19b0548f4 __CFRunLoopRun + 1996 48 CoreFoundation 0x19b053cb8 CFRunLoopRunSpecific + 608 49 GraphicsServices 0x1dfaa91a8 GSEventRunModal + 164 50 UIKitCore 0x19d68eae8 -[UIApplication _run] + 888 51 UIKitCore 0x19d742d98 UIApplicationMain + 340 52 UIKitCore 0x19d8bc504 0x19d284000 + 6522116 53 MyApp 0x10544402c 0x1043d4000 + 17236012 54 dyld 0x1be834154 start + 2356
0
0
32
3w