I got a warning in Xcode 5.01 indicating that I needed to validate components. I clicked the button to do the validation and since then my app doesn't actually start on the simulator. I know I'm being vague but I do recall a message about validating components.
Xcode says the app is running on the simulator but I don't see my app ever appearing on the simulator any more.
I've cleaned the app and reset the simulator. I put a breakpoint in main.m but it never executes. And the breakpoint buttons to step into, over, etc are not highlighted so it is as if it has not reached the main.m breakpoint.
I also don't see any messages in the debug console.
Any idea what happened and what I can do?
Thanks
Ok, the problem was that the app had added arm64 when it did a Validate Project. However, I had an API, that I think only supports 32-bit. So I followed the instructions here which resolved the problem.
Related
I've been developing a small "Cookie Clicker" style game for a while now and all of the sudden, the app will instantly crash upon opening. It doesn't crash on my own phone that I've been running the tests on, however, anyone that downloads it from TestFlight cannot even open it. It runs perfectly on the Xcode simulator as well.
Out of desperation, I completely backtracked the update that started the crashes (deleted all the new code for the menu I was working on) but it STILL CRASHES.
I don't want to copy/paste the code here because it is 16,000+ lines and I don't even know which aspect could be affecting it. I am using Xcode 11 and Swift.
If anyone has encountered this problem before and knows even where to start looking for the problem, any help is appreciated.
You need to download the crashlogs from Testflight, re-sybolicate them, and see where it's crashing. Download them from https://appstoreconnect.apple.com/ where you manage TestFlight. Here's an example:
Inside the download is generally two files:
crashlog.crash -- this is the actual crash
feedback.json -- any input provided by the user when it crashed
The .crash file can be re-symbolicated in Xcode as needed and you can see exactly which line caused the crash.
I have a SDK project which will compile and build a framework. Inside this project, I have my person NSLog shown there. I have another framework test app to using this framework to do my task. After upgrading to iOS 10 and Xcode 8, I notice all the NSLog are gone. I cannot find it anywhere.
I search and find this answer: iOS 10 doesn't print NSLogs, I gave a try for both my SDK project and my framework test app, adding OS_ACTIVITY_MODE "disabled", however, it is still not showing NSLog.
Update: I still have one device which is iOS 9, I gave a try on that one, NSLogs are still shown in device console. Using Mac's console app I can also see my own logs.
This is a MFI project so I cannot directly debug this project, because the lighting cable is always connected with my hardware. I can only use log to see what happened.
OS_ACTIVITY_MODE set as disable remove OS activity state which is printed during the when project is runs. OS_ACTIVITY_MODE is only printed only in the x-Code 8.0 but when you upgrade your x-codefrom 8.0 to 8.1 you can found that it does not print any console for OS. But in overall procedure I have found that NSLog is working properly.
For your confirmation i just update my old project and run it into x-code 8.1. Output as below images
Environment variable
Nslog Code
console print
Suggestion
I have checked your problem in multiple style with multiple project but I didn't found any problem. So I just suggest you
To update your x-code
or
Re-install x-code after removing previous x-code completely.
Because If it is x-code bug them i also have to face the same in my every experiment.
If you still have any query you can ask.
Apple did some changes the way NSLog works and I probably you might not be able to get them.
My recommendation is that you change your NSLog to something that prints to the output console without using NSLog.
I'm the co-founder of a product called Bugfender that might help you, what we do is that we provide a BFLog function that will print the logs to the console and also upload them to our servers, so you can always check the logs without any need to connect the device to your computer.
The only problem our product has is that it's not in real time, but usually there's a delay of a few seconds. Some of our customers are using it to debug the app instead of using the XCode console.
If you set this,you can not see any log in your device ,but you can see that in simulator.
It used to be that I would see syntax errors and the like in the iOS simulator. Now all of a sudden I get stuck in Xcode (see screenshot). I can fix the error, but pressing cmd+r in the simulator does nothing and I have to press stop in Xcode and re-launch the app. My chrome debug console is open.
The latest thing I changed that I believe caused this is upgrade react-native from 0.13.0 to 0.17.0.
This might not be what you are looking for but what is your active scheme? you can check right next to the stop button. It should show your project as the active scheme.
I had this problem & it went away when I disabled my "all exceptions" breakpoint.
I've recently updated my XCode from 4.2 to 4.6 as I had an outdated iOS SDK.
However, after performing the update, When I try to run the app and press buttons, the iPhone app freezes, and returns me back to the XCode window with the errors. These are errors I have never seen before, as the App was working perfectly fine before the update. As I have never seen these errors before, I do not know what Information is needed for this error to be fixed. If I need more than these screenshots, please do tell.
What can I do to fix these errors?
I don't have the rep to post pictures, this is why I am just posting the links.
http://imgur.com/DIorBXp
http://imgur.com/t7DrRwA (One of the threads)
If the app freezes after you try to press a button then I would assume it's a problem with the linking between your an IBAction function and the onclick event of the button.
Unless I'm misunderstanding the issue, try setting a breakpoint in the function that's called when the button is cliked.
Beside suggestions of nchinda Check "Enable Zombie Objects" under Edit Scheme as this will report issues caused by bad excess or pre-releasing of an object, and check the Logs for issues. Also set break points on your IBAction to inspect more.
As the title says, I'm having issues using LLDB. I've looked into this thread Xcode 4 hangs on attaching to (App name) when debugger is set to LLDB and followed the instructions given because I'm having exactly the same issue, and managed to debug by using GDB - it works flawlessly. Anyway, i'm working in a team and I'm the only one who's having this issue, so it's a bit annoying to switch back and forward from GDB to LLDB every time i commit changes so the workaround doesn't get synchronized in the remote repository.
I've checked the compiler, and it's set to LLVM 4.2. In fact, the app compiles perfectly and gets installed in the simulator (i can execute it once I kill and restart Xcode). I would try to reinstall Xcode, but it's a mess since it's a big-sized package and I have a limit on my internet usage, it would take a long while. Does anyone know what's happening here? Is it possible that LLGB is bundled outside XCode, even if I failed to locate it on the system?
Any insight would be appreciated. I can keep the workaround going, it's just that it's a bit annoying given my personal circumstances :-)
EDIT: More details about what I mean by 'hung'. I start with Xcode open, and simulator closed (it doesn't even appear on the Dock). I click 'Run', the simulator is launched successfully, and the application shows the Splash Screen. Then xcode shows the message: "Attaching to ". And now it's hung. You can close the simulator, and xcode is still attaching. Both the Run and Stop buttons stop working. You can try to exit the application by right-clicking on the dock, you get an alert message, and from this point you can't even type code: XCode is fully hung. The only choice here is to kill XCode by using Cmd+Alt+Esc.
This sounds like it could be the problem some folks were seeing in Why does the LLDB Debugger constantly fail to attach? where they'd modified their /etc/hosts file so when Xcode tried to connect to debugserver via "localhost", the connection was never set up.
When Xcode hangs, try switching to Simulator by clicking on its Dock icon. Don't use Cmd+Tab.
Upgrading to XCode 4.6.2 fixed this issue for me