-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Inaccurate update logic (latest ASFE version updating itself) #324
Comments
maybe updating logic from @Rudokhvist will help you to solve this |
Not an issue with ASFE - ASF for compatibility reasons will update the plugin to the same version if more than one zip asset is found, since new ASF version could decide to use different asset than the one used in the previous run. I have no clue why ASFE provides a zip asset per language though 🙂 |
So having only single ASFEnhance.zip archive in ASFE releases would fix it? |
Yes, although what you're describing is not an issue, plugin can force itself to be updated to the same version at any time it wants, and it should never cause you issues. |
I'm pretty sure @chr233 never intended this. |
And if the asset ASF decided to update to is the same as current one? In this case ASFE is in the |
tried use resx for multiple language support, and it will output resource dlls like |
All ASF plugins are shipped with multi-lang support and they work fine, so it seems ASFE does something different which is why it doesn't load. You definitely should not have a real need for that. |
You are right, this's a "historical issues" |
Now ASFE updates to v2.2.4.2. 2024-10-07 22:13:33|ArchiSteamFarm-1|INFO|ASF|GetTargetReleaseURL() Found ASFEnhance plugin update from version 2.2.4.0 to 2.2.4.2... but after restart it's v2.2.4.0 again 2024-10-07 22:18:30|ArchiSteamFarm-1|INFO|ASF|GetTargetReleaseURL() Found ASFEnhance plugin update from version 2.2.4.0 to 2.2.4.2... Something's wrong. |
just for testing github action, no need to upgrade this release |
I know it's was for testing, but still it had to update to v2.2.4.2 if I'm correct, since both ASF and ASFE were pre-release. -- ASFE was successfully updated to v2.2.5.0 now. |
During updating ASF from v6.0.7.5 to v6.0.8.0 ASFEnhance was updated from v2.2.3.3 to v2.2.3.3.
The text was updated successfully, but these errors were encountered: