Bug: 1.1.10 'cannot get property getTime of null'

[Temerityc]

Been using Vortex for months, no problem. After update I get the following bug ONLY when offline and not connected to the net.

 

Version: Vortex-1-1-1-10-1579775055

Game: Skyrim

# of Mods: 89

OS: Windows 10 (up to date)

 

See attached log. (Well I tried a few times to attach it, it uploads and then gives me a blank white line. Doesn't seem to work.)

 

Error window that opens when Vortex is loading: https://i.postimg.cc/HLMnSSPf/Bug.jpg

 

 

 

[HadToRegister]

Have you tried reinstalling Vortex?
It seems that sometimes things can get lost during the install, maybe by an AV software or Windows Defender

[Cyclohexatriyne]

The same problem as yours except that mine ocurrs every time I run the program whether it is online or offline. Having tried many times reinstalling the soft and rebooting the system, but it didn't work.

[darklaker]

I got it because updTe, i reinstall with older version

[BigBizkit]

Have you tried clicking "Ignore" and then sending in a report through Vortex?

 

I relayed your report anyway, in case that's not possible.

 

edit: this appears to already have been fixed by the developers. A hotfix will be released soon (some time this week).

[BaronGreystone]

I love the way that it tells you not to whine to them if you decide to ignore the warning and play anyway. Ya know, that means it's not a bug. Bugs don't come with their own smart-ass attitude. Someone thinks they're pretty wise. Way to alienate people.

[Pickysaurus]

Please try updating to 1.1.12 where the issue should be resolved.

[Tannin42]

Ya know, that means it's not a bug.

 

Umm, no, you confuse the term "bug" with "crash".

 

The message says that an unexpected exception was caught (an exception can be expected, e.g. "your disk is full" is an exception but since it's out of our hands we can't prevent it, just react to it. But in this case we have no code to react to this specific exception).

 

We can produce the error message that was generated at the time the exception was thrown and we can have that reported to the developers so they can determine when, where and why it happened and fix it if necessary.

But at the time that release was made, we, the developers, do not know about the error and what the consequences of the error are and thus we can not tell you if it's safe to ignore it.

It may be (and often is the case) that there is no negative consequence and things sort itself out.

It may be that some irrelevant functionality breaks but everything else is ok.

It may be that Vortex crashes immediately afterwards but no further problems arise.

It may be that you get additional error message as a result of this one - which is why we ask that you don't report any errors after you ignored one, we only care about the initial trigger.

It may also be that due to the error Vortex has invalid data in memory and by ignoring it you get that invalid data saved to disk, potentially overwriting data that was valid, potentially destroying hours of setup. "data" may be vortex application state but theoretically it could also be save games, profiles, ini files, ...

 

Ignoring this kind of error message without a dev telling you that it's save is dangerous. And yes, that's something you need to hear.

The decision is yours, if you want to do something stupid, that's fine, it's your decision, I don't judge. But I don't want you to be able to say later you didn't know it was risky "because the message wasn't clear enough".

The reality is that if we offer an "Ok" or "Continue" button, a significant number of users click it blindly without actually reading what the message says, because they have been trained to do that by years of pointless OK, Cancel dialogs.

If it requires me to have a somewhat offensive button text if it means that more users will stop for a second and see what it actually says then I think it's worth it.