HearthSim/HSTracker

Automatic update never works

DennisBecker opened this issue · 15 comments

Describe the bug
I always have to check for updates manually even though I have checked the option for automatic updates. I have HSTracker installed for more than one year.

To Reproduce
Steps to reproduce the behavior:

  1. New version gets released
  2. open HsTracker / close HsTracker multiple times
  3. open HsTracker
  4. Open "Check for updates ..." and you can install a new version

Expected behavior
HsTracker should install new updates automatically

Screenshots
Screenshot 2022-08-10 at 07 31 26

Version (please complete the following information):
2.2.2

Please run the following command from a Terminal:

defaults read net.hearthsim.hstracker | grep -vi token

and share the output. I suspect there is a setting that's preventing automatic updates from happening. Automatic updates are checked once each day but if the update URL is pointing at the wrong feed, then that would explain it.

{
    AppleLanguages =     (
        en
    );
    MSAppCenter310AnalyticsUserDefaultsMigratedKey = 1;
    MSAppCenter310AppCenterUserDefaultsMigratedKey = 1;
    MSAppCenter310CrashesUserDefaultsMigratedKey = 1;
    MSAppCenterAppDidReceiveMemoryWarning = 1;
    MSAppCenterInstallId = "70F86EB6-8447-4732-B7C7-6F3FEEAFD3D3";
    MSAppCenterPastDevices = {length = 1156, bytes = 0x62706c69 73743030 d4010203 04050607 ... 00000000 0000038e };
    MSAppCenterSessionIdHistory = {length = 502, bytes = 0x62706c69 73743030 d4010203 04050607 ... 00000000 0000017e };
    MSAppCenterUserIdHistory = {length = 455, bytes = 0x62706c69 73743030 d4010203 04050607 ... 00000000 00000151 };
    "NSWindow Frame SUAutomaticUpdateAlert" = "972 913 616 193 0 0 2560 1415 ";
    "NSWindow Frame SUUpdateAlert" = "970 762 620 398 0 0 2560 1415 ";
    "NSWindow Frame com.sindresorhus.Preferences.FrameAutosaveName" = "-1387 389 328 486 -1728 0 1728 1079 ";
    SUAutomaticallyUpdate = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2022-08-10 05:31:06 +0000";
    SUUpdateRelaunchingMarker = 0;
    "arena_helper_version" = "0.1.121";
    "auto_position_trackers" = 0;
    "battlegrounds_session_frame" = "{{1638, 72}, {200, 1152}}";
    "can_join_fullscreen" = 1;
    "disable_tracking_in_spectator_mode" = 1;
    "flash_draw" = 0;
    "hearthstone_language" = enUS;
    "hearthstone_log_path" = "/Applications/Hearthstone/";
    "hide_all_trackers_when_game_in_background" = 1;
    "hide_all_trackers_when_not_in_game" = 1;
    "highlight_last_drawn" = 0;
    "hsreplay_cardtier_version" = "0.1.4";
    "hstracker_language" = en;
    "opponent_board_damage" = 0;
    "opponent_board_damage_frame" = "{{1626, 1041}, {50, 50}}";
    "opponent_card_count" = 0;
    "opponent_cthun_frame" = 0;
    "opponent_draw_chance" = 0;
    "opponent_galakrond_invoke_frame" = 0;
    "opponent_graveyard_frame" = 0;
    "opponent_jade_frame" = 0;
    "opponent_libram_counter" = 0;
    "opponent_tracker_frame" = "{{0, 0}, {217, 1440}}";
    "opponent_yogg_frame" = 0;
    "player_board_damage" = 0;
    "player_card_count" = 0;
    "player_cthun_frame" = 0;
    "player_draw_chance" = 0;
    "player_galakrond_invoke_frame" = 0;
    "player_graveyard_frame" = 0;
    "player_jade_frame" = 0;
    "player_libram_counter" = 0;
    "player_tracker_frame" = "{{1839, 0}, {217, 1286}}";
    "player_yogg_frame" = 0;
    "rarity_colors" = 0;
    showMemoryReadingWarning = 0;
    "show_average_damage" = 1;
    "show_card_huds" = 0;
    "show_experience_counter" = 0;
    "show_floating_card" = 0;
    "show_hero_toast" = 1;
    "show_mercs_opponent_abilities" = 0;
    "show_mercs_opponent_hover" = 0;
    "show_mercs_player_abilities" = 0;
    "show_mercs_player_hover" = 0;
    "show_mercs_tasks" = 0;
    "show_mmr_start_current" = 1;
    "show_mulligan_toast" = 0;
    "show_opponent_created" = 0;
    "show_opponent_tracker" = 0;
    "show_player_tracker" = 0;
    "show_secret_helper" = 0;
    "show_session_recap" = 0;
    "window_locked" = 1;
}

@DennisBecker Thanks for the data, I don't see anything wrong there. Can you also share the contents of ~/Library/Logs/SparkleUpdateLog.log ?

2022-07-26 13:51:04 +0000: ===== Tunnelblick =====
2022-07-26 13:51:04 +0000: Verified appcast signature
2022-07-28 20:43:42 +0000: Verified appcast signature
2022-07-30 04:44:54 +0000: Verified appcast signature
2022-07-31 14:06:44 +0000: Verified appcast signature
2022-08-02 22:37:36 +0000: Verified appcast signature
2022-08-05 10:59:45 +0000: Verified appcast signature
2022-08-06 14:15:54 +0000: Verified appcast signature
2022-08-07 14:42:06 +0000: Verified appcast signature
2022-08-09 12:02:51 +0000: Verified appcast signature
2022-08-11 04:52:42 +0000: Verified appcast signature

Nothing of notice there unfortunately. I think we will have to wait for the next release shortly after the next balance patch and see if the sparkle log sheds some light into it.

No problem. Should I open HsTracker an wait several monutes when a new update gets released or should it update immediately when I start it?

No problem. Should I open HsTracker an wait several monutes when a new update gets released or should it update immediately when I start it?

It should tell you about the update within a few seconds after restarting but be aware that if your previous version had already checked for updates, it may take up to 24 hours for a pop up. I will check if I can force an update check when starting.

Are you running HSTracker from /Applications or from the directory you downloaded from?

Okay this neither triggered on my M1 nor on the old Intel Macbook before.

I have put in /Applications

Okay this neither triggered on my M1 nor on the old Intel Macbook before.

I have put in /Applications

Ok. I will monitor my local installation as well but I usually run the debug version in case I hit bugs. Let's see how it goes during the next update.

The tracker runs 10 to 15 minutes now and still is on version 2.2.2 - no automatic update to 2.2.3

~/Library/Logs/SparkleUpdateLog.log

Is the contents of the file still not helpful like last time? Please note that HSTracker may need up to 24 hours before it tells you there is an update. If you want it to try sooner, stop it and run defaults delete net.hearthsim.hstracker SULastCheckTime and start HSTracker again.

Version 2.2.3 will have an indicator that there is an update, like when you have a new email. Again, this may only be noticeable if you leave it running for more than 24 hours as the configuration only checks for updates once a day.

I will check that. My Macbook was shutdown for more than 8 days and I started it today. Most of the time it is only running when I will play Battlegrounds.

I will check that. My Macbook was shutdown for more than 8 days and I started it today. Most of the time it is only running when I will play Battlegrounds.

I am hoping that once you get into 2.2.3, it will give you at least a better message/warning when updates are available. I could force check for updates on each start, but doesn't seem to be necessary as I am trying to only do updates when necessary (typically around HS patches or major issues)

I had the tracker closed, opened now and now it is on 2.2.3

SparkleUpdateLog has still nothing interesting:

2022-08-25 07:18:38 +0000: ===== Tunnelblick =====
2022-08-25 07:18:38 +0000: Verified appcast signature

That was the first time it worked, before even using the tracker multiple times over a week it did not update automatically

I think the new version of Sparkle was set to automatically upgrade and it does so without prompting (or you clicked the setting to let it do automatically). I think this was a change in behavior with the old version. Version 2.2.3 now disables automatic upgrading. You could change this setting to 0: SUAutomaticallyUpdate but hopefully the next update will give you a prompt that it is available.

If you are ok with closing this, let me know. You can reopen after the patch 24.2 is launched and a new version is available.