| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Clean up some tests.
--
MOS_MIGRATED_REVID=103600539
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103068396
|
|
|
|
|
|
|
| |
This is because apkbuilder uses $HOME/.android/debug.keystore by default, which does not exist when running within the sandbox, thus, it always generates a new debug key, and thus, "adb install -r" doesn't work.
--
MOS_MIGRATED_REVID=102331570
|
|
|
|
|
|
|
| |
Fixes #419.
--
MOS_MIGRATED_REVID=102248331
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that Bazel finds Android tools and update the tools themselves to handle their new location.
This paves the way for eventually referencing every tool this way.
We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.
This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.
Fixes #384.
--
MOS_MIGRATED_REVID=101456190
|
|
|
|
|
|
|
|
|
| |
(only for devices with Android M).
Until now, we always reinstalled every split .apk. It was simple, but also not very fast.
--
MOS_MIGRATED_REVID=101120400
|
|
|
|
|
|
|
| |
not supported in the app to be installed.
--
MOS_MIGRATED_REVID=101004548
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100655790
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99567637
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces a new way to stop applications when deploying incremental
changes that saves the current app state for the next run. This allows things
like the back stack, and View/Fragment/Activity saved state to be restored when
the app next launches, making it easier to quickly iterate on code changes.
It adds a "--start" flag to mobile-install that replaces "--start_app".
--start accepts an argument describing the mode: no, cold, or warm. "no" is
now the equivalent of "--nostart_app", "cold" is the equivalent of
"--start_app", and "warm" is the new start mode.
Note that this is only useful with incremental installs, as Android clears out
any previously saved state when an APK is replaced.
--
MOS_MIGRATED_REVID=99508790
|
|
|
|
|
|
|
| |
This makes things a bit more robust.
--
MOS_MIGRATED_REVID=99464712
|
|
|
|
|
|
|
| |
installing native libraries.
--
MOS_MIGRATED_REVID=99257598
|
|
|
|
|
|
|
| |
This stubs out all Android support, but that's okay, because in order to test Android stuff, we need a way to get the NDK and the SDK somehow, which we don't know yet how to do.
--
MOS_MIGRATED_REVID=97222940
|
|
|
|
|
|
|
| |
and aar_generator.sh to the tools directory and make stub applications proper android_library rules instead of stub filegroups.
--
MOS_MIGRATED_REVID=97206853
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96883818
|
|
|
|
|
|
|
|
|
| |
actually work. This is a temporary measure until these targets are integrated into android_sdk .
Also make handling invalid tools/android/jack packages in JackCompilationHelper a bit more robust.
--
MOS_MIGRATED_REVID=96202009
|
|
|
|
|
|
|
| |
Note that despite the rule being present, Android support is still not functional: two tools (//tools/android:{aar_generator,resources_processor} are still missing (and are a-coming!)
--
MOS_MIGRATED_REVID=96099045
|
|
|
|
|
|
|
|
|
|
|
|
| |
BazelRuleClassProvider:
- Add stub targets to tools/android/BUILD
- Make Constants.ANDROID_DEFAULT_SDK non-constant so that the classfile can be replaced in the .jar
- Make AndroidTools complain if --android_sdk does not point to an android_sdk rule.
- Make the default visibility in the BUILD file generated by android_sdk_repository public
--
MOS_MIGRATED_REVID=95816158
|
|
|
|
|
|
|
|
|
| |
I noticed this while testing --split_apk: sometimes APKs would be duplicated on the command line, and simply removing "argv" from "FLAGS(sys.argv + [line.strip()...)" in line 558 would sometimes cause a --adb_arg argument to be lost.
This seems to work for all cases.
--
MOS_MIGRATED_REVID=95715369
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=94515805
|
|
--
MOS_MIGRATED_REVID=94198797
|