CrashReporter | Lightweight macOS Crash Reporter Setup | Dashboard library

by CleanCocoa Swift Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | CrashReporter Summary

CrashReporter is a Swift library typically used in Analytics, Dashboard applications. CrashReporter has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Your app will crash one day. Be prepared to collect crash data automatically, because not every user is a techno wizard capable of sending you .crash files from the built-in Console app.

Support

Quality

Security

License

Reuse

Support

CrashReporter has a low active ecosystem.

It has 102 star(s) with 2 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of CrashReporter is current.

Quality

CrashReporter has no bugs reported.

Security

CrashReporter has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

CrashReporter is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

CrashReporter releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of CrashReporter

Get all kandi verified functions for this library.

CrashReporter Key Features

No Key Features are available at this moment for CrashReporter.

CrashReporter Examples and Code Snippets

No Code Snippets are available at this moment for CrashReporter.

Community Discussions

Trending Discussions on CrashReporter

Problem with Repackaging Applications with Frida Gadget on iOS

How can I debug a "Failed to install" message?

Xamarin app crashing during apple review process

How to check for errors on xcode disconnected devices?

Can not find origin of "This application is modifying the autolayout engine from a background thread"

App crashing when run from device but not from Build and Run

Dyld Message: Library not loaded: /System/Library/Frameworks/FileProvider.framework/FileProvider

How to read symbolicated crash log?

Symbolicated iOS crash report from Apple review still not readable

DYLD, no cache image with name (@rpath/libswiftCore.dylib)

QUESTION

Problem with Repackaging Applications with Frida Gadget on iOS

Asked 2021-Jan-04 at 08:19

I've been tinkering with Frida Gadget recently on a Phoenix jailbroken iOS 9.3.6 device and keep running into a problem that prevents my re-packaged application from launching.

In this example, I have re-packaged my DVIA application using the patch-ipa option that comes with objection. This tool basically automatically re-packages an ipa file with Frida Gadget.

I have also tried re-packaging manually by following this link.

In both methods of re-packaging an application with Frida Gadget, I end up with an application that crashes the moment I launch it. It seems that there might be an error with loading a dynamic library but I cannot seem to find any fixes after combing through the internet to see if anyone has experienced anything similar, and am completely lost.

The full console logs from launching a re-packaged-with-frida-gadget DVIA (Damn Vulnerable iOS Application) with the crash are as follows:

...

ANSWER

Answered 2021-Jan-04 at 08:19

iOS fails to load FridaGadget.dylib with the error message no matching architecture in universal wrapper.

Combining this error message with the knowledge that Frida has dropped iOS 32bit support some months ago (as far as I remember 12.11.x were the last versions with 32bit support) the chance is high that the app you are trying to repackage is a 32 bit app.

Based on the size of the decompressed version of FridaGadget.dylib you can identify if it is a version with 32bit support or not. If it smaller than 70MB then it is a 64bit only version. If you want the full list of supported architectures use otoool or file command.

Therefore you have now two options: If possible I would recommend you to change DVIA app to 64bit. Then the recent Frida gadget will work again.

Alternatively you can try to use an older Frida gadget versions that still has 32bit support. Keep in mind that you also have to use the old Frida python scripts because the Frida 14.x seems to use a modified communication protocol between Frida and the FridaGadget and thus the communication between recent Frida 14.x scripts and old 12.x Frida gadget will not work.

Source https://stackoverflow.com/questions/65557508

QUESTION

How can I debug a "Failed to install" message?

Asked 2020-Oct-19 at 01:57

I am currently attempting to develop a cross-platform mobile app using Xamarin.forms. As a part of this application I need to include a 3rd party .framework in my Xamarin.iOS project. I have successfully created a Xamarin.iOS Bindings Library .dll and included it in my project. I am able to reference the library and compile without errors, however when I attempt to deploy the app to the iPhone simulator the app will start and then crash with a “Failed to install” message.

Error Message

If I remove any lines of code which reference this .dll the app will run fine.

Does anyone have any insight on how to solve this?

Potentially useful information:
I am developing in Visual Studio for Windows
Xamarin version: 16.7.000.440
Xamarin.iOS version: 13.20.2.2
XCode version: 12.0.1
iOS version: 14.0

Device Crash Log:

...

ANSWER

Answered 2020-Oct-19 at 01:57

From the apple document, the errors means you have linked the frame while does not ember it.

