Niagara-Issues
Niagara-Issues copied to clipboard
Widget Disappears/Missing since 1.10.x
Describe the bug
After the Anycons update the Google search bar widget doesn't last more than a couple hours before just disappearing and leaving a search bar sized gap in it's place. Removing and re-adding the widget temporarily solves the problem but it always disappears again...
Note using Android 14 but wasn't an option in the drop down.
Steps to reproduce
- Add Google Search bar widget to Niagara (either above or below the clock, doesn't matter)
- Use phone as normally
- Wait
- Poof 💨
Does the issue also occur with other 3rd-party launchers?
Problem doesn't occur with other launchers
Other 3rd-party launcher(s) tested
No response
Device name
Google Pixel 7 Pro
Android version
Android 13
Screenshots / Screen recordings
You can see Niagara believes the widget is there but it does not render. Tapping it as if it was there does nothing.
Hi there,
Thanks for reporting this issue. We are aware of it and are currently trying to fix it. Sadly, it's difficult to reproduce and seems complicated, so resolving it might take a while.
We will keep you updated.
(Also, thank you for pointing out that Android 14 is missing from the selection. I have updated the template)
I'm currently having the same issue with a different widget. Lmk if you need to perform any test once you understand how to trigger it.
Device name
Google Pixel 6a
Android version
Android 14
Kris from HelpScout reported a similar issue, where only part of the widget disappears:
The widget is a Google Maps widget
I've noticed that force stopping Niagara and allowing it to relaunch is a quick fix, it brings the widget back for a while quite reliably.
Same issue here with Android 14 Widget smart suggestions ("Suggestions intelligentes" in French) except that remove and add Widget doesn't work and restart Niagara neither.
Samsung s21ultra, One UI 6.0 Android 14 niagara 1.11.5
I wanted to check in and see if the recent update of Niagara v1.12.2 has fixed the issues you were experiencing.
Actually it hasn't happened in a while so I guess it has been actually fixed in one of the latter updates. Thanks for the heads-up!