IssueTracker

uwb library has two places right now where it uses Log.e (see below). In once case it silently ignores that failure and in second it throws a generic RuntimeException.

• https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:core/uwb/uwb/src/main/java/androidx/core/uwb/impl/UwbManagerImpl.kt;l=136
• https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:core/uwb/uwb/src/main/java/androidx/core/uwb/impl/UwbManagerImpl.kt;l=90

Instead of doing that, please have proper error handling (see https://g3doc.corp.google.com/company/teams/android-api-council/guidelines/index.md?cl=head#return-error). We should only throw exceptions when it is the library users' fault in how they use the library.

Additionally, we should also really avoid using Log.i as well, it is logcat spanning without much additional help. If you really need it for local iteration, added const val DEBUG = false and flag check all these printouts through out the library.