Closed Bestfastfire closed 3 years ago
The problem is the CI stopped, because there was no activity on the repo. I already pinged them, but the didn't answer. Maybe we should fork the repo so we can fix it @pchampio @GeertJohan ?
The problem is the CI stopped, because there was no activity on the repo. I already pinged them, but the didn't answer. Maybe we should fork the repo so we can fix it @pchampio @GeertJohan ?
I forked, do you have any idea how I can make him try to download from my rep instead of the original?
You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312 You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.
You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312 You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.
I go try, if works, I type here. Dude, ty, you are saving my job kkkkk
You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312 You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.
Do you think it would not be easier to download the file from there manually and make the code do what it has to do with the local zip?
I don't understand
I don't understand
In the code it downloads the rep zip file and then uses it, it wouldn't be easier to download it manually and make the code instead of trying to download it, do what you have to do with it locally
Yeah you can download it manually, but why would you do that? The engine builds need to run anyway and changing the repo url is much easier.
Yeah you can download it manually, but why would you do that? The engine builds need to run anyway and changing the repo url is much easier.
I tried it now but dont works, I think I do something wrong, I changed the code but when I run the command, show same mensage:
Are you on windows? I see there is this release: https://github.com/Bestfastfire/engine-builds/releases/tag/draft, but the actions need to set the proper tag for it
I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.
I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.
Ye, I did it, I have no idea how to proceed, I am totally a layman in go language :/
I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.
Well, I'm going to finish my project and give the client the debug version for now, it's working fine. If this problem ever resolves or I figure out how to do it, I create the release.
Forget it, I found a file picker plugin that works without the need for hover, https://pub.dev/packages/file_picker_cross, works well in the standard flutter release.
@jld3103 yea we can fork the engine build repo. I guess we have no choice choice. Too bad, it’s something else we have to maintain.
Actions are now running again, but still we might want to fork the repo to get more control over it.
Hi, is this issue has a quick fix?
Any other method to build windows release?
Actions are now running again, but still we might want to fork the repo to get more control over it.
@all check that your flutter engine version was compiled by rs-flutter. If it was missed due to the action been stoped, please try update your flutter branch. Or use the hover engine-version flag and pick a version available as a rs-flutter/engine-build release.
Master channel builds are now succeeding again. Hopefully the other channels will work soon.
Actions are now running again, but still we might want to fork the repo to get more control over it.
@ALL check that your flutter engine version was compiled by rs-flutter. If it was missed due to the action been stoped, please try update your flutter branch. Or use the hover engine-version flag and pick a version available as a rs-flutter/engine-build release.
how? can u explain please?
EDIT: Forget that, I just changed engine version on hover.yaml to engine-version: "b3a18f5182827ca6db20f3e75bfe11b39368b4ec". And worked again.
Beta builds are also working again.
Hi, I'm still facing this issue, and flutter version is 2.5, hover version is 0.46.6.
Hi, I'm still facing this issue, and flutter version is 2.5, hover version is 0.46.6.
I also have this problem. I seem to have found a temporary way.
@niuhuan Yeah flutter 2.2 works, it's not a good idea to stay with a lower version of flutter through.
@niuhuan Yeah flutter 2.2 works, it's not a good idea to stay with a lower version of flutter through.
I think this problem because "https://github.com/flutter-rs/engine-builds/releases" don't have this commit release.
I tried to specify the engine version before "hover run", it build success , but windows can‘t init. It does not correspond to the commit of flutter.
“hover run” is not have problem because the engine download URL is different
flutter-rs/engine 's action has stop auto build long time ago, watch forked repertoires build.
Try clone and modify hover sources, change the engine download url , then build hover.
flutter-rs/engine 's action has stop auto build long time ago, watch forked repertoires build.
Try clone and modify hover sources, change the engine download url , then build hover.
I had.success download 2.5 engine, but failed to build ( aot error)
When I try run
hover build windows
I awalys get this: