My app running well when running through xcode. After apple submited my app i discovered it crushes on the user's devices. The bug on terminal is:
: * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CPTMutableNumericData setDataType:]: unrecognized selector sent to instance 0x21606e90'
I know I use this class in CorePlot-CocoaTouch.h.
1.How can i solve it?
2.Why it is happens only when user download it (Also me, as a user) and not crush when running through xcode?
Thanks
It sounds like you only tested your app using development builds. Before submitting to the app store you want to test the release build using Adhoc deployment. This lets you test the version you will end up sending to Apple.
For now you need to run your app so it crashes on your own device. Then connect the device to your computer with Xcode running. Go to the Organizer window and select the Devices tab. Click on the Device Logs section near the top left corner. After some updating you should see a crash log for your app at the time you just made it crash. Use the crash log to determine where in your app it is crashing.
Related
I've been given a new React Native app to maintain and whenever I build it or run it in the simulator, I get the "Application has not been registered" error. There are no other errors in the console before this message (although there are some warnings). I can't find any code issues as if the error message is dismissed in the simulator, the app runs fine so the bundler is running correctly, although on an actual device, this registers as a crash on open.
I'm running in the simulator using react-native run-ios from the project root. Builds for running on actual devices is managed by Fastlane.
My app doesn't make an explicit call AppRegistry.registerComponent due (I think) to the way react-native-navigation is set up, so most of the info online about this error doesn't apply.
Where should I go next to figure this out?
I have setup firebase in my react native app.
But currently exceptions are not handled means not added any crashlytics logs or recorded errors
But for android app I am getting crashes in firebase but not for IOS.
Can someone explain this in detail?
Crashlytics may only be able to upload the data once the app starts again. Did you restart the app?
This can happen if you are testing while the Xcode debugger is attached.
Check this document, it explains how to test this in iOS.
If that doesn't work, enable debug logging and check if something is causing issues. For this:
After enabling debug mode, run the app.
Then hit "stop" in Xcode.
Run the app in the device and crash it
Run the app again from Xcode
Collect the output from Xcode
I've created a windows app with appcelerator Titanium. The app runs fine in all the emulators but when I run it on the device it crashes immedeately (only the splashscreen is being displayed). The error message in the console is:
The app didn't start in the required time
Any idea what the cause of this error can be?
Thanks for the help.
Trying to deploy a mobilefirst project using testflight and the app stop after the error.
: -[__NSDictionaryI WLJSONRepresentation]: unrecognized selector sent to instance 0x1740f9d80
The app works when deployed using xCode, but when installed form TestFlight, it shows black screen with the error when inspecting device log.
I resolved similar problem by following Steps in following link.
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/hello-world/configuring-a-native-ios-application-with-the-mfp-sdk/
Mainly, I was able to reproduce this by removing
-ObjC.
This sounds like an upgrade error. However without providing a sample project to recreate the error and debug it, there is not much to do other than creating a new application and migrate the app source into it.
When I use the iOS simulator and the app crashes, I can't find the crash logs. I've been looking all over the internets and can't figure out how to enable them. I know I can just run on an actual device and get the crash logs that way, but the bug I'm trying to fix right now tends to cause the program to be hung in the debugger. Then there's no qlaunchsuccess packet sending and it's a huge pain, especially when I have to run the program over and over. The only advice I've been able to find says the use CrashReporterPrefs, but a search of my hard drive reveals nothing named something even close to this. I've also dug into the package contents of XCode and the files of the iOS simulator. The iOS simulator has a crash logs folder, but it is empty. Anyone know how to get this working? Thanks.
Run your App with Xcode to install the App to iOS Simulator
Launch your App on Simulator without Xcode
reproduce steps for crash
the Crash log should show up under this directory
~/Library/Logs/DiagnosticReports/
It appears if you aren't running Xcode (mine is 4.5.2) but just the simulator (mine is 6.0) that when an app crashes it does save a crash report. To view it bring up the Application/Utilities/Console and
(1) make sure it shows the log list (see top left of console to make sure not hidden)
(2) under "DIAGNOSTIC AND USAGE INFORMATION" there is a "User Diagnostic Reports" that if you open up should have your crash reports
(3) the area on the right of the console has the log
A Crash log is just an output of what the debugger already gives you. When you are running in the simulator attached to the debugger, and you hit the crash, you can view the back trace information in the debug navigator (default key binding is cmd+5)