Impact-I
Unable to build custom Flutter 3.27.1 engine using engine commit cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d for Flutter 3.27.1
Hi team,
I’m trying to reverse a Flutter application built with Flutter 3.27.1 and Dart 3.6.0 using reFlutter. According to your enginehash.csv, the correct configuration for Flutter 3.27.1 is:
Engine Commit: cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d
Snapshot Hash: f956f595844a2f845a55707faaaa51e4
However, when I run the Docker build process like below:
docker run -it
-v "$(pwd):/t"
-e HASH_PATCH=f956f595844a2f845a55707faaaa51e4
-e COMMIT=cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d
reflutter
I get the following error:
fatal: remote error: upload-pack: not our ref cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d It seems that this engine commit no longer exists (or is inaccessible) in the public Flutter Engine repository.
I also tried cloning the flutter/engine repository and manually checking out the latest commit for the corresponding Flutter version (17025dd88227cd9532c33fa78f5250d548d87e9a), but encountered the same result — the referenced commit for the engine does not appear to exist in the public repo.
Could you please clarify:
Is there an alternative working engine commit that matches the same snapshot hash (f956f595...) for Flutter 3.27.1?
Or is there a known workaround to proceed with the engine patching for this version?
Thanks in advance for maintaining this great tool. Any help would be appreciated!
Hi team,
I’m trying to reverse a Flutter application built with Flutter 3.27.1 and Dart 3.6.0 using reFlutter. According to your enginehash.csv, the correct configuration for Flutter 3.27.1 is:
Engine Commit: cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d
Snapshot Hash: f956f595844a2f845a55707faaaa51e4
However, when I run the Docker build process like below:
docker run -it -v "$(pwd):/t" -e HASH_PATCH=f956f595844a2f845a55707faaaa51e4 -e COMMIT=cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d reflutter I get the following error:
fatal: remote error: upload-pack: not our ref cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d It seems that this engine commit no longer exists (or is inaccessible) in the public Flutter Engine repository.
I also tried cloning the flutter/engine repository and manually checking out the latest commit for the corresponding Flutter version (17025dd88227cd9532c33fa78f5250d548d87e9a), but encountered the same result — the referenced commit for the engine does not appear to exist in the public repo.
Could you please clarify:
Is there an alternative working engine commit that matches the same snapshot hash (f956f595...) for Flutter 3.27.1?
Or is there a known workaround to proceed with the engine patching for this version?
Thanks in advance for maintaining this great tool. Any help would be appreciated!
The repository for flutter has been moved to https://github.com/flutter/flutter.git Check the updated Dockerfile here: https://github.com/Impact-I/reFlutter/blob/main/Dockerfile Delete the initial image you built and re-build from the new one.
I'm getting same error. I cloned the repo recently.
docker run -it -v "$(pwd):/t" -e HASH_PATCH=18818009497c581ede5d8a3b8b833b81d00cebb7 -e COMMIT=830f4f59e7969c70b595182826435c19 reflutter
Requirement already satisfied: wheel in /usr/lib/python3/dist-packages (0.37.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Processing /t
Preparing metadata (setup.py) ... done
Building wheels for collected packages: reflutter
Building wheel for reflutter (setup.py) ... done
Created wheel for reflutter: filename=reflutter-0.8.5-py3-none-any.whl size=24585 sha256=e615650ca4ee3b45de9edaf0b8c7f34abc6d91d189932ef089c8a36ea6ca2837
Stored in directory: /tmp/pip-ephem-wheel-cache-b32n47aq/wheels/d4/1a/f7/4f1df35f9b27b201c83741a429987cbbea05bf9f77e0f30c38
Successfully built reflutter
Installing collected packages: reflutter
Successfully installed reflutter-0.8.5
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Cloning into '/depot_tools'...
remote: Finding sources: 100% (7/7)
remote: Total 64834 (delta 39796), reused 64829 (delta 39796)
Receiving objects: 100% (64834/64834), 80.17 MiB | 8.00 MiB/s, done.
Resolving deltas: 100% (39796/39796), done.
Cloning into '/engine'...
remote: Enumerating objects: 1061172, done.
remote: Counting objects: 100% (215/215), done.
remote: Compressing objects: 100% (193/193), done.
remote: Total 1061172 (delta 117), reused 23 (delta 22), pack-reused 1060957 (from 4)
Receiving objects: 100% (1061172/1061172), 380.54 MiB | 1.36 MiB/s, done.
Resolving deltas: 100% (753693/753693), done.
Updating files: 100% (14790/14790), done.
fatal: couldn't find remote ref 830f4f59e7969c70b595182826435c19
