Andrew and Greg, if you'd submit a ticket to us via the link at the top of the page, we can send you a debug build to try.
There are many factors involved in the update and without debug info it's difficult to know where the failure is happening.
When I reboot my phone, it updates the widgets one time, and that's that. For example, I have the widget for Google Fit on my home screen, and it is still showing the status from a couple of days ago; when I rebooted my phone.
I tried the Android N beta some time ago (I can't remember if the widgets updated then though). But I'm guessing the Android N beta has nothing to do with my problem? Are there some settings that I could have executed that froze my widgets?
But after a time the widget would probably crash or something (not visible though), and other widgets stopped too.
So the best solution for me was: This happened to me quite time ago.
I really like the look and feel of the the app, but it's not much use to me personally while the widget isn't updating.As I already mentioned, I'm using a Motorola Nexus 6 with stock Android 6.0.1 on it.I have all the latest version of the Android version for my phone, and have installed all security patches.Our developers are working on some logic for the app so that it will try again.The new update should be available in the next few days.But because there were some problems with applications I use daily, I reverted back to my old Android 6.0.1 build. Maybe something with battery optimizations or something?I don't have to mention to you that widgets that aren't updating are very annoying.Including the July security patch from a couple of days ago. I don't have any special applications running that should customize my battery behaviour (like Greenify). So I got into the Android widget documentation to find out what made the widgets tick. So I found out, that one widget can actually block the updating of the other widgets. So by adding every widget seperately, with a lot of time in between, I could notice that the problem occurred after a while.The time in between was rather important, because if I did it immediately there was no problem.This seems like a pretty key function of a weather app.The way the app is currently configured, if an update fails - for example if the signal is bad, Wi Fi is unavailable, you're on the phone, etc., it does not try again, but it does update the time it tried the last update - so in some instances though the update time is current, that's not the time of the last successful update - just the last time it tried.