Fixed
Status Update
Comments
jg...@google.com <jg...@google.com>
je...@google.com <je...@google.com>
lu...@google.com <lu...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ev...@gmail.com <ev...@gmail.com> #3
Almost 2 months later and this is still broken
lu...@google.com <lu...@google.com> #4
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
ev...@gmail.com <ev...@gmail.com> #5
jb...@google.com What is the update on this?
lu...@google.com <lu...@google.com> #6
What is the status of this item?
Description
The short version: there's no error raised for something like this:
#0xFFBB86FC
is not a valid hex code, and should not be allowed to be compiled. Instead, the app compiles successfully and fails at runtime. I've made tiny little demo app here: