Closed NightMean closed 1 day ago
I've now also checked EventViewer and upon opening 1.3.2
, the event viewer shows the same log I've shared for 1.3.0
above although the log in %APPDATA%/OBSNotifier/logs
is empty.
[11/16/2024 19:22:25] Exception: [11/16/2024 19:22:25]- Sequence contains no elements [11/16/2024 19:22:25]- StackTrace: [11/16/2024 19:22:25]- at System.Linq.Enumerable.First[TSource](IEnumerable`1 source) [11/16/2024 19:22:25]- at OBSNotifier.App.SelectLanguageOnStart(CultureInfo start_ui_info) [11/16/2024 19:22:25]- at OBSNotifier.App.Application_Startup(Object sender, StartupEventArgs ee)
Based on these logs I will assume that your language is not added to the list of supported localizations.
I'll fix that soon.
Can you check this build?
My program is actually targeting 4.7.2.
Yeah, I noticed. Although having a newer minor version shouldn't be a problem.
Based on these logs I will assume that your language is not added to the list of supported localizations.
Also, yes. I didn't submit any translation yet :) Although, I thought that might be an issue, when I switched my Windows to English as a primary language, the app still didn't open without this fix.
Can you check this build?
You are awesome! :) Now it starts without any issue. Thanks for the quick fix!
Now it starts without any issue.
I hope the program restarts and the language changes without problems too? If so, I will prepare and release this version.
Yes it does, already tried to auto start it along OBS. No issues here :)
Commit or version
1.3.2
On which operating systems the error occurs
OS:
Windows 10 22H2 (19045.5131)
with all updates installed along with.NET Framewework 4.8
OBS:30.2.3 (64 bit)
with websockets enabledIssue description
Hi, I wanted to use this app once again as I reinstalled my Windows but whenever I open OBSNotifier.exe
v1.3.2
, the app silently crashes in the background without any prompt or any helpful logs.As I've used this in the past on my previous Windows installation without any issue, I tried to open older version
1.3.0
but the result was the same although, this time I saw something in the error logs. I'm not sure if this is related.Logs:
Steps to reproduce