Package Details: flutter-artifacts-engine-web-google-bin 3.41.2-3

Git Clone URL: https://aur.archlinux.org/flutter.git (read-only, click to copy)
Package Base: flutter
Description: Flutter SDK component - web engine
Upstream URL: https://flutter.dev
Keywords: android fuchsia ios mobile sdk
Licenses: custom, BSD, CCPL
Groups: flutter
Conflicts: flutter-engine-web
Provides: flutter-engine-web
Submitter: flipflop97
Maintainer: WithTheBraid
Last Packager: WithTheBraid
Votes: 151
Popularity: 0.021404
First Submitted: 2017-06-05 21:03 (UTC)
Last Updated: 2026-02-22 06:08 (UTC)

Required by (1)

Sources (43)

Pinned Comments

WithTheBraid commented on 2025-11-11 10:15 (UTC)

This package is deprecated in favor of aur/flutter which now contains all required artifacts on its own. This PKGBUILD will be kept as is in order to ensure seamless builds of old Flutter version in future.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 28 Next › Last »

ipoulakis commented on 2024-04-04 10:01 (UTC)

I got past the "Your Flutter SDK download may be corrupt" message on Manjaro by creating a symlink from /opt/dart-sdk-dev to /opt/dart-sdk.

But now I'm getting a "Unexpected Kernel Format Version 114 (expected 116)" error when trying to run a new test project.

y0uCeF commented on 2024-04-03 22:23 (UTC)

I met the same issue as @StrontiumK9:

Your Flutter SDK download may be corrupt or missing permissions to run. Try re-downloading the Flutter SDK into a directory that has read/write permissions for the
current user.

leo72 commented on 2024-04-03 15:27 (UTC)

Same of StrontiumK9 for me. flutter doctor doesn't see any issue on my installation but flutter doesn't even create a new project from terminal, printing that error. Obviously, I got to my user r/w permissions for flutter at /usr/lib/flutter

StrontiumK9 commented on 2024-04-03 10:29 (UTC)

I just installed 3.19.5-7 with Yay and didn't see any of the reported issues. But I can't run flutter once it has been installed. flutter pub upgrade in my project just complains: "Your Flutter SDK download may be corrupt or missing permissions to run. Try re-downloading the Flutter SDK into a directory that has read/write permissions for the current user."

Is there some post install work I need to do to get it to work?

WithTheBraid commented on 2024-04-02 14:32 (UTC)

@ajje Yeah, really sad. I wished I could resolve the problem. Yay btw. isn't in an infinite loop, bu "only" builds the package 15 times - if you are very patient, yay can hence install it.

About paru, I already consider writing a patch to the upstream running pacman interactively - because the build process works way faster using paru.

Alternatively, I'm working on pre-built packages for those who don't wanna manually build them, the progress can be found on the GitLab mirror of this repo, at https://gitlab.com/flutter-archlinux/tool/-/merge_requests/1 .

ajje commented on 2024-04-02 14:16 (UTC)

@WithTheBraid Thank you for your detailed explanation and your patience. Yes, now yay asks if you want to remove the old flutter package, but it still doesn't work for me because I get stuck in an infinite loop trying to build the package. That's why I tried paru, but as you correctly point out, it runs pacman non-interactively.

I see now that some users has suggested uninstalling Flutter manually then doing a clean build with paru. I'll try that. Thanks again for all that you are doing for us lazy users of AUR helpers.

WithTheBraid commented on 2024-04-02 12:28 (UTC)

@ajje This is intended. Both yay and paru are sadly not able to first build all packages and install them at once (as pacman -U or pacman -S would do). This is not my fault.

I hence added the conflicts list removing the previous installation in order to make the update work. Using yay, this works. You simply have to accept yay removes the stated packages. paru sadly does not allow that since it tries to run pacman non interactively (I don't get why tho).

Again, these are bugs of AUR helper - it should not be the task of AUR package maintainers to do nothing but workarounding issues of the helpers failing at dependency resolution.

Feel free to open a ticket in paru asking to fix that - as people already did with yay.

ajje commented on 2024-04-02 12:17 (UTC)

I've tried installing with both yay, and now paru but I get conflicting dependencies:

==> Finished making: flutter 3.19.5-7 (tis  2 apr 2024 13:55:06)
==> Cleaning up...
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
loading packages...
resolving dependencies...
looking for conflicting packages...
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict. Remove flutter? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: flutter-common-3.19.5-7 and flutter-3.19.4-5 are in conflict (flutter<3.19.5)
error: packages failed to build: flutter-artifacts-google-bin-3.19.5-4 (flutter-sky-engine-google-bin flutter-material-fonts-google-bin flutter-engine-common-google-bin flutter-engine-linux-google-bin)  flutter-3.19.5-7 (flutter-target-linux)  flutter-artifacts-google-bin-3.19.5-4 (flutter-engine-android-google-bin)  flutter-3.19.5-7 (flutter-gradle flutter-target-android)  flutter-artifacts-google-bin-3.19.5-4 (flutter-engine-web-google-bin)  flutter-3.19.5-7 (flutter-target-web flutter-intellij-patch flutter)


WithTheBraid commented on 2024-04-01 08:47 (UTC)

Thanks for the feedback about the AUR helpers failing at the version upgrade. This is caused due to the split package across two pkgbase repositories - the helpers do not seem to see that the final builds provide each other with all requested versions. Likely that's an edge case no one considered when writing an AUR helper.

As a workaround, I patched the conflicts sections of all packages provided here in a way that they force an uninstall of the previous version group in order to upgrade. That's a bit sad and inefficient but looks like no AUR helper copes with the upgrade in case we don't.

In all cases, building the two pkgbase repos using makepkg -s[fC] and a manual installation of all output packages using pacman -U works. Sad no helper reaches there.

silikeite commented on 2024-04-01 06:06 (UTC)

Regarding the issue also encountered by xAsh and nameless, currently it is impossible to update Flutter without uninstalling, clean building (or in paru's case deleting the cache for Flutter), and reinstalling.

Not sure if this is a temporary issue as the PKGBUILDs are being fixed or if this is a recurring issue; will have to wait for the next update to see.