-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Robot building and working again. #2598
Conversation
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.
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. |
No description provided.