openbullet / OpenBullet2

OpenBullet reinvented
https://docs.openbullet.dev/
MIT License
1.79k stars 479 forks source link

[Bug]: Open Bullet 2 doesn't open #904

Open usslmuk opened 1 year ago

usslmuk commented 1 year ago

Version of the software

0.2.5

Operating system

Windoes 11

Browser / Native

Brave

What happened?

My open bullet 2 doesn't open.

Relevant LoliCode if needed

No response

openbullet commented 1 year ago

Hi, could you please let us know the exact steps you did? Did you follow the official installation guide? What exactly do you mean by "it doesn't open"? Did you navigate to the localhost address?

GNanosecond commented 1 year ago

Same here - updated Native from 0.2.4 -> 0.2.5 via Native updater. Crash on initialize (before window present).

Just a side note, despite the original ticket stating a browser, I believe this may be a Native issue. I initially thought it was asking for the browser used in general on first glance.

The issue I came across

I've taken a gander and discovered the crash (in my case) is directly related to problematic JobOptions. Here's a culprit:

{"Options":{"$type":"OpenBullet2.Core.Models.Jobs.MultiRunJobOptions, OpenBullet2.Core","ConfigId":"MyAmazingConfig","Bots":7,"Skip":0,"ProxyMode":1,"ShuffleProxies":false,"NoValidProxyBehaviour":2,"ProxyBanTimeSeconds":0,"MarkAsToCheckOnAbort":false,"NeverBanProxies":false,"ConcurrentProxyMode":false,"PeriodicReloadIntervalSeconds":0,"DataPool":{"$type":"OpenBullet2.Core.Models.Data.FileDataPoolOptions, OpenBullet2.Core","FileName":null,"WordlistType":"Default"},"ProxySources":[{"$type":"OpenBullet2.Core.Models.Proxies.GroupProxySourceOptions, OpenBullet2.Core","GroupId":-1}],"HitOutputs":[],"StartCondition":{"$type":"RuriLib.Models.Jobs.StartConditions.RelativeTimeStartCondition, RuriLib","StartAfter":"00:00:00"}}}

On inspection, the crash is caused by "HitsOutput" being an empty array. I couldn't tell you how this happened, I have no wild guesses on how this could've happened.

I manually modified the db to check if this was an issue with 0.2.4 and found it didn't give a shit 🙂