Eric Seidel
Eric Seidel
Maybe just always require `shorebird` to auto-update? Our system is designed so that a newer `shorebird` should always work with an older `flutter` (but not the other way around). It...
Moving to our own tokens would make it so we can: 1. revoke them (and give them lifetimes, etc.) 2. vend them from console.shorebird.dev Right now our CI instructions ask...
I'm not sure why. And I'm not sure if it's always done this, or only recently. But when I use `shorebird preview` to install an iOS app, it hangs on...
Right now collaborators are per-app. I expect some customers are going to want to add collaborators on a per-account, or per-team basis. When we get such a request, this is...
Currently if a patch fails to boot we will crash the app. I suspect we don't need to do that. I'm not entirely sure how hard it will be to...
Right now if you publish a patch to Android and then a patch to iOS (for the same app), they will end up with patch number "1" and "2" respectively....
Probably the correct solution is to create groups or orgs or some other way to add collaborators rather than per-app/per-flavor. But stating the user journey, what the user is trying...
Request from a customer: > Is it possible for us to be able to view the cumulative total installs for a particular patch rather than only being able to view...
Some users don't install Flutter directly, rather they use fvm. So `flutter` isn't even on their path, just `fvm` is and they might then use a shell alias to map...
Also fixed the various typos I found.