The app crashes at launch, because the dynamic linker can’t locate the missing framework.

So what you need to do is ember the framework and here is the document you can refer:

Linking the dependencies

binding-objective-c

Source https://stackoverflow.com/questions/64360943

QUESTION

Xamarin app crashing during apple review process

Asked 2020-Sep-30 at 11:26

I'm developing a Xamarin navigation app for a local walking route, the app seems to work fine on any physical device I try it on, also distribution using the Testflight system seems fine. The android version is available on the app store and works.

However when I submit the IOS app for review, the app always seems to crash when the Apple employee presses the "Get started" button in my app.

Pressing get started switches the app to the gps navigation page and starts the navigation, which is why I'm asuming something goes wrong here: MapPage.xaml.cs

I have tried different linker settings, because I think that might be the issue, sadly I can not try to disable the linker entirely, because it makes the size of the executable exceed the app store limit.

The project is public: https://github.com/jelknab/FamilieWandelPad

Attached is a symbolicated crash log:

...

ANSWER

Answered 2020-Sep-30 at 11:26

I found the issue by adding appcenter issue tracking. The problem still persist on apple review devices, but has now passed review by try-catching the issue and not doing anything with it. The app works fine on any other devices.

Source https://stackoverflow.com/questions/63615287

QUESTION

How to check for errors on xcode disconnected devices?

Asked 2020-Jun-08 at 05:35

I'm testing it by building an app on my iPhone device with xcode. An iPhone app that has been disconnected from xcode works for a few days, and then turns off when you run the app.

I don't see my app name in the analysis log in iPhone privacy, and after syncing with mac, I can't check the error in logs> crashReporter.... How do I check the wrong part of my code?

...

ANSWER

Answered 2020-Jun-08 at 05:35

You can connect the Xcode debugger to a running process or you can also have Xcode wait for a process to launch before connecting. Either way use the Xcode Debug menu to attach the debugger to a process (If you want to set some breakpoints for when the App is launched you can do that also) :-

If the App is not yet running you will need to attach to it by name. For example, here I am going to attach to the AdaptType project:

If the process is not running the Xcode debugger will wait for it to start. This is useful if you want the App to launch in response to an external event such as a notification :

If the App is already running you can connect to it directly either by name or finding it in the list of running processes. Make sure you have the device or simulator selected as the target of your Xcode project then use the “Attach to Process” option in the Debug menu:

Xcode suggests the most likely process based on your current Xcode project and destination or you can find it in the list of running processes. Once attached you can debug as usual. The debugger will stop if it hits a breakpoint or you can use the view debugger to inspect the view hierarchy.

More info can be find here :

Source https://stackoverflow.com/questions/62255307

QUESTION

Can not find origin of "This application is modifying the autolayout engine from a background thread"

Asked 2020-May-15 at 05:23

My app crash only the first time i log into it. It used the GoogleMaps (3.7.0) pod, and I suspect the error comes from that library:

...

ANSWER

Answered 2020-Jan-23 at 08:26

Obviously the background thread in question (Thread 17) is accessing some UIKit method directly which in general is not allowed (can only be done from the main thread).

Did you dispatch some method on a background thread using GCD's dispatch async?

Source https://stackoverflow.com/questions/59874131

QUESTION

App crashing when run from device but not from Build and Run

Asked 2020-Apr-20 at 03:50

I'm fairly new to Swift and using Metal so please forgive if I've made a huge oversight. I was following a tutorial for starting with MetalKit and the app works fine using "Build and Run" with a device connected, but it crashes on launch immediately when started from springboard.

Attaching the debugger prior to launch, I get the following breakpoint with a [UIResponder doesNotRecognizeSelector:]: message. This occurs immediately during the Storyboard initialization.

The view hierarchy is a MySceneViewController: MetalViewController,MetalViewControllerDelegate as the root view controller, with the mtkView below set in the main storyboard. There is nothing else in the app right now.

Again, this exact same code works when running from Xcode directly so I have no idea what I'm doing wrong here.

Thanks for your help. I'd be happy to add any other information if required.

Edit: added the debug trace from the phone log

...

ANSWER

Answered 2020-Apr-20 at 03:50

If application is launched from a Springboard, then mtkView has wrong type (UIView). To check it you can use command po in a debugger:

Source https://stackoverflow.com/questions/59043406

QUESTION

Dyld Message: Library not loaded: /System/Library/Frameworks/FileProvider.framework/FileProvider

