HSTracker 2.4.2(2623) stuck after last patch (23.2) => application not responding.

[ShereKahn]

Describe the bug Since yesterday's Hearthstone update (to v26.2.0.17458) the application starts fine, but as soon as HS gets started, the application become non-responsive, and needs to be forcibly shutdown.

The logs seems to show that it's stuck waiting for HeartMirror with messages such as:

:02:18.791 VERBOSE CoreManager.setup():206 - Zones found : [[Power: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=true, RequireVerbose=true], [Rachelle: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=false, RequireVerbose=false], [Arena: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=false, RequireVerbose=false], [LoadingScreen: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=false, RequireVerbose=false], [Decks: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=false, RequireVerbose=false], [FullScreenFX: LogLevel=1, FilePrinting=true, ConsolePrinting=false, ScreenPrinting=false, Verbose=false, RequireVerbose=false]]
14:02:18.792 VERBOSE CoreManager.setup():217 - Is power valid ? true
14:02:18.794 VERBOSE CoreManager.setup():217 - Is rachelle valid ? true
14:02:18.795 VERBOSE CoreManager.setup():217 - Is arena valid ? true
14:02:18.796 VERBOSE CoreManager.setup():217 - Is loadingScreen valid ? true
14:02:18.798 VERBOSE CoreManager.setup():217 - Is decks valid ? true
14:02:18.800 VERBOSE CoreManager.setup():217 - Is fullScreenFX valid ? true
14:02:18.801 VERBOSE CoreManager.setup():230 - Missing zones : []
14:02:18.803 INFO Game.set():1465 - has Valid Mirror Deck: 18 cards
14:02:19.293 DEBUG BattlegroundsOverlayView.updateTrackingAreas():125 - update Tracking Area
14:03:38.348 VERBOSE CoreManager.appLaunched():312 - Hearthstone is now launched
14:03:38.354 INFO DeckWatcher.startWatching():22 - Starting ExperienceWatcher
14:03:38.572 VERBOSE MirrorHelper.mirror():27 - Initializing HearthMirror with pid 97736
14:03:38.638 ERROR MirrorHelper.initMirror():56 - Mirror is not working yet, trying again...
14:03:39.138 ERROR MirrorHelper.initMirror():56 - Mirror is not working yet, trying again...
14:03:39.639 ERROR MirrorHelper.initMirror():56 - Mirror is not working yet, trying again...
14:03:40.140 VERBOSE MirrorHelper.mirror():27 - Initializing HearthMirror with pid 97736

The trackers never appear when starting a game, although detection would seem to occur according to logs (that I have attached)

To Reproduce Start HSTracker

Start Hearthstone

Application is now unresponsive on the GUI side.

Game mode

• [x] Standard
• [x] Wild
• [x] Classic

Haven't tried the other modes

• [ ] Arena
• [ ] Battlegrounds
• [ ] Duels
• [ ] Mercenaries
• [ ] Tavern Brawl
• [ ] Dungeon Run/Book of Heroes/Book of Mercenaries
• [ ] Single Player

Expected behavior Application should not become unresponsive.

Screenshots N/A

Version (please complete the following information): HSTracker 2.4.2(2623)

Additional context

Log file Attach the hstracker.log file found under /Users/<userid>/Library/Logs/HSTracker/ directory (or use the Help->Open log directory)

Deck code If the problem happens with a specific deck, please include the deck code used. hstracker.log

[ArturKontrabaev]

same problem here, tried to install prev version, same effect

[Sternish]

Seems like Blizzard broke pretty much every third party app, as they upgraded Hearthstone to a new version of Unity in the latest patch.

[fmoraes74]

I am working on the update. I almost released a new version without BobsBuddy update but held back to try to get the new BB version included but ran into some issues while testing it. It is close, hopefully tomorrow I will have the update. Please be patient. It was a lot of changes from new cards that need to be simulated, new Unity version which broke every third party application. It was close, just takes longer for HSTracker due to Swift and C# integration in this case and some new behavior that is crashing HSTracker.

[ShereKahn]

Sure @fmoraes74, Thanks a lot and keep up the great work!

[fmoraes74]

Please give version 2.4.3 a try and let me know how it goes. Battlegrouds simulations are working well but some interactions are not fully supported by BobsBuddy at the moment (same as HDT).

[ArturKontrabaev]

Please give version 2.4.3 a try and let me know how it goes. Battlegrouds simulations are working well but some interactions are not fully supported by BobsBuddy at the moment (same as HDT).

works perfectly, air m2, all latest updates installed thank you so much !

[ArturKontrabaev]

Please give version 2.4.3 a try and let me know how it goes. Battlegrouds simulations are working well but some interactions are not fully supported by BobsBuddy at the moment (same as HDT).

btw auto positioning of tracker changed before it was a little bit standing away from corners, and now stuck to corner of the screen

and manual positioning I never could use due to fact that I always move hs window

[fmoraes74]

btw auto positioning of tracker changed before it was a little bit standing away from corners, and now stuck to corner of the screen

@ArturKontrabaev What do you mean? Which tracker window specifically? I don't recall changing anything, at least not around this patch.

[ArturKontrabaev]

@ArturKontrabaev What do you mean? Which tracker window specifically? I don't recall changing anything, at least not around this patch.

there is no space between tracker and window https://shottr.cc/s/Up3q/SCR-20230512-7ng.png

and before it was like this https://shottr.cc/s/U8pJ/SCR-20230512-7of.png and some additional space on the sides

[fmoraes74]

The opponent tracker has an option to prevent it from covering the name. The player tracker doesn't. This part of the code was not changed in over 6 years :-)

Anyway, if there are any further issues, feel free to open a new issue. Closing this one.