hi, recently i updated my flutter sdk to 3.35.3.
when i try to make a release, an error appears even though I have updated the flutter version in the workfile
#failed run shorebirdtech/shorebird-release@v1
hard bridge
dire swan
I don't know if this is the cause of the issue, but you should remove the --, or at least put --flavor to the left of it
hard bridge
I don't know if this is the cause of the issue, but you should remove the `--`, ...
Hmm it worked well before, and it is necessary if you look at the documentation.
dire swan
Hmm it worked well before, and it is necessary if you look at the documentation.
--flavor needs to come before the -- because shorebird needs to do more with that argument than just forward it to Flutter (although we do that as well).
hard bridge
Hi, I just figured something out — the Flutter SDK being used is 3.35.4-0.0.pre-17, while I’ve defined 3.35.3 everywhere. Could this be coming from the Shorebird side?
I also tried moving the --flavor argument before the -- separator.
hard bridge
Oh, was there an issue?
hard bridge
Let me take a look
Thank you
dire swan
Yeah. The way Flutter determines its version doesn't play nicely with forks. Let me see if I can find the issue and the relevant PR
So it looks like you're on 1.6.66, which is our latest version
A quick workaround would be removing the flutter version from your pubspec if you're needing to get something out now
But that's not the long-term solution we want
Give me a minute to dig in
hard bridge
Alright, thank you — appreciate it! I need to publish because the 16 KB deadline is only a few days away 😅 .
Hmm, maybe it would be a good idea if Shorebird supported defining the Flutter version from a file, similar to https://github.com/subosito/flutter-action
dire swan
We could definitely respect what is in the pubspec.yaml
we also allow the specification of a flutter version using the --flutter-version argument
It looks like you're using that though 🤔
Ooooooo I bet the issue is that we didn't have that fix in the Flutter version you're using
Yeah, it looks like that was introduced with 3.35.4
So you can either upgrade your app's flutter version or just temporarily remove that from your pubspec file
hard bridge
Yes, i just removed the Flutter version from my pubspec.yaml because I didn’t want any issues to occur if I did an upgrade.
It worked