After the project was launched, the application was not added to the dashboard.
I launched the project on an android SDK with the same package name. After that, the application was added to the dashboard.
Events such as "sendCustomEvent" work. But the crash still is not sent. Does anyone know the solution?
Todd from Fabric here. Corona is not currently supported by our SDKs due to the way it builds projects. Barring official support, I'd love to hear if any one has gotten this up and running and the steps they used to do so. Thanks!
I was able to send a crash. It was necessary to remove the application using adb.
adb uninstall "name.package"
Related
Please guide me! Why Firebase console take much time to communicate with server. I'm waiting one and half hour to complete this takes. Anybody tell me what is the reason behind this issue or anyone facing this issue before.
Not show the Graph.
Please make your app force fully crash 2-3 times, after disconnecting your app from Xcode.
This is what worked for me.
In my case, I solved this problem by doing these steps:
Make sure you follows the all steps that mentioned in Firebase Documentation Crashlytics.
Use fatalError() for crash your app.
Uninstall App from simulator or Real Device
Run the app on Simulator or Real device then stop running.
And then Open the App that Install on Simulator or Real device.
Open Firebase Console project And Refresh it.
This can happen as a result of several different issues, however they're usually connected to your app being unable to make the proper call to the Crashlytics settings endpoint. You can either write in to Firebase support, or feel free to start a private thread with me, and I can check your apps settings in the Firebase backend.
if you followed all steps as per latest crashlytics documents!
try forcing a crash directly with button click on initial view instead of just building and running your app
use fatalError() for crash your app
I have a whitelabeled app and every customer's app has its own unique bundle identifier. This causes Crashlytics to flood with different apps which potentially could have the same crash report. I would like to have it all grouped under one app, so it's easier to maintain.
I know there's a solution for Android (https://gist.github.com/tyvsmith/6188014), but couldn't find anything for iOS.
Does anybody know if this is possible for iOS and if so, how can I do this?
Mike from Fabric here.
Currently, there isn't a way to do this on iOS for Fabric. I'll let the team know you'd like to see it added in.
I have the same situation, and I've confirmed with testing today that Crashlytics forces me to have a separate app in their system for each of my customers. I suspect with Firebase/Google integration this will not change as they'll be offering a complete app framework (just as the transition from Xamarin Insights -> HockeyApp -> Microsoft Mobile Center). I reviewed the alternatives today; Raygun.com has had long-standing support for Xamarin and the only association between your app and Raygun is a text key, and it works with or without the dSYM files. So far so good!
Are we able to use FBDialogs in production apps yet? Looking at the latest SDK 3.5.3 I see this: https://github.com/facebook/facebook-ios-sdk/blob/master/src/FBSettings.h#L58
Which states that we shouldn't be using the native fast app switching share dialog in app store apps yet. Can someone clarify? Thanks.
They're in production, meaning that you don't need to set those flags anymore.
I am using testflight to distribute a beta of my app and sometimes having issues logging in to the websites. I want to try crashlytics but i read that there some issues with using both at the same time. Can i not include testflight SDK and still be able to distribute beta using it? Is that a normal practice or i should just stick to one? What about using hockeyapp for both?
Also for people that use crashlytics do you ask the user first to allow sending crash reports.
PS if this question is not approriate for stackoverflow please let me know where with stackexchange
Thank you in advance!
Wayne from Crashlytics here. Crashlytics is compatible and you shouldn't have any worries. For support you can contact at support.crashlytics.com.
You do not need to use the testflight SDK to distribute with testflight, so remove that and use ccrashlytics.
You can ask them before they become the beta user, you dont need to ask each time. If you put that code into production, then you should ask every time before sending.
We have logging in place for any .Net Framework exceptions that occur in our iPad MonoTouch application and can get these back to our support department to help analyze and resolve issues.
However, if the application crashes due to an iOS error (i.e. sigsev), we are unsure how to capture that information or tell our very unsophisticated users how to obtain and provide it to us.
Can anyone offer any guidance on this?
We're using these bindings for HockeyApp iOS SDK (I believe they have one for Android too).
They provide a service similar to TestFlight. Automatic crash symbolication is very nice.
We also employ this fix because it's essential to crash reporters working in MonoTouch.
Be warned that TestFlight and HockeyApp will currently crash your app if you don't use this fix.
Crashes will often (but not always, e.g. out-of-memory) create crash logs on the device. iTunes will download them to the user's computers.
Are you releasing your application thru the appstore ? If so you should be able to get the crash logs from it (iTunes will upload them).
If not then the following documents (and sections) can be useful to know about them (and to create a procedure for end-users to send the crash reports to you).
Acquiring Crash Reports
Sending Crash Reports to a Developer
Xamarin is working on getting the Testflight SDK to fully work with MonoTouch (i.e. the service itself (distribution already works and is integrated in the latest MonoDevelop releases). That will give you another option (for crash reporting) in the future.
The official (I assume given it's a branch of the mono git hub repository) monotouch-bindings project over on github now has support for the TestFlight SDK, check out:
https://github.com/mono/monotouch-bindings/tree/master/TestFlight
and
https://github.com/mono/monotouch-bindings
Excerpt from their readme:
TestFlight
This is a MonoTouch binding for the TestFlight SDK which can be found at
https://testflightapp.com/sdk/
The current version of this binding is for TestFlight SDK 1.2.1
v 1.2.1 released on 26 dec 2012
Bindings updated on 17 mrt 2013
Building
Run make in the binding directory to build TestFlight.dll
Using TestFlight.dll with your own iOS App
Simply add TestFlight.dll to your project's References in MonoDevelop and you
are good to go!
To use the thread safe TakeOff methode. Change TestFlight.TakeOff(token) to TestFlight.TakeOffThreadSafe(token)