How to debug mobile apps on production?

Posted by Alice Gajos

Debugging mobile applications puts specific challenges on developers. Some of them are correlated with limitations of individual mobile platforms. Other with specifications of devices, on which application will be deployed. It’s no surprise that developers of mobile applications constantly look for solutions that allow them to take care of QA in the best possible way. Due to this demand in recent years some new debugging techniques have appeared. One of them is reverse debugging.

How reverse debugging changes the game?

Could you imagine that all data about the bug could be sent from the client device right to your debugger? All events, values, exceptions, which led to a crash? These are the possibilities which the reverse debugging gives you. Check this infographic, and this article where we are explain this idea in more depth.
Getting back to the question raised in the title of this article, how to use reverse debugging in your mobile applications? There is one simple way to do it. You can build your application with RevDeBug. This Visual Studio extension is a reverse debugging tool, now also available for mobile, Xamarin applications.

What about performance?

Imagine that you record a few hours of your product running on thousands of your client machines. Do you really need the whole recording from every device? Or perhaps you would like to receive the information only about sessions when something went wrong? It turns out that you only need the last few minutes, the few thousand events, that led directly to a crash. The newest RevDeBug version 4.5 gives you that ability also on Xamarin apps!

Crash Recording - How to use all the best that RevDeBug offers without performance loss for you and your clients

RevDeBug is an extension created by developers for developers, that’s why our team loves to hear your feedback about it. Crash Recorder is one of those improvements, that were made to meet our customers needs. This newest feature of RevDeBug gives you:

  • Smaller file size - shorter recording equals a smaller file size. Smaller file size means less internet bandwidth used.
  • Record only what matters - you rarely need to record the whole session of running an application. With Crash Recorder you can record only what lead to a crash.
  • Send only what matters - In a standard reverse debugging session your application is incessantly sending data about its state. The Crash Recorder connects application to server only when crash appears.

There is only one downside: you may get addicted to using Crash Recorder!

What are you waiting for?

Download for free


Submit a Comment