Asked 2020-Apr-11 at 21:04

I'm developing a multi-device app with C++Builder (RAD Studio 10.2.3).

The Android release works, while the iOS does not.

I build the app for iOS using a Mac (MacOS 10.3.4), with Xcode 9.4.1 (with iOS SDK 11.4), with the option to compile both for 32-bit and 64-bit version.

I'm realeasing it for Ad Hoc deployment. My iPad3,3 (iOS 9.3.5) is connected to my PC via USB and synchronized with iTunes. I install the app by drag&drop from the PC to the device in iTunes.

When I run the app on the iPad, a black screen appears for a moment and then nothing. If I read the .crash file in C:\Users\myuser\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\myiPadName (synchronized with iTunes) I see:

...

ANSWER

Answered 2018-Sep-03 at 06:38

I solved this issue removing FileProvider framework (that seems to be available from iOS 11) from RAD Studio > Tools > Options > Environment Options > SDK Manager.

Source https://stackoverflow.com/questions/52117962

QUESTION

How to read symbolicated crash log?

Asked 2020-Apr-10 at 23:01

Today my first app was rejected from testflight, because it crashed on start. But I cannot replicate it, because I do not have an Iphone, and in the simulator it works. I managed to symbolicate the crash log, but cant figure out how to read it. Could you please explain what this means and how it is read?

have to dump some text because its longer than the max. allowed post length:

...

ANSWER

Answered 2020-Apr-10 at 18:01

So @sharkyenergy found the real bug! I am placing his solution above my suggestions:

"I developed on windows, but due to the pinch/zoom problem, i had to move to a mac. I didnt know that on mac you must add every nuget package to the .ios project too, while on windows they are shared. after adding all the packages it didnt crash anymore."

If his solution doesn't work for you, you can try the following below the line:

Things you can try,

While creating the archive, we use the Release-iPhone config, which is different from the Release-iPhone Simulator config. So when you are testing, you may not be testing the ACTUAL configuration. To check this, open the iOS Project Options in Visual Studio and compare all the settings to be the same (particularly the Linker behavior). Then test it on the simulator again and it could catch the error.

2. Occasionally your app can crash on launch in prod only, and the Microsoft AppCenter package can help you with this for free. Here's something you can add in the AppDelegate just when your FinishedLaunching function begins:

Source https://stackoverflow.com/questions/61087534

QUESTION

Symbolicated iOS crash report from Apple review still not readable

Asked 2020-Feb-16 at 10:27

I got a crash report from Apple and symbolicated it following this document, but I still didn't understand the report.

First, I tried below "XCode approach" to symbolicate the report:

Connect an iOS device to your Mac

Choose "Devices" from the "Window" menu

Under the "DEVICES" section in the left column, choose a device

Click the "View Device Logs" button under the "Device Information" section on the right hand panel

Drag your crash report onto the left column of the presented panel

Xcode will automatically symbolicate the crash report and display the results

Before that, I downloaded dSYM files from App Store by 'Organizer' and copied them into a separated folder. But all the symbolicated names looked like this:

...

ANSWER

Answered 2020-Feb-09 at 07:32

In Xcode 10 you can follow these steps:

Inside Organizer, locate the archive where the app is based on. Click on the Download Debug Symbols button. Nothing will appear in your Downloads folder, but that's OK. Connect the build machine to an iOS device. Select the device in Devices and Simulators. Click on the View Devices Logs button. Drag-and-drop the crash file to the left panel. The file must end with a .crash extension, otherwise the drag fails. Switch to the All Logs tab. Select the added crash file. The file should automatically symbolicate, otherwise use the right-click context menu item Re-Symbolicate Log.

Source https://stackoverflow.com/questions/60133806

QUESTION

DYLD, no cache image with name (@rpath/libswiftCore.dylib)

Asked 2020-Feb-06 at 12:16

I'm getting a crash on tvOS 12.2 with the following details:

...

ANSWER

Answered 2020-Feb-06 at 12:16

I've found a workaround for this issue. Simply adding a dummy Swift file (with a dummy class in it) to the ObjC app project resolved the issue. No need to have a bridging header, nor any need to actually reference the dummy class anywhere.

It doesn't answer the question of why it's happened, but perhaps there's an issue in Xcode and this just forces it to include the Swift standard libraries.

Source https://stackoverflow.com/questions/60092499

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install CrashReporter

See the code in Example/, which is part of the Xcode project.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: