| Age | Commit message (Collapse) | Author |
|---|
|
|
|
I've copied all files containing "danger" to both release and debug java folders (solution learnt from http://stackoverflow.com/questions/18782368/android-gradle-buildtypes-duplicate-class), and removed every trace of any "danger" related code in the release apk.
This way, we make sure nobody can exploit that unused variable in production mode, so that if Android fails to protect our app (people have been able to introduce code into signed apks, so it's not impossible), we make it difficult to bypass the SSL certificate verification. You can call me paranoid if you want ;)
|
|
New provider dialog resources use danger_on checkbox in debug, but not in release.
This kind of solutions forces us to maintain 2 different codebases for the same class, so beware for next updates.
Next step: split java code.
|
|
|
|
I ignore that file, it contains passwords, although I have encrypted it to myself.
|
|
This way, gradle commands generate apks correctly named.
|
