Obsolete
Status Update
No update yet.
Comments
lb...@gmail.com
P.S. Actually we cannot running Instrumented Test when using NavigationUI.
When initialize the AppBarConfiguration, it will call the final method of NavGraph (findNode) and we cannot mock it.
When initialize the AppBarConfiguration, it will call the final method of NavGraph (findNode) and we cannot mock it.
lb...@gmail.com
I also ran into this today while trying to add a FragmentScenario test. Followed the testing documentation and arrived at the same place. AppBarConfiguration attempts to interact with NavGraph and crashes.
ja...@google.com
Yep, we should have a better testing story that doesn't depend on using mocks.
yt...@gmail.com
One and only solution is to use Mockito in Espresso tests. Which is actually is almost equal to no solution. We strictly do not use Mockito in our integrations tests running on devices because that is very fragile and causes huge amount of issues when using on different SDK versions. This makes Navigation lib no go for us.
So current situation:
- Navigation library is already released with stable API.
- API is created without test-ability in mind. Huge classes with large amount of public methods, no interfaces. Using such tools as Mockito is not a solution, but workaround for situations when API is not testable.
After 10 years of creating un-testable Android SDKs there was possibility to have clean slate opportunity. And here we go again. API released and needs to be maintained now. Please recognize this problem now and bump priority from lowest (P3) to something higher. Because until we won't have possibility to test our app navigation flows we can't use this library.
So current situation:
- Navigation library is already released with stable API.
- API is created without test-ability in mind. Huge classes with large amount of public methods, no interfaces. Using such tools as Mockito is not a solution, but workaround for situations when API is not testable.
After 10 years of creating un-testable Android SDKs there was possibility to have clean slate opportunity. And here we go again. API released and needs to be maintained now. Please recognize this problem now and bump priority from lowest (P3) to something higher. Because until we won't have possibility to test our app navigation flows we can't use this library.
lb...@gmail.com
We'll be releasing a dedicated navigation-testing artifact in Navigation 2.3.0-alpha01 that provides additional testing specific APIs
This work includes:
https://android-review.googlesource.com/1180272 https://android-review.googlesource.com/1182957 https://android-review.googlesource.com/1187078
Among other changes.
sa...@google.com
at...@google.com
Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete.
og...@gmail.com
Is there a chance this feature could return for Android 15 as an option that may be off by default or at least in the developer settings? iPhones now have this feature while Android 9 (clear) / 10 (forced blur) was the last version with it.
Description
I hope I'm wrong in this understanding as I didn't see it written on any article so far, including of Google.
But if I'm right in understanding what Google says, please consider this alternative instead of a complete removal:
Add a preference on the "privacy" settings, right below "notifications on lock screen", to let user who do want it being shown:
"show album art of player apps".
The options would be "disabled", and "enabled".
Once enabled, a new preference would appear to allow to set the amount of blur for the album art image, with demonstration of how much it can get blurred.