Good news for debugging database in mobile phone: Android-Debug-Database

Currently, debugging apps in the browser is becoming more and more popular.

For example, Facebook's open source tool Stetho allows Chrome to debug Android.

This article introduces an open source project "Android-Debug-Database".

He can debug the DB in the browser

It involves "getting data - starting service - remote call", I hope it will be useful to everyone

Preface

Generally, it is very troublesome to debug the database in the mobile phone. Generally speaking, there are several ways to do it:

Export the SQLite database in the mobile phone to the computer, view the database through the computer software, execute the relevant SQL statements, and see the results.

Root your phone, install RE File Manager on your phone, go to the application package, find the file of your database, and then check the database.

Android Studio has related plug-ins, which makes operation convenient, but some of them require payment and are not very pleasant to use.

Now, AMIT SHEKHAR has open-sourced Android-Debug-Database. With this library, we can easily view the database through the browser and execute SQL statements. Isn't it great!

feature

1. You can view all databases in your application.
2. You can view all shared preferences of your application (extra benefit).
3. Executes a SQL statement against the database you specify.
4. Visually edit the data in the database you specify.
5. Download the database directly.

How to use

Add the following to your build.gradle: debugCompile 'com.amitshekhar.android:debug-db:1.0.0' The function of debugCompile: It only works when you debug compile. There is no need to use it when you release.

That's it, you don't need any other code.

Next, when you start the App, you should check your logcat, there will be a line like this: D/DebugDB: Open http://XXX.XXX.X.XXX:8080 Copy it to your computer's browser, you can see the database in your App and shared preferences

The interface is as follows:

principle

The overall structure is as follows:

DebugDB starts a thread for your application:

This thread continuously processes requests from the browser (Socket form)

According to the content sent by the Socket, it makes judgments: according to different requests, it processes and returns different results:

Others: Where does the content in the browser come from? Why can it send request data? debug-db sends interactive HTML to the browser:

The interactive capabilities of the browser are based on HTML and JS. These designs involve front-end knowledge. Let's talk about it when we have time.