eclipse - Debugging on an Android device after first release -


now android app released on google app store, continue developing , debugging on device.

i have few options:

  1. delete app device , install new version during development.
    • this has disadvantages. lose local files saved released app, and, when time comes next release, not share same experience users while upgrading.
  2. introduce minimal change by, say, renaming package. 2 apps distinct , can co-exist on device.
    • this introduces superfluous change in souce tree, headaches that entails.

if have avoided these difficulties, approach have taken when continued develop after release?

i recommend switching android studio , gradle. using build types (which can't link because n00b , have no reputation), can switch between debug , release builds, , set build file have both on device @ same time without changing in source or manifest.

the 1 big gotcha failed understand , bit me in butt several times until got in build variants tool window, selected build variant controls everything. if choose release variant:

  • when build, build apk release keys (if you've set them in build files)
  • when run app, put release version on device
  • if try debug app, debugger not attach because app not debuggable

and of course reverse if select debug build variant.

you have give eclipse, if you're me sad thing, i've heard they're planning add gradle support eclipse @ point.


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -