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

The apps offer update to latest version although its a last version. #837

Open
ilyak83 opened this issue Apr 5, 2024 · 12 comments
Open
Assignees
Labels

Comments

@ilyak83
Copy link

ilyak83 commented Apr 5, 2024

Description

If checking updates In manual manner the apps offer update to latest version although its a last version.

Screenshot attached.

Expected Behavior

No response

Log Data

service.log

Commit Hash, Version and Windows Build

Edition Windows 11 Pro
Version 23H2
OS build 22631.3374
Experience Windows Feature Experience Pack 1000.22688.1000.0

Screenshots / Videos

image

@Spiritreader
Copy link
Member

okay that is very strange.

I've never seen this happen. Do you still get this after updating to the latest beta build?

@ilyak83
Copy link
Author

ilyak83 commented May 10, 2024

I noticed that this issue was accrued only if the app was installed in a common profile for all users and not in particular.

Copy link

github-actions bot commented Jul 9, 2024

No updates have been provided to this issue after 60 days of inactivity. The issue will be automatically closed in 7 days.

@wollac11
Copy link

wollac11 commented Jul 9, 2024

I also experience this issue. Weirdly for me the app reports an even older version in the notification but the installed version is the very latest,

@Armin2208 Armin2208 added the bug Something isn't working label Jul 11, 2024
@Gravifer
Copy link

image
I got something even more weird.
Can confirm I'm on 10.4.1.1
image
Also worth noticing, several errors are thrown when I use the copy-version-info button. Maybe this hint some problem in the version handling code?

@mateuszdrab
Copy link

I have that non-stop as well.
Could it be because the notification comes from AutoDarkModeSvc.exe and that still is on version 1.3.0.90, the service executable version does not match.

@Spiritreader
Copy link
Member

Please check if this still occurs with the latest beta.

@Gravifer
Copy link

Please check if this still occurs with the latest beta.

Is there a tag for it? I can't seem to find it in the releases

@Armin2208
Copy link
Member

Please check if this still occurs with the latest beta.

Is there a tag for it? I can't seem to find it in the releases

You need to open the Auto Dark Mode app, go to settings and change your update channel to beta.

@Gravifer
Copy link

Gravifer commented Dec 2, 2024

Screenshot with Beta
I suspect the issue arises arise because I installed in all-user mode. I'll try and switch to a per-user install
Update: I managed to switch to a user install; the app crashed for a few times, but now is up and working. The updater also recognizes the correct version and does not pop-up erroneously anymore.

@Spiritreader
Copy link
Member

Screenshot with Beta I suspect the issue arises arise because I installed in all-user mode. I'll try and switch to a per-user install Update: I managed to switch to a user install; the app crashed for a few times, but now is up and working. The updater also recognizes the correct version and does not pop-up erroneously anymore.

That looks correct.
If you're in all user's mode the updater will tell you to download the app manually.

I understand the issue now. If you're in all users mode you can't use beta versions because the update system is not designed to run privileged.
All users mode is getting pulled soon so the issue should disappear then

@Gravifer
Copy link

Gravifer commented Dec 4, 2024

I suspect the issue arises arise because I installed in all-user mode....

That looks correct. If you're in all user's mode the updater will tell you to download the app manually.

I understand the issue now. If you're in all users mode you can't use beta versions because the update system is not designed to run privileged. All users mode is getting pulled soon so the issue should disappear then

The OP seems to have encountered the opposite case? To reiterate

I noticed that this issue was accrued only if the app was installed in a common profile for all users and not in particular.

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

No branches or pull requests

6 participants