Skip to content

How to update to 3.0 #248

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

Closed
kukjevov opened this issue May 17, 2022 · 12 comments
Closed

How to update to 3.0 #248

kukjevov opened this issue May 17, 2022 · 12 comments

Comments

@kukjevov
Copy link

Hello i have been successfuly using flutter-pi with flutter 2.10, i have updated to 3.0 and i get following error during startup.

Error while initializing the Dart VM: Wrong full snapshot version, expected 'd56742caf7b3b3f4bd2df93a9bbb5503' found '1441d6b13b8623fa7fbf61433abebd31'

I had pulled latest engine binaries on development machine and called ./install.sh
I had called flutter upgrade on development machine.
I had pulled latest flutter-pi changes on raspberry os and removed build directory in flutter-pi and called following commands.

mkdir build && cd build
cmake ..
make -jnproc
sudo make install

What am i missing?

Thank you

@pieter-scholtz
Copy link
Collaborator

pieter-scholtz commented May 18, 2022

Perhaps try the following :

  1. Make sure that your flutter SDK is checked out at 3.0.0 using flutter doctor -v
  2. Inside the flutter SDK delete the cache folder located at: /flutter/bin/cache

@zoechi
Copy link

zoechi commented Jun 8, 2022

I run into the same issue.
In my case it was because I didn't use the full path to the dart.exe and so the one from my Dart SDK install was executed, instead of C:\flutter\bin\cache\dart-sdk\bin\dart.exe ...

@pieter-scholtz
Copy link
Collaborator

pieter-scholtz commented Jun 8, 2022

I run into the same issue. In my case it was because I didn't use the full path to the dart.exe and so the one from my Dart SDK install was executed, instead of C:\flutter\bin\cache\dart-sdk\bin\dart.exe ...

I just want to clarify , this is with regards to AOT modes (profile & release) , and not a issue when running in debug mode ?

@zoechi
Copy link

zoechi commented Jun 8, 2022

@pieter-scholtz yes, in my case it was only with the additional steps for the release build.

@pieter-scholtz
Copy link
Collaborator

@zoechi Thanks , makes sense , when I first got the error it haunted me for a few weeks : D

@kukjevov
Copy link
Author

kukjevov commented Jun 9, 2022

Well i found out too, that problem is dart, but is the problem on dev machine, or on rpi production machine?

@zoechi
Copy link

zoechi commented Jun 10, 2022

It's on the dev machine when I try to create a release build, before rsyncing it to RPi

@pieter-scholtz
Copy link
Collaborator

Yes exactly , the reason I suggested deleting /flutter/bin/cache (On the dev machine) , is because sometimes when switching flutter SDK versions using just git , the dart stuff in the cache does not get updated, if you delete it , the correct version will be downloaded automatically (I think running flutter upgrade is better in this regard)

@kukjevov
Copy link
Author

Well i have deleted /flutter/bin/cache and even removed all ignored files in flutter repo. I have upgraded flutter using flutter upgrade and problem is still there. When i was looking on stackoverflow for something like this, one guy had similar problem, that only full reinstall of flutter helped. That is one thing that i havent tried yet. So i hope full reinstall will help :).

Anyway thx for replies :).

@pieter-scholtz
Copy link
Collaborator

Before you do that , I would recommend you check that you have the right engine libraries on the pi , perhaps delete the old ones from /usr/lib on the pi , and then run the install for that.

@ardera
Copy link
Owner

ardera commented Jun 14, 2022

I had pulled latest engine binaries on development machine and called ./install.sh

The engine binaries need to be installed on the pi, you don't need to install anything on your development machine except the flutter SDK

@kukjevov
Copy link
Author

@ardera @pieter-scholtz it looks like that problem was engine-binaries on rpi, now it is working thx :)

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

4 participants