Status Update
No update yet.
Comments
en...@google.com
da...@google.com
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
gw...@gmail.com
what m126 bugs could this report be a duplicate of ?
Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in
But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in
Re #1,
Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:
- Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "
b/360530624 - Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?
Thanks!
gw...@gmail.com
This might be a dup of the internal bug of
As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!
da...@google.com
da...@google.com
Bugjuggler: wait 8w -> hugobenichi
gw...@gmail.com
gw...@gmail.com
It is still happening, so I will report the next instance with the requested text. It doesn't happen on a specific network, but all networks I am connecting to. It's not repeatable on other non ChromeOS devices in at least two of those, but is repeatable on the exact same device of another owner. I can ask them to also report with the reference number if that is helpful. Let me know if I can provide any additional information or troubleshooting.
I am out of the office for a few days this weekend, but should be able to repeat issue by eod Monday.
Description
Bug report
Hello. I was working on creating an app that makes use of the NDK. I need openSSL for cryptographic functions. Long story short after troubleshooting for an insane numbers of hours, I decided to create a blank NDK project and install openSSL there, then slowly add stuff to the test project until it broke so I could narrow down the issue.
Much to my surprise, a fresh install of OpenSSL in a fresh NDK project still does not work. Trying to do so yields the following error
Upon inspecting the apk, libcrypto.so is indeed missing from the lib folders for every architecture.
Steps to reproduce
module:appbuild.gradle, add the following dependency:prefab trueto thebuildFeaturesin the same file.target_link_librariesTesting
Now that you've got your test project setup, perform a gradle sync if necessary and run the app. You will get an error. Navigating to log cat you will get the error listed above. If you open the debug APK in android studio, you will see libcrypto.so is nowhere to be found