Description and screenshots of end-user side

gligoran

Posted on
Apr 24 2013

Hi!

I've just learned about this tool today from your email and it looks great.

I was just wondering one thing - how does the end user see this? Is just hidden in code and he/she doesn't even know that the application is sending error reports back to Raygun.io or do they get some kind of a popup?

Thanks for the answer and keep up the good work :)

-- gligoran

John-Daniel Trask

Raygun

Posted on
Apr 26 2013

Hi Gligoran,

The user doesn't currently see anything -- it's just in the code.

You could always update your unhandled error page to include a note that you've recorded the error and will be looking to fix it :-)

I hope that helps and thank you for the kind words!

John-Daniel Trask

gligoran

Posted on
Apr 26 2013

Thanks John-Daniel, now I clearly understand what your service actually does. It's not a yet another bug report service, as I understood earlier.

I do have another question, though. Is this meant only for online/web applications or do you support offline applications as well? How do you handle sending an exception report if the application doesn't have internet access at the moment when the exception occures?

--gligoran

John-Daniel Trask

Raygun

Posted on
Apr 29 2013

Hi Gligoran,

Raygun is built to handle both types of applications. The smarts for handling an offline application (or at least a 'partially connected' system) is handled by the provider.

For example, if you used the .NET provider with a Windows Phone app, it will check if a connection is available and, if not, simply store the crash report. Next time the app is run it will quietly check if there is a connect and, if so, send the report then.

We're constantly improving all our providers so if you have a particular provider you want to use in that scenario please let me know and I can tell you how it's doing this.

I hope that helps,

John-Daniel

Reply