Skip to content
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

🐛 Can't get it build and recurring 'native assets' error #64

Open
escottgoodwin opened this issue Jun 13, 2024 · 3 comments
Open

🐛 Can't get it build and recurring 'native assets' error #64

escottgoodwin opened this issue Jun 13, 2024 · 3 comments

Comments

@escottgoodwin
Copy link

Bug report

Describe the bug
I keep getting the 'native assets required' error and the app never builds.

I am using an M2 mac.

Steps to reproduce

Steps to reproduce the behavior:

I have enabled native assets with 'flutter config --enable-native-assets' several times, restarted editor and continue to get native assets required error when running 'flutter run --dart-define=GEMMA_8B_GPU_URI=...' (using a gemma model hosted with gcloud storage). I have it configured to run on my mac and my real iphone.

In VScode, when run the app with the 'play' button, it starts, I don't get a error, but it never finishes building. It stays launching. There is output in in the debug console on VScode.

Expected behavior

App runs

Sample project

Running the example app from the repo.

@escottgoodwin
Copy link
Author

flutter config --list
All Settings:
enable-web: (Not set)
enable-linux-desktop: (Not set)
enable-macos-desktop: (Not set)
enable-windows-desktop: (Not set)
enable-android: (Not set)
enable-ios: (Not set)
enable-fuchsia: (Not set) (Unavailable)
enable-custom-devices: (Not set)
cli-animations: (Not set)
enable-native-assets: true (Unavailable)
enable-flutter-preview: (Not set) (Unavailable)

@craiglabenz
Copy link
Collaborator

Switch to the master channel and the native-asserts experiment should become available.

@mlleo
Copy link

mlleo commented Jun 28, 2024

Any other way to solve if I use stable channel? For the production, using master channel could be kind of risky.....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants