-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update pubspec #169
Update pubspec #169
Conversation
I also rebased device_calendar on the latest devel, but I will leave that for another time (and branch), since it's a lot of fixing null safety after their rewrite among other things https://github.com/hellcp/device_calendar/tree/rebble And maybe if the upstream is fast enough, we can get that merged and get a release with those changes soon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Static analysis finds problems in app in test, check out "Dart Analysis" tab in IntelliJ or log from CI
44ed8e9
to
d04825e
Compare
I'm switching this to draft since I noticed breaking change of not being able to connect to the watch anymore (which is pretty useful) |
696b560
to
52bd589
Compare
When I first installed an app from this branch, I was able to pair to a watch, but sending pings and test notifications did not work. I then added a tiny bit of logging to the Android layer, installed the new APK (no hot reload), and sending pings and test notifications started working. I'm not too sure what to make of that, but at least it's not entirely broken. It's also worth noting that I did not have any watch connection issues with #201 |
I should come back to this branch at some point to test it again |
Most of the changes are from riverpod, from the following change: rrousselGit/riverpod#341
There were also slight changes in Uuid, but they are more obvious
The dependencies blocked by other dependencies were marked