Skip to content

Comments

Get Robot building and working again.#2598

Merged
pmuetschard merged 11 commits intogoogle:masterfrom
pmuetschard:robot
Feb 15, 2019
Merged

Get Robot building and working again.#2598
pmuetschard merged 11 commits intogoogle:masterfrom
pmuetschard:robot

Conversation

@pmuetschard
Copy link
Member

No description provided.

@AWoloszyn
Copy link
Contributor

Other than style nits, the only thing I want to comment on is that I think how we package up OBB files for Robot will have changed.

Now it is expected that you EITHER pass a .apk file down in this call OR a zip file that contains your your .apk + .obb files. This way everything can be in a single file.

It's nil and causes a panic.
Return the host's binaries in case the ABI is nil.
The error cannot possibly be non-nil at that point.
If given a URI of the form `apk:<file>` it will send the APK to the gapis
to be installed on the device and traced.
This is how it used to work for automated scripts.
This way the tracing logic for an newly installed app will "just work"
as if the URI had been specified in the request.
@pmuetschard
Copy link
Member Author

re: obb - if put in a TODO and made robot return an error if a subject with an OBB is attempted to be traced. If we actually want OBBs again we can fix robot to properly package them, or fix gapit to do it for robot.

@pmuetschard pmuetschard merged commit 5f46206 into google:master Feb 15, 2019
@pmuetschard pmuetschard deleted the robot branch February 15, 2019 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants