Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qbt 5 compatibility #98

Open
benfishbus opened this issue Oct 17, 2024 · 10 comments
Open

qbt 5 compatibility #98

benfishbus opened this issue Oct 17, 2024 · 10 comments

Comments

@benfishbus
Copy link

Is anyone else running this with qbt 5.0 as a separate server? When I login to iQbit, I see a flash of UI then total black screen. My qbt 5.0 is using the (new) default webui. Sorry if this is already addressed somewhere and I missed it...

@espiox
Copy link

espiox commented Oct 17, 2024

Yeah, I have the same issue

@benfishbus
Copy link
Author

I should add, my phone is on iOS 18, and I'm using Firefox. I just signed in from Firefox on Windows, and iQbit displays correctly.

@benfishbus
Copy link
Author

Occurs in Safari and Chrome for iOS too. Switching off dark mode made no difference. And I confirmed my similarly set up qbt 4.x instance still displays properly through iQbit. Viewed directly on iPhone, qbt 5.0 webui displays as well as can be expected - not a black screen but still not mobile friendly. Anyway, seems like something going wrong between iQbit and webui 5.0.

@ntoporcov
Copy link
Owner

Im planning on taking a look today! Should be some api call that got updated

@ntoporcov
Copy link
Owner

I wasn't able to repro but a I did notice that the UI seems to be getting hung up at some point, and while that was happening the UI also fails to respond (API calls stay pending). If you're on the nox version, I imagine that would be hard to notice maybe :/

Best solution might be to downgrade :/

@benfishbus
Copy link
Author

Bummer! Will you be reporting that as a qb issue? I don't think I've experienced that while using the 5.0 webui directly.

@benfishbus
Copy link
Author

Not sure what changed, but I'm no longer experiencing this problem.

@breadbyte
Copy link

breadbyte commented Oct 29, 2024

Currently having the same issue, and my console has spouted the following error:

TypeError: Cannot read properties of undefined (reading 'short')
    at II (TorrentBox.tsx:319:57)

which does seem to correlate with the following line:

<span>{stateDictionary[torrentData.state].short}</span>

I can provide more information if required.

qBit version: v5.0.0
iQbit version: 9ae1463

@Lemagex
Copy link

Lemagex commented Nov 7, 2024

Same issue, can help with logs if required.

@brandonjp
Copy link

Well, I don't know the iQbit or qB api well enough to make a real fix, but if you wanna temp fix:

  • open iQbit/release/public/static/js/main.b4c1c017.js
  • search for children:kT[t.state].short (it's about 75% to the end of the file)
  • replace it with: children:kT?.[t.state]?.short || 'Unknown'
  • save and reload the page

For me the iQbit ui works, although is a little sluggish and occasionally has additional JS errors that crash the page

If you're building from the source files you can...

  • open iQbit/src/components/TorrentBox.tsx
  • find this line: <span>{stateDictionary[torrentData.state].short}</span>
  • change it to: <span>{stateDictionary?.[torrentData.state]?.short || 'Unknown state'}</span>
  • then rebuild

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants