Every time I try to create a bot with Xcode Beta 4, I get a crash.
Process: Xcode [4678]
Path: /Applications/Xcode-beta.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 7.0 (8178.7)
Build Info: IDEFrameworks-8178007000000000~3
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [4678]
User ID: 501
Date/Time: 2015-07-22 10:42:20.647 -0700
OS Version: Mac OS X 10.10.4 (14E46)
Report Version: 11
Anonymous UUID: ***
Time Awake Since Boot: 880 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 7A165t
UNCAUGHT EXCEPTION (NSInternalInconsistencyException): View <NSPopUpButton: 0x7ffaf0480970> is not (and has to be) in stack view <NSStackView: 0x7ffaf0486080>.
UserInfo: (null)
Hints: None
This looks like the relevant bit and it seems like it's an Xcode bug.
UNCAUGHT EXCEPTION (NSInternalInconsistencyException): View <NSPopUpButton: 0x7ffaf0480970> is not (and has to be) in stack view <NSStackView: 0x7ffaf0486080>.
Other people with the same issue: https://forums.developer.apple.com/thread/11780
Not necessarily a fix, but a good workaround:
Open project in Xcode 7 beta 3 or Xcode 6
Switch Server to run with Xcode 7 beta 3 or Xcode 6
Create Bot using older version of Xcode
Switch Server to run with Xcode 7 beta 4
Bots seem to run fine using Xcode 7 beta 4 (you just can't create them)
I had to do this because my project is using iOS 9 and another bug made Xcode 7 beta 3 unable to run tests with bots.
Submit a bug report... The more valid reports they receive the more quickly they can fix it. Be sure to submit any work around so's they can communicate them, should they decide to do so.
Related
I have test and submit my app to Apple Store but Apple reject and response my app crash on launch. I have test my app on many model iPhone and iPad it's working normal, Have anyone can tell me why?
Crash log Apple send to me:
"bug_type":"109","os_version":"iPhone OS 11.2.5 (15D60)","incident_id":"F2C32C7F-63B2-4D96-8D90-1AF644DC5179","name":""}
Incident Identifier: F2C32C7F-63B2-4D96-8D90-1AF644DC5179
CrashReporter Key: 31ed20e652158d2a96b6662d50b1000ce2837b82
Hardware Model: iPad5,1
Device Model: J96AP
Process: gamebaionline [5995]
Path: /private/var/containers/Bundle/Application/872913FE-A768-4837-81EB-F76C427CFBED/gamebaionline.app/gamebaionline
Version: 0 (2.0.5)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd.development [1]
Date/Time: 2018-03-03 07:05:30.9221 -0800
Launch Time: 2018-03-03 07:05:23.9926 -0800
OS Version: iPhone OS 11.2.5 (15D60)
Baseband Version: n/a
UDID: 3ab61350a5372c6a81b3d6b6ac3e5a8c7d1cd04c
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 11
Application Specific Information:
* Terminating app due to uncaught exception 'NSGenericException', reason: '* Collection was mutated while being enumerated.'
terminating with uncaught exception of type NSException
abort() called.
Now i can't test with iOS 11.2.5 because Apple not allow signing in iOS version 11.2.5 or downgrade version to 11.2.5. Please help me.
Collection was mutated while being enumerated.
This mean that you have some data structure (like dictionary or array) and you iterate over elements and in same moment modify this structure, for example remove some elements. I suppose you to check all iteration that you do on very start. Or use symbolic breakpoint to find it. Note, that such crash can be a little bit tricky, because i guess some operation like remove or so may be not performed. Because of this you may or may not have crash on start
I solved mine by doing the following,
1. Symbolicate the error logs received from Apple.
2. Delete the app completely from you actual device and run a build from Xcode on it, this time it will crash and show you the lines where the bugs are!!!
I'm running into a strange issue whereby an app I'm building crashes shortly after launching as an archived build from TestFlight, but runs without issue when running on the same device directly from Xcode. The application doesn't appear to be terminating fully - if I double-tap the home button, I see what looks like an image of the application in the background from midway through a run, even though the new session crashed long before it would have gotten to the displayed screen. If I then bring the application back to the foreground, it returns to its loading screen and then shuts down again, with a log that looks like this:
Incident Identifier: 983F8E4E-EFE0-4C93-8F46-D223FD86DF14
CrashReporter Key: 3515df1d8c55a27394a78b6efee5f83946ed9a99
Hardware Model: iPhone7,2
Process: FileProvider [218]
Path: /private/var/containers/Bundle/Application/89708FF4-E848-4F49-BC0D-B2DC9EF536C6/Drive.app/PlugIns/FileProvider.appex/FileProvider
Identifier: com.google.Drive.FileProviderExtension
Version: 4.2017.25202 (4.2017.25202)
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: launchd [1]
Coalition: com.google.Drive.FileProviderExtension [368]
Date/Time: 2017-06-30 22:59:01.2937 -0700
Launch Time: 2017-06-30 22:59:00.7649 -0700
OS Version: iPhone OS 10.3.2 (14F89)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace <0xF>, Code 0xdead10cc
Triggered by Thread: 0
...Any thoughts on what I should be investigating to understand what's going on here?
App is built in C++ using the Cocos2d-x framework.
Thanks!
_Kevin
Figured out what was going on, if not yet exactly why. Some of the details posted above turned out to be red herrings as I investigated further. What initially appeared to be a difference in behavior between an archived build and a build launched directly from Xcode was actually a difference in behavior between a debug build and a release build.
The solution was to create a new scheme in Xcode to run a release build (Product->Scheme->Manage Schemes in Xcode 8.3), duplicate my default mobile scheme, and then set the new scheme's Run->Info->Build Configuration to Release.
Once I ran a release build with Xcode attached, I found an error (probably an incorrectly-initialized variable but I'm still investigating) that occurred in release builds only.
The reason why crash logs weren't being generated appears to have been that the error was causing an assertion to trip (the CC_ASSERT macro in Cocos2d-x), so iOS considered the app shutdown to be a legitimate termination and didn't log it as a crash.
I have been working on an App today and have been able to debug it. All of the sudden I can't use breakpoints without Xcode 5.1 crashing. It will stop on the breakpoint, look like it's trying to display the local variables in the bottom left window, and then crash.
This is the crash report:
Process: Xcode [8084]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.1 (5084)
Build Info: IDEFrameworks-5084000000000000~21
App Item ID: 497799835
App External ID: 444172641
Code Type: X86-64 (Native)
Parent Process: launchd [189]
Responsible: Xcode [8084]
User ID: 294396280
Date/Time: 2014-04-03 14:57:52.981 -0600
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 5BFD5C24-5465-3BC8-137A-4BF1A8D48B38
Sleep/Wake UUID: F94AB6A7-9517-4F94-93DA-CC2C9154C8A7
Crashed Thread: 30 DBGLLDBSessionThread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 5B130a
Assertion failed: (!isNull() && "Cannot retrieve a NULL type pointer"), function getCommonPtr, file /SourceCache/lldb/lldb-310.2.36/llvm/tools/clang/include/clang/AST/Type.h, line 547.
(I can supply the rest of the report of what the threads are doing if it is helpful).
I have placed breakpoints in various files and locations in the code. I am able to use breakpoints in some places, but the majority of the breakpoints cause the crash.
I have looked through several SO pages with no luck. Among other things I have tried deleting all the breakpoints and just adding 1 back in. I have deleted and regenerated the schemes.
Any ideas?
I updated to 5.1.1. and the problem still exists:
Process: Xcode [19072]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.1.1 (5085)
Build Info: IDEFrameworks-5085000000000000~10
Code Type: X86-64 (Native)
Parent Process: launchd [197]
Responsible: Xcode [19072]
User ID: 294396280
I happened to have two iPhones connected via USB (a 4 with iOS 7.1 and a 5 with iOS 7.1.1), and Xcode 5.1.1 was "beach-balling" on me at the first break-point, wherever it might be, whichever breakpoint was hit first.
Just disconnected the iPhone 4 from USB.
I can use breakpoints again :)
YMMV of course ...
I encountered this problem as well recently with the same exact LLVM error:
Assertion failed: (!isNull() && "Cannot retrieve a NULL type
pointer"), function getCommonPtr
In my case it was a piece of code where I was storing an enum value (Permission) within another object as a reference, rather than a value:
Correct:
#property(nonatomic, readwrite) Permission permission;
Wrong:
#property(nonatomic) Permission *permission;
I was able to narrow down the problem by running Xcode's code analysis. After I made a correction to one or more of the warnings in each class I would rerun the analysis, then test and commit. Tedious but effective, and now I can debug again properly. Hope this helps steer someone in the right direction.
I clicked to turn off auto layout. And now I click the check box to turn it on, and xcode immediately crashes..Every time. I'm pretty sure that all tableviews have a datasource. I can't work on the project! Please help.
Process: Xcode [5748]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.0 (3332.25)
App Item ID: 497799835
App External ID: 38302662
Code Type: X86-64 (Native)
Parent Process: launchd [144]
User ID: 501
Date/Time: 2013-09-30 00:12:40.236 -0400
OS Version: Mac OS X 10.8.5 (12F37)
Report Version: 10
Interval Since Last Report: 62599 sec
Crashes Since Last Report: 13
Per-App Interval Since Last Report: 4441 sec
Per-App Crashes Since Last Report: 13
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 5A1413
ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch- 3742/IBPlugin/Utilities/IBObjectMarshalling.m:670
Details: Failed to compute auto layout status IBUIDatePicker, IBUILabel, IBUITableViewCell, and IBUITableViewCellContentView.
Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Exception name: NSInternalInconsistencyException
Exception reason: UITableView dataSource is not set
I just faced this problem and removing all of the File Owner's Outlets and Referencing Outlets did the trick.
Note: Firstly, as I couldn't turn off autoLayout graphically as Xcode crashed just by trying to view the .xib, I managed to do it following AbuYusuph's suggestion.
I was able to fix this issue by deleting the symlinks I had from the /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/ to the /Users/xxx/Library/Developer/Xcode/iOS DeviceSupport. I hope this will help.
I just remade an entire viewController and it works now. Not really answering the question. I am thinking it's just a glitch
I have currently updated an app and pushed to App Store. After the approval process, it can be downloaded from AppStore.
The issue is, "some" of the users report that they cannot switch on the app, either update or download from scratch.
Some of the devices they use:
iPod Touch (5th Generation)
iPhone 5
iPad 2 ''newly added''
The console log shows like this:
UIKitApplication:{app-identifier} exited abnormally with signal 4: Illegal Instruction: 4
I have also got the crash report like this:
Incident Identifier: 1912AA89-01F4-4BFE-8BD8-2D8EB3B4B988
CrashReporter Key: 4e0582bb30455ff2c12665099359dfddd3ec9bab
Hardware Model: iPod5,1
Process: 'app_name' [551]
Path: /var/mobile/Applications/C589BCAA-B833-4708-93CA-CDD2ABCBA38A/'app_name'.app/'app_name'
Identifier: 'app_name'
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-07-16 15:45:42.278 +0800
OS Version: iOS 6.1.3 (10B329)
Report Version: 104
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x00000000e7f5e2fa
Highlighted Thread: 0
I cannot find much information on the Internet related to Illegal Instruction: 4, some of those are listed here and here.
They lead me to suspect the case is due to:
compiler issue
new CPU
like A6 / A6x
armv7s
Does anyone know the reason?
Apple did not give any comment, after doing the Support request.
We uploaded the new ipa with all the same settings to iTunes Store again, and ask for Expedited Review. Apple approves the app in one day. Then, problem no longer exists.