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

[Bug]: Won't load #176

Closed
The-Ducktor opened this issue Oct 9, 2023 · 13 comments
Closed

[Bug]: Won't load #176

The-Ducktor opened this issue Oct 9, 2023 · 13 comments
Labels
bug Something isn't working triage Waiting for this issue to be triaged

Comments

@The-Ducktor
Copy link

The-Ducktor commented Oct 9, 2023

Describe the Bug

Bug Description
won't load when opening app after app login
Actual Behaviour stuck in loop
Expected Behavior
go to main screen and finish animation

Reproducing the Bug

  1. Login
    2 wait/open app

Version

7.0

Category

Connection

Relevant Log Output

No response

Screenshots

No response

Additional Info

No response

@The-Ducktor The-Ducktor added bug Something isn't working triage Waiting for this issue to be triaged labels Oct 9, 2023
@ShikiSuen
Copy link

I met this issue, too.

@hayd1n
Copy link

hayd1n commented Oct 9, 2023

Screenshot 2023-10-10 at 12 34 26 AM Same here.

@thuvasooriya
Copy link

thuvasooriya commented Oct 10, 2023

drawing drawing

Same Here :(
I was pretty excited to try it but it won't work 😢

@khurshid-alam
Copy link

Same here. It seems it is broken on Ventura.

@mgidding
Copy link

mgidding commented Oct 12, 2023

I am encountering this error both on 0.6.1 and 0.7.0. This is the CLI output for 0.6.1:

2023-10-12T13:36:43+0200 warning RobustWebSocket : error=dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid JSON.", underlyingError: Optional(Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected character '' around line 1, column 1." UserInfo={NSDebugDescription=Unexpected character '' around line 1, column 1., NSJSONSerializationErrorIndex=0}))) [DiscordKitCore] Error decoding message
2023-10-12T13:36:47+0200 warning RobustWebSocket : timeout=4.0 [DiscordKitCore] Connection timed out
2023-10-12T13:36:47+0200 warning RobustWebSocket : [DiscordKitCore] Forcibly closing connection
2023-10-12T13:36:47+0200 info RobustWebSocket : [DiscordKitCore] [RECONNECT] Preemptively attempting reconnection
2023-10-12T13:36:47+0200 info RobustWebSocket : attempt=1 connectIn=3.8000000000000003 [DiscordKitCore] Retrying connection
2023-10-12T13:36:47+0200 warning RobustWebSocket : [DiscordKitCore] Already reconnecting, not reconnecting
2023-10-12T13:36:47+0200 warning RobustWebSocket : [DiscordKitCore] [WS CLOSED] closeCode: 1006
2023-10-12T13:36:47+0200 error RobustWebSocket : [DiscordKitCore] [WS CLOSED] closed with error: no error description
2023-10-12T13:36:47+0200 warning RobustWebSocket : [DiscordKitCore] Already reconnecting, not reconnecting
2023-10-12T13:36:51+0200 info RobustWebSocket : version=9 ws=wss://gateway.discord.gg/?v=9&encoding=json&compress=zlib-stream [DiscordKitCore] [CONNECT]
2023-10-12T13:36:51+0200 info RobustWebSocket : [DiscordKitCore] [CONNECTED]```

@nnzo
Copy link

nnzo commented Oct 13, 2023

I've never built with xCode before but I've managed to fix the bug causing this.. it's only a temporary fix as I've disabled stream compression and Swiftcord will run a lot slower than usual, but nevertheless it's still a fix.

If you'd like to fix the bug yourself and build it, follow these steps: (otherwise at the bottom of this comment you can find my built version).

  1. Download both Swiftcord and DiscordKit from Github
  2. Open the Swiftcord project in xCode and drag your local DiscordKit into the project navigator
  3. Find DiscordKit > Sources > DiscordKitCore > DiscordKitConfig and modify line 182 from streamCompression: Bool = true to streamCompression: Bool = false
  4. Build for your mac

Let me know if the below binary works!
Swiftcord.zip

@khurshid-alam
Copy link

@nnzo

Yes!. That seems to work. Logged in now. Thanks.

@nnzo
Copy link

nnzo commented Oct 13, 2023

@khurshid-alam Another update - a proper fix has been pushed to the DiscordKit repo and a full fix will be on the way shortly according to @cryptoAlgorithm in the Discord.

Make sure to switch over to the proper version instead of mine because it sounds like it'll run a lot faster.

@toshmukhamedov
Copy link

+1
image

@Duskiee
Copy link

Duskiee commented Oct 15, 2023

there is currently an updated package on the discord server
https://cdn.discordapp.com/attachments/964741354339057689/1162599122365337620/Swiftcord_2.zip?ex=653c85ce&is=652a10ce&hm=3f995664004fdfbb026fd1a7189b9c7a8d5895fd1c584cd063b284c5521ab03b&

@Kusanalee
Copy link

Kusanalee commented Nov 8, 2023

Swiftcord 2.zip
here's a more permanent copy of that since discord is killing off permanent cdn links soon (i.e. making it temporary which makes it expire after 24 hours)

@cryptoAlgorithm
Copy link
Member

Thanks everyone, sorry I had not been able to partake in this discussion as my schedule was quite messed up the past few month. I will be publishing an official release to GitHub soon, containing a fix for this issue. Once again apologies this took so long!

@cryptoAlgorithm
Copy link
Member

Hi everyone, https://github.com/SwiftcordApp/Swiftcord/releases/tag/v0.7.1 I've made a release incorporating this patch, as well as some other fixes I had previously worked on. Hope this works, feel free to reopen if there are any related concerns!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Waiting for this issue to be triaged
Projects
None yet
Development

No branches or pull requests