OS: Windows 7 (Mac cannot be used)
Apple mobile devices running iOS7
We're testing our apps. In iOS6 and previous versions of iOS, we just needed to sync the iOS device using iTunes, and the app crash logs & memory dumps appeared in "C:\Users\ *USERNAME \AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\ *DEVICENAME" (mostly there was a ".crash" file). But after updating to iOS 7, the crash logs no longer appear in the specified directory when the iOS device is synced. Since crash logs are vital in knowing what caused the crash, we need them as soon as the app crashes. Please provide some help on how to get the crash logs.
EDIT: WHY ARE YOU GUYS DOWNVOTING?
Use the Xcode organizer to see the crashes of your device and get it symbolicated.
Related
I just got back into iOS / WatchKit development after a ~8 year break. I'm having a really hard time making an app for the watch, because
Simulator is not helping because random things seem unsupported (most recent example being WCSession.transferFile, which apparently is a bug)
On device is not helping because the loop to get it to run on device is completely out of hand, and I was not able to get either logging or debugging to work when running on device. (My main problem is that if I do CMD R in Xcode with my Watch selected as target, it builds, and says running, but never launches the app. If I launch the app manually I find it's not the most recent version. I have to go and remove it from the watch, and re-add it, which then causes Xcode to not be able to run it anymore, which means I have to restart Xcode. What.)
So my question to more experienced devs is: what's your debug cycle when writing Apple Watch apps?
I'm running Xcode 12, watchOS 7.1, on Mac OS 10.15.7 (not Big Sur which may be some cause of issues)
Some steps that help for on device debugging:
To re-install the watch app, select the iPhone app in Xcode and build and run that. This will also re-build and re-install the watch app as needed.
Open the app manually on the watch
I still haven't figured out how to get a debugger or console, but for now my hack is to have a label on the watch that I use as my on device console.
This is almost certainly an Xcode 12 issue. At least since Xcode 12.5 my app has not worked with watch simulator (it can't connect to the phone simulator) and I get no debugger with a real device.
Using Xcode 12.3 seems to work.
My application is working fine on iOS 11.0. But when I am run on iOS 12.0 they crashing immediately on startup. My application is on Objective-C and MRC.
Running fine in simulator but crashes in the device.
No main or didFinishLaunchingWithOptions is called yet.
Tried re-installing the application. Tried "Eare All Content and Settings" but it does not work.
Enabled zombie objects but even that did not help(no logs recorded).
I also try to symbolicated the crash report but not find any solution from crash report.
I have attached my crash report here.
Crash Report
I found the solution. The app is crashing just because of using an Old version of the Crittercism SDK. Upgrade to the latest version to support iOS 12.0.
I'm getting crash on iPhone 5 (8.2) ,When i install through ipa but I'm unable to get any crash while debugging on the same device.Please help me how to fix this?.
Start with looking at the console, to see what messages occur on the device.
Also, if you hook the device up to your development computer with a USB cable, you should be able in Xcode to look at the device logs to get crash reports and figure out where the crash is from.
Also check for TestFlight crash logs on Apple's servers (iTunes Connect)
During review, your app crashed on iPad running iOS 8.1.2 when we tap the login button on the first page.
This occurred when your app was used:
- Offline
- On Wi-Fi
- On cellular network
We have attached detailed crash logs to help troubleshoot this issue.
I have tested latest release on iPad 2 , iPad air simulator and even in iPad devices. Its working fine. I have tested it in IOS 8.1.3 because this is the latest update. How we test it in IOS 8.1.2.
I also matched UUID of release , and crash log UUID its same. i followed all the guide. How i follow my issue , i did't find this bug in my app.
I have recently sent an app to App Store to fix a crash on iOS 4.3 (I accidentally used a color on a UIProgressBar). I tested the new version on a iOS 4.3 device and everything runs as it should. Apple have accepted the app and the update has rolled out. The users are still reporting about crashes on iOS 4.3.
I have tested the app on iOS 4.3 in both Debug and Release and it seems to run exactly as it should. But if I download my own app from the App Store it crashes on iOS 4.3. I haven't changed anything in my code since I uploaded the new version to to App Store.
How can this happen? Shouldn't it be exactly the same to run the app as Release directly from Xcode and downloading the app from App Store?
try looking at the crash report on the device.
To do so:
attach your device to your computer.
Open organizer in XCode
select your iOS Device
open the Device Logs.
Perhaps you can find something there - Probably a call to a method not supported by iOS 4.x
Good luck!
It could come from the watchdog of the device killing the app when it launches. When you run from Xcode the watchdog is disabled to compensate the overhead of attaching the debugger, etc.
When downloaded from the app store (or unplugged off Xcode), the watchdog is active, and killing your app if it's too long to launch.
Look for error code "0x8badf00d" in the crashlog.