The application crashed at the customer device. Unfortunately the app does not provide
an error log in order to identify the root cause.
I was wondering what information can be collected from the customer device in order to start
working on the issue. For example is there a core file available? What other data might help us understand the problem?
Two cases:
the customer can give the device to the developer
the customer cannot give the device to the developer
Malke the Customer get the crash log(using iTunes), search a tutorial on google about how to do it. When you have import in Xcode organizer and match it with the archive that you distribute. You shoul see a comprehensible crash log.
Tecnote Apple
We're using test flight. Test flight installs its own exception handler which provides some decent data when debugging crashes (backtrace, device type, ios version, etc.).
You can see the logs on the device:
Settings -> General -> About -> Diagnostics & Usage -> Diagnostics & Usage Data
While giving the customer the IPA and provision file also give him the .dSYM file and also send him step by step procedure to send back the crash logs through iTunes. That will help you find where exactly your app is crashing.
Related
I have enterprise version installed on few of the devices.
On one of the device app is crashing immediate after the launch button click every time.
It is working on other device without crash. Can any one help me on the issue that why it is crashing ?
**edit:
We seems it certificate expiration issue. But if certificate is expired then it also should not work when I install it in new device.
Here are few steps will help you to find / detect / resolve your issue :
If its live version which you are testing than check out crash logs.
To check crash logs open Xcode -> window -> Organiser -> Select your app -> Crashes -> Select current version. You will find the crash
open it in Xcode it will help you to find the line which generating
crash
If its not live app than try to debug app on same device using debug ad hoc provisioning
Another way is you can also use crashlytics tool into your app. It will give you detailed information of the crash along with the
possible code which encouraging the crash
Possible reasons for crash :
Architecture support. Might be crash issue generated only on base 64 devices than check out your app is base 64 supported or not
Use of Depreciated methods can also cause the crash
iOS Compatibility issue can also be a reason of crash
Most important reason is if your app trying to access privacy information without permission alert than also it will get crashed at
very beginning of app launch
Hope it will help you.
We figured out this but posting bit late.
Few data systems and validation not matched in case of the Date Time system used. Date Time formats are different according to user and devices. Few systems have date formate as a month in the first 3 characters longer than the year(e.g. 1 Aug 2020). (from the same region devices, the date time format could be different). so this validation is very critical and needs to consider and all test cases. This was the issue we were facing as in the start we were opening the calendar and fetching the events accordingly.
Also displaying data on threads and managing threads are also more important in this kind of case. Memory leaks and appropriate GCD usage may also lead to this situation.
Thanks
Is it possible to get the crash log from my app? I know that we can get the exception handler by NSSetUncaughtExceptionHandler, but I want to get the crash file which could be found by Organizer. I want to access that file and send to my server. Is there any supported SDK to do that?
Thanks!!
The popular service HockeyApp is based on open source software that has it's own client that lives in your app and a basic server to collect crash reports from your app.
Check out their github account for more information on setting it all up.
https://github.com/TheRealKerni/QuincyKit
The crash log returned when your app has an error on iOS is wonderful however it would be 100 times better if it contained the console output from when your app started as part of the log. Is there a way to automatically have that information in the crash log, or have a semi-automatic system that testers could use when sending in crash logs?
I think you might want to take a look at http://apphance.com. It's exactly what you are looking for - including capability of sending problem reports from device by testers, including screenshots, you can track history of session including full console logs, you can even see crashes from out-of-memory problems which are otherwise difficult to get without physical access to the device. It's closed beta for now but soon it will be open for everyone. You can request access directly at the page.
Disclaimer: I am CTO of Polidea, company which is behind apphance and co-creator of the service.
#Medran i am not sure if this will help but if you can get the Brad Larsons videos on Advance iPhone App Development than there he says some thing about .dSYM file that will help you find the places where crash occurs. .dSYM file is made when you build your app using Xcode. See if you can find that file in your project folder its named something like this MYapp.app.dSYM
I found this information on a blog which talks about invalid product ids.
http://troybrant.net/blog/2010/01/invalid-product-ids/
I tried everything suggested in the
Apple forums and here, and still
couldn’t get it to work. Found the
solution – your app needs to be
transferred by Xcode for the sandbox
to be enabled.
Obvious, right? Well, if you are
working with an update to an existing
account, the device will still treat
it as an App Store-installed app.
Delete it, then transfer it again. It should work now :)
i am also getting invalid product ids.i am not able to get clear in the above said point...
i am not able to understand what i need to do when transferring the application into device...
Kindly guide me out and thanks for your help
That point just means that you need to run the app from Xcode in order for the sandbox to be available. (Build and Run)
Invalid product ids are a major pain to debug. If you're sure you've gotten everything on that checklist, then you just need to wait. Then only other problem that I've seen is that you might need to remove the app from the device and redeploy in order to get good products back from the store.
I had trouble getting the app store to recognize my sandbox test account. I had to log out wit iTunes, sync, then log in again with iTunes. Just using the device itself to log in/out didn't help.
Can we get the crsah logs thro app ?
Will NSFileManager/NSData help us to accesss .crash files from iphone ?
Is there any way to get it, except the well-known iTunes sync method...??
Thanks in advance.
Gopi.
There are also other ways: my company just released a service for just that purpose: http://apphance.com . You add a simple framework project to your app, integrate it (takes about 5 minutes) and you can see all the logs and crashes from your application in a web panel, where the logs, crashes, memory exceptions etc. are all available. It's automagically available from a web panel, without telling the tester whet should be sent where. The tester can also report issues directly from the application including screenshots.
The service is currently in closed beta stage and you can request beta access to it.
No, apps can not access their crash logs programatically. Apps can't access the file system outside of their sandbox (i.e. your application's directory).
Yes. Thanks Shaggy Frog.
To get the crash reports , I thought that I need to communicate with an user, and help them find the logs, they can email to me.
But later( after posting this question) I found that, we can get logs from iTunes Connect.
Apple allows us to see the some crash logs ,where developers can manage applications they have on the App Store, check their sales, and get promotional codes for their apps.
http://www.tuaw.com/2009/05/02/itunes-connect-now-lets-developers-see-crash-reports/
Thank you all!!
Have a great day!!