Raygun with Xojo

Raygun seems to be the monitoring and crash reporting solution du jour. I need to capture crash reports from my app to improve the reporting rate from users and therefore improve the app’s quality and I was wondering whether anybody had any experience using Raygun with a Xojo app? As expected Xojo isn’t listed as one of their supported languages but they have a REST API that looks simple enough though it appears as though it won’t provide the full feature set that you’d get with one of the language-specific integrations. Anyway just looking for any feedback if somebody has attempted this.

I would love to know. I have not looked at it but looks feasible.

Looks interesting. We created our own Xojo web app to do something similar with our apps. This is probably better in the long run.

I thought about creating a Xojo web app to handle error reports and that would work but Raygun is about the same price per month (or less) and it’s ready to go.

I dont expect raygun for iOS will work with xojo at all (no plugins so you cant “link it in” like their quick start says to in Xcode)

It might be possible to create a plugin for a desktop or console app & web too

For a web app since it’s js that you can add in and then call into etc it may (not sure how it interacts with the js that the xojo js framework uses)

Raygun’s site says you can manually publish errors to Raygun using their REST-oriented API. While not providing the benefits and ease of integration of a Cocoa pod library, for example, it still looks like an option to me.

Thats roughly what we do with feedback from within the IDE

Why not look at airtable? It’s what i’m using for my crash reports (internal) and they show up instantly on my iphone (airtable app). I use it for iOS and Desktop. The xojo video about airtable on youtube is very helpful for this.

For those interested, the Airtable Webinar http://developer.xojo.com/webinar-airtable

Thanks. That’s definitely an option. But we’ve decided to subscribe to Raygun anyway for our web and mobile apps and as it’s all about crash reports and analytics the small price difference (Raygun is less than $50 per month) puts Raygun in front for us.

Without really knowing what Raygun was, strange imaginations came to mind when reading the subject. Mainly the movie “Mars Attacks” and for a moment, my brain was trying to decide how Xojo would fit into the mechanics of an alien weaponry (there are rifles that are linux powered, for the automatic adjustment of the scope).

I’m expecting you cant get crash reports from Raygun for Xojo apps either since it cant integrate into the built app in the way I think it would need to to be able to do this

If you sell your apps via the App Store, you get the crash reports; you have to manually log into iTunes Connect and download them. I don’t know if it only collects reports from App Store signed apps or if this includes all signed versions.

I reached out to Raygun yesterday and they replied that using their REST API will provide almost the same functionality as using one of their pre-built library integrations but, yes, I agree Norman that I won’t get Xcode-style crash reports this way. However I can get these in Xcode so they aren’t my main problem. The main problem I have is that the stack trace I get in the app’s UnhandledException event is logged but users don’t always send it to me. I want a way to submit it automatically.

You also get them in Xcode without the need to login to iTunes Connect and download them.

Airtable can do more and i think it’s even cheaper, but it’s not special to crasg reports it’s more a dbspreadsheet-form-tool to make it easy.

Yeah I could write a web service to receive my stack trace and save that into a spreadsheet or a database, etc, but I value the specific crash report related functionality and reports over the generic spreadsheet paradigm for this purpose.

Haven’t watched the webinar, yet. But why would I use a spreadsheet app for crash reports?

I simply let my users send me the crash reports via email… When there is a Xojo crash the reports are collected and sent. When there was a hard crash at the next start the app checks if there are more crash reports and offers to send those. Is this too simple?

I like that approach and I do that now but I get very few crash reports using the optional email method so I want to automate it.

you will want a way to save the “crash” info locally if the user doesnt have internet access at the moment, and send later when they do. For instance about 50-60% of my time I am either no network (including Internet) access or have a company intranet access but not Internet access. Like when I am standing in a data center configuring storage arrays. so in those times if you dont save the crashes for later sending, you will loose the data.

would love to see how you integrate Xojo with Raygun.