#[WARN] shorebird patch was only able to share 33.0% of Dart code with the released app
1 messages · Page 1 of 1 (latest)
1.1.15
@halcyon surge
We have been working to improve link percentage, you can follow our progress through this github issue: https://github.com/shorebirdtech/shorebird/issues/1892
Can you provide a reproduction sample or describe the changes you made in the patch?
This should be significantly improved for builds made with Flutter 3.22.2 (which is the default for 1.1.15)
Are you using Flutter 3.22.2 or something earlier?
is using different version of shorebird effecting the linking percentages? i'm getting is 28 something percent when patching ios, which is bad. the preview is laggy and my FAB is missing for some reason
i'm using v1.1.13 for the release and v1.1.16 for patch.
I have the same problem, I did not even add much load of code. Just 12 lines across 2 files
The Flutter version is what matters. (Shorebird uses its own copy of Flutter, but following the version you specify.). By default we will use the latest stable Flutter which is Flutter 3.22.2 with Shorebird 1.1.16.
It used to be a common problem for the link percentage to be low.
You’ll need to re-release using the latest flutter revision in order to benefit from the link percentage improvements since we always build the patch using the same revision of flutter as the release
We believe we've solved that as of the last two releases (Flutter 3.22.2 + Shorebird 1.1.15 and Flutter 3.22.2 + Shorebird 1.1.16)
I have a similar problem. I use the Flame library and perform many computational operations. I noticed a problem on iOS with rendering the glow and fast animations.
Looks like you're not using the latest stable flutter revision. Can you try re-releasing with the latest revision of 3.22.2 (shorebird upgrade and shorebird release ios) and let us know if you're still experiencing performance issues?
We had a bug where functions using "double" would sometimes get corrupted doubles in patched functions (this bug was about a year old, but only recently surfaced due to other changes in the dart vm). This was fixed in the 3.22.2 we released on Tuesday of this week.
So you'd need to make a new release with 3.22.2 to get the fix unfortunately.
corrupted doubles = wild unpredictable values for things like animations ðŸ˜
this is pre-alfa
bu this build is compile on 3.22.2
and work better when i realese on testflight
but i try tomorrow
We make multiple releases for a given flutter release. Flutter released 3.22.2 about a month ago, and we've released maybe ~5 versions of 3.22.2 since. Any new release will always use our latest 3.22.2, but a release made a week ago with 3.22.2 will have an older version of our 3.22.2 fork than one made today.