| Age | Commit message (Collapse) | Author |
|---|
|
Forgot to add the menu for the log.
Now we'll strive to fix se.leap.bitmaskclient problems: first compilation, then functionality.
|
|
api folder and aidl files aren't needed for us. They are used for
external apps that want to use ics-openvpn as an already installed
package, while what we want is to avoid the installation of ics-openvpn
including it (refactored) in bitmask android.
|
|
|
|
Now we need to decide what's our relationship with LogWindow and
LaunchVPN, refactor its classes and fix ours so that we use the
currently supported methods.
|
|
|
|
I'm hardcoding their values based on the compilation errors (i.e., the
drawables referenced by de.blinkt.openvpn.core.OpenVpnService). If a new
drawable were introduced, build.gradle should be updated accordingly.
|
|
I privilege ics-openvpn translation to ours. If we need to change
something, we can introduce a new xml element without any future
compatibility problem with ics-openvpn.
|
|
|
|
WARNING: there are still compiling errors, related to BuildConfig and R
classes in de.blinkt.openvpn
|
|
imports from se.leap.bitmaskclient java files have also been updated.
WARNING: compiling errors for de.blinkt.openvpn.R, aidl.de.blinkt.openvpn.
|
|
|
|
|
|
|
|
Functionality copied to the Release build.
|
|
This has the problem of localized messages. irc log questioning:
May 8th 2014
08:12 <@parmegv> mm, I was thinking... I was rephrasing the error messages given by our api during authentication
08:13 <@parmegv> I thought why should I rephrase it and think twice
08:13 <@parmegv> so now I'm just "pretty printing" the error message given by the api
08:13 <@parmegv> but that has a problem: they aren't localized
08:14 <@parmegv> would implementing a localized version of our error messages be useful?
|
|
A bit of refactoring too, sendM1 much simpler.
|
|
|
|
There is some problem in the maths, because the server says it's ok but
login doesn't work from Android app nor from webapp.
|
|
|
|
|
|
|
|
|
|
'bug/provider.json-isn't-downloaded-without-danger_on-set-to-true-#5568' into develop
|
|
release apk is not working ok with proguard.
|
|
Removed the default danger_on = true in the debug build.
|
|
|
|
|
|
This fixes https://leap.se/code/issues/5556
|
|
|
|
|
|
|
|
Notifications get mad, we have to fix that.
|
|
|
|
Next step: don't restore off status!
|
|
|
|
|
|
The test that checked how many providers were listed was failing
because this test added dev.bm.net, which was already present in the
debug apk, so no new provider was added.
|
|
You have to edit a gradle.properties file with the following structure:
storeFileProperty=fullPath
storePasswordProperty=store password without quotation marks
keyAliasProperty=key alias without quotation marks
keyPasswordProperty=key password without quotation marks
|
|
|
|
|
|
If you choose one and then tap "Switch provider" button, no duplicated providers are shown.
|
|
This return to "app" instead of "bitmask_android" is due to this reading: https://developer.android.com/sdk/installing/studio-build.html#projectStructure
I'll have to tweak the final apk name in build.gradle.
|
|
This way, gradle commands generate apks correctly named.
|
|
|
|
|
