Opening the latest release (0.2.2) triggers a gatekeeper alert I had never seen before.

This is unlike the regular popup for unsigned/unverified apps which require you to bypass it manually in the system settings. This popup suggests that this app was actively flagged as being malicious by Apple.

It is possible to compile Switftcord on older macOS versions?

Since SwitfUI is a unified GUI framework since macOS 10.15, compiling for older macOS versions should be possible.
I mean, macOS Catalina and Big Sur are also capable of running SwiftUI widgets used by Swiftcord.

Is there any problem in compiling on these macOS versions? I can be a tester if necessary.

Describe the bug
When the app remains in the background for a long time, macOS "suspends" network activity, including WebSockets. This causes heartbeat ACKs to go missing, and the connection will eventually be terminated due to the threshold of pending heartbeat ACK being exceeded. In such a scenario, another WebSocket should be opened, and the session resumed. Unfortunately, a bug causes the connection to be immediately terminated again right after reconnection, which I suspect is due to the heartbeat timers not being stopped properly and the pending ACKs not being reset.

To Reproduce

1. Keep the app open in the background for a long time
2. Observe how the connection is broken and the socket being closed immediately after opening

Expected behavior

The socket reconnects and resumes in such a scenario.

Logs

https://gist.github.com/cryptoAlgorithm/ba1a390899f41d28b71d6bf027266815

Additional context

There were also a few connection drops due to sleep/internet connection loss, might have made the issue more serious.

Describe the Bug

server bar goes beyond divider

it shouldn't do that

Reproducing the Bug

do nothing

Version

0.4.5

Category

Other

Relevant Log Output

No response

Screenshots

Additional Info

No response

Version 0.4.4(11)

Stacktrace

DiscordKitCore.DecompressionEngine.push_data(Foundation.Data) -> Swift.String? (DecompressionEngine.swift:58);Swiftcord

closure #1 (Swift.Result<(extension in Foundation):__C.NSURLSessionWebSocketTask.Message, Swift.Error>) -> () in DiscordKitCore.RobustWebSocket.(attachSockReceiveListener in _A386195F83E543A29375DB207BC98EE8)() -> () (RobustWebSocket.swift:147);Swiftcord

Reason

SIGSEGV

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/852881004u

Version 0.4.5(12)

Stacktrace

main (SwiftcordApp.swift:15);Swiftcord

Reason

SIGTRAP

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/291392331u

Some files that are required to build the program are not found in the repo but xcode knows they should be there.
The files that are required are:

• views/ServerButton.swift
• views/ServerView.swift
• utils/CodableThrowable.swift

Describe Your Request

Please add Japanese as a language!

Category

Other

Other Category

Translation

Screenshots

No response

When loading channels i get this error

<E> [DiscordGateway] Unknown close code: 1000
2022-04-13 07:18:59.697935+0100 Swiftcord[37958:1482007] [SwiftUI] Publishing changes from background threads is not allowed; make sure to publish values from the main thread (via operators like receive(on:)) on model updates.

and when looking into xcode

Im not sure if this warning is turning into an error or not due to my account having server folders and Swiftcord not supporting that just yet or its an actual error. So i have 2 questions. How do i log out of my account before fully loading in? and Is there a way to solve this warning?

Describe the bug
Can't compile from source:

Dependencies could not be resolved because no versions of 'lottie-ios' match the requirement 3.3.0..<4.0.0 and root depends on 'lottie-ios' 3.3.0..<4.0.0.

To Reproduce
Xcode -> Source Control -> Clone...

Currently roles and permissions aren't handled (except cosmetically in the user profile popover). Channels that you do not have permission to view aren't hidden, and you can send messages to channels you do not have permission to post in.

This is probably a SwiftUI bug, and I've been searching for workaround to it but have found none.

Describe the bug
When typing a long message into the message field, the text does not wrap once it hits the end of the field.
Although newlines work (opt + return), the text does not wrap anymore like it did before with TextEditor

To Reproduce

1. Type very long text in the message field
2. Notice how the text does not scroll, but you can still input text into the field
3. Send the message and note that the text that was entered beyond the width of the field is present

Expected behavior
The text wraps to the next line

Screenshots

Note the cut-off 't' that appears after the cursor

Additional context
Text wrapping used to work while a TextEditor was used, but newlines didn't. Now, its the opposite xD

Currently the add button in the message input field does nothing, and uploading files (especially images) is especially important.

Just an idea for a feature/bootstrap, maybe voice implementation and other API's can be forked from https://github.com/nuclearace/SwiftDiscord.

Describe the bug

To Reproduce

1. Login in Swiftcord
2. Close App
3. Open App
4. See error

Expected behavior
Show Channels, Messages ... Views

Screenshots

Logs

Adding a better logging system might be required. to-do

Describe the bug

For some reason my nitro badge is being duplicated and overlapped ontop of my hypesquad badge. idk if this will occur with other badges or if it happens with a set amount etc.
To Reproduce

Open a users profile who has HS balance & nitro badges

Expected behavior
No duplication and or overlap
Screenshots
Swiftcord:

standard client:

Logs

Additional context

Version 0.4.1(8)

Stacktrace

DiscordKit.DecompressionEngine.push_data(Foundation.Data) -> Swift.String? (DecompressionEngine.swift:58);Swiftcord

closure #1 (Swift.Result<(extension in Foundation):__C.NSURLSessionWebSocketTask.Message, Swift.Error>) -> () in DiscordKit.RobustWebSocket.(attachSockReceiveListener in _F1774E6A520C990059FB4817E840CF73)() -> () (RobustWebSocket.swift:144);Swiftcord

Reason

SIGABRT

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/867091571u

A megathread for penning down everything macOS 13 breaks/fixes

macOS 13 is still in beta 1, so hopefully these bugs get ironed out soon.

When the app is minimized or the sidebar is closed, the # button should open the sidebar or open a popover list of all channels in the server.

This would improve the UX and would be logical for when the app is docked to a side of the screen.

Keep up the great work!

• Homebrew Support

Not a bug just an extra feature request! Perhaps connecting with GitHub Actions so a new release is built on every new version/milestone. Because right now building the entire project would be quite a hassle, and as the other issue states, building isn't possible in the current state. Awesome project btw looks so much like the original Discord app. Great work!!

For people like me who are on way too many servers but only actually chat in select few channels on each one, it would be nice to have a “favourite channels” tab where you could just put a selection of channels, so you don’t have to keep flicking between a gazillion different servers (similar to what Ripcord does).

(This is almost definitely a SwiftUI bug) If the message list is scrolled up, and the channel is changed, the placeholder sometimes does not load and hence no messages load.

This is due to the list still being stuck at the original scroll position even though there is no more content there, which causes the messages placeholder not to load. Due to how I design message loading, the messages do not load if the placeholder doesn't appear.

However, when the window is resized, it causes the scrollView to recalculate something and it suddenly realises the content height changed. Then it scrolls to where it should be, the placeholder appears and the messages load. This further compounds my suspicion that this is a SwiftUI bug.

Describe the bug
When collapsing the channel list again via the “#” button, the window should resize to what the state was prior to being expanded

To Reproduce

1. Dock the app to the side of the screen and reduce the size
2. Press #
3. Find your channel, and press #
4. When hiding the channel list, the window size doesn't go back to the minimized state.

Expected behavior
When pressing the # button to collapse the channel list, the channel list should get smaller, and the chat display should stay the same size. At the current moment, the chat gets bigger while the channel lists collapses.

It's not really a bug per se, something I do very often is to paste an image into the input field, I find that it's not supported yet in Swiftcord, would be nice to have it in future iterations.

Thanks for creating this project!

Version 0.4.1(8)

Stacktrace

main (SwiftcordApp.swift:14);Swiftcord

Reason

SIGILL

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/1806249957u

Describe the Bug

Enhancement
I cannot paste an image I have copied on my clipboard.

Expected Behavior
An image should be pasted as it does in the official discord client.

Category

Media (images, audio, video etc.)

Version 0.4.1(8)

Stacktrace

$s16CachedAsyncImageAAV4load33_1115941DA3DEE378C52E09DA49AE1AD2LLyyYaYbFyyXEfU1_ (CachedAsyncImage.swift:335);Swiftcord

partial apply forwarder for reabstraction thunk helper from @callee_guaranteed () -> (@error @owned Swift.Error) to @escaping @callee_guaranteed () -> (@out (), @error @owned Swift.Error) (:0);Swiftcord

reabstraction thunk helper from @callee_guaranteed () -> (@error @owned Swift.Error) to @escaping @callee_guaranteed () -> (@out (), @error @owned Swift.Error)partial apply forwarder with unmangled suffix ".8" + 8;Swiftcord

$s16CachedAsyncImageAAV4load33_1115941DA3DEE378C52E09DA49AE1AD2LLyyYaYbFTQ0_ (CachedAsyncImage.swift:334);Swiftcord

Reason

SIGABRT

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/3402362575u

version 0.4.1

Describe the bug

I checked on servers and in my DMs, but when someone sends a GIF, only the URL is displayed with a block underneath it. You can still click on the link to view the GIF in your browser, but needless to say, this is not the best solution :,)

I'm sorry to break it to you but https://twitter.com/discord/status/1229357198918197248

Just fix the readme

Describe the bug
when clicking any menu items (bar at top of screen) they show up for a split second and then disappear, not to mention getting them to trigger is janky for some reason
To Reproduce

1. click any menu item

Expected behavior
for the dropdown to show as intended and stay until unfocused
Screenshots
https://user-images.githubusercontent.com/44528100/171665531-b5167f99-097a-479e-b293-9443d1e21a70.mov
Logs

Additional context

Describe the Bug

Bug Description
When moving the mouse over one of the icons representing a server in the sidebar server list, the mouse cursor sometimes briefly (seems to be about 1 frame) changes to the pointing hand cursor instead of the arrow cursor.

I attempted to record a video of the glitch occurring, but it seems that the video did not pick up every instance of the glitch. https://youtu.be/E76HkcnRaMs

Actual Behaviour
The pointing hand cursor sometimes briefly appears when hovering server icons.

Expected Behavior
The pointing hand cursor should never appear when hovering server icons, the traditional arrow cursor should only be used in this location.

Reproducing the Bug

1... Hover over a server
2... Repeat until the wrong cursor appears
3... Observe that the wrong cursor has appeared briefly

Version

0.4.5 (12)

Category

Other

Relevant Log Output

No response

Screenshots

No response

Additional Info

macOS 12.5 Monterey
intel macbook 2020

Hello, I love the concept of your app (it's beautiful ❤️) BUT I'm stuck on this screen:

(I'm connected, the "preferences" menu works)

Here are the errors in Xcode :

Thank you in advance for your response

Version 0.4.5(12)

Stacktrace

DiscordKitCore.DecompressionEngine.(decompress in _011348DEE0EBF1DDE39324940856E45D)(Foundation.Data) -> Foundation.Data (:0);Swiftcord

DiscordKitCore.DecompressionEngine.push_data(Foundation.Data) -> Swift.String? (DecompressionEngine.swift:65);Swiftcord

closure #1 (Swift.Result<(extension in Foundation):__C.NSURLSessionWebSocketTask.Message, Swift.Error>) -> () in DiscordKitCore.RobustWebSocket.(attachSockReceiveListener in _A386195F83E543A29375DB207BC98EE8)() -> () (RobustWebSocket.swift:147);Swiftcord

Reason

SIGSEGV

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/3784116973u

The file MiscSettingsView.swift is missing from the cloned repo

Describe the bug
Upon launching Swiftcord, I am presented with an endless "Establishing connection" view.

When I look at the logs (running in Xcode), I see a couple of decoding errors that seem to be stalling the process:

dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "t", intValue: nil)], debugDescription: "Cannot initialize GatewayEvent from invalid String value READY_SUPPLEMENTAL", underlyingError: nil))
[…]
dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "t", intValue: nil)], debugDescription: "Cannot initialize GatewayEvent from invalid String value SESSIONS_REPLACE", underlyingError: nil))
{"t":"SESSIONS_REPLACE","s":3,"op":0,"d":[{"status":"online","session_id":"my-session-id-is-here","client_info":{"version":0,"os":"osx","client":"desktop"},"activities":[]}]}

Including but not limited to: more accurate headers, sequencing of gateway events, gateway zlib-stream compression, etc.

Clicking into any DMs causes Swiftcord to send out a malformed event subscribe (for typing events etc) payload to the gateway, causing an immediate connection termination and session invalidation. Check if server is a DM and don't subscribe to events, since events are automatically sent for DMs.

Version 0.4.3(10)

Stacktrace

main (SwiftcordApp.swift:15);Swiftcord

Reason

SIGTRAP

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/514924801u

Version 0.4.4(11)

Stacktrace

$s16CachedAsyncImageAAV4load33_1115941DA3DEE378C52E09DA49AE1AD2LLyyYaYbFyyXEfU1_ (CachedAsyncImage.swift:335);Swiftcord

partial apply forwarder for reabstraction thunk helper from @callee_guaranteed () -> (@error @owned Swift.Error) to @escaping @callee_guaranteed () -> (@out (), @error @owned Swift.Error) (<compiler-generated>:0);Swiftcord

reabstraction thunk helper from @callee_guaranteed () -> (@error @owned Swift.Error) to @escaping @callee_guaranteed () -> (@out (), @error @owned Swift.Error)partial apply forwarder with unmangled suffix ".8" + 8;Swiftcord

$s16CachedAsyncImageAAV4load33_1115941DA3DEE378C52E09DA49AE1AD2LLyyYaYbFTQ0_ (CachedAsyncImage.swift:334);Swiftcord

Reason

SIGABRT

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/3148303593u

Trying this out as a native alternative to Ripcord (by cancel.fm)! Looks like a cool project!
When I open the app it seems to just sit on "Establishing Gateway connection" without progressing.

Looking at its network traffic in LittleSnitch, it sends a request to "discord.gg" when first launched but it never gets a reply and it does not make any more requests.

Swiftcord v0.2.2(3) - Pre-built provided on GitHub
MacOS v12.3.1
Macbook Pro M1 Pro

DMs haven't been a big priority for Swiftcord since lets be honest, you definitely use DMs much less often than servers (if not why use Discord lol). This issue will fix broken DMs, since currently the name of the DM is simply just '' (nothing). It will also allow you to finally send DMs, so finally you can respond to that friend you've left read for way too long.

Version 0.4.4(11)

Stacktrace

closure #1 (DiscordKitCommon.GatewayEvent, DiscordKitCommon.GatewayData?) -> () in closure #6 () -> () in Swiftcord.ServerView.body.getter : some (ServerView.swift:0);Swiftcord

reabstraction thunk helper from @escaping @callee_guaranteed (@unowned DiscordKitCommon.GatewayEvent, @in_guaranteed DiscordKitCommon.GatewayData?) -> () to @escaping @callee_guaranteed (@in_guaranteed (DiscordKitCommon.GatewayEvent, DiscordKitCommon.GatewayData?)) -> () (:0);Swiftcord

partial apply forwarder for reabstraction thunk helper from @escaping @callee_guaranteed (@in_guaranteed A) -> () to @escaping @callee_guaranteed (@in_guaranteed A) -> (@out ()) (:0);Swiftcord

partial apply forwarder for reabstraction thunk helper from @escaping @callee_guaranteed (@in_guaranteed A) -> (@out ()) to @escaping @callee_guaranteed (@in_guaranteed A) -> () (:0);Swiftcord

partial apply forwarder for closure #1 () -> () in DiscordKitCommon.EventDispatch.notify(event: A) -> () (EventDispatch.swift:101);Swiftcord

reabstraction thunk helper from @escaping @callee_guaranteed () -> () to @escaping @callee_unowned @convention(block) () -> () (:0);Swiftcord

main (SwiftcordApp.swift:15);Swiftcord

Reason

SIGTRAP

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/2592686302u

Especially while scrolling, CPU usage sometimes shoots up to 90% and above. While idling, CPU usage is around 15-30%, which is unsatisfactory. The aim is to at least match the official client in CPU usage, which is less than 10% while idling, and almost no scroll jank.

These observations were made on a 14" 10c M1 Pro, so your experience might vary.

Version 0.4.5(12)

Stacktrace

merged closure #1 () -> () in closure #1 () -> SwiftUI.TupleView<(<<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, SwiftUI.Divider, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, SwiftUI.Divider, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(_: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0)> in Swiftcord.NavigationCommands.body.getter : some + 1892;Swiftcord

partial apply forwarder for closure #1 () -> () in closure #1 () -> SwiftUI.TupleView<(<<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, SwiftUI.Divider, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0, SwiftUI.Divider, <<opaque return type of (extension in SwiftUI):SwiftUI.View.keyboardShortcut(_: SwiftUI.KeyEquivalent, modifiers: SwiftUI.EventModifiers) -> some>>.0)> in Swiftcord.NavigationCommands.body.getter : some (:0);Swiftcord

main (SwiftcordApp.swift:15);Swiftcord

Reason

SIGTRAP

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/4199375089u

Describe the bug

It seems that RichEmbeds containing markdown text are not properly rendering.

To Reproduce

1. Go to a channel with RichEmbed messages including markdown text inside.

Expected behavior

See screenshots

Screenshots

First one is SwiftCord, the other one is Discord
https://imgur.com/a/rBOkGFO

Additional context

I'm not sure if this is a problem or not as I saw that "Rich message rendering" should work fine on the roadmap.
So just in case 🤷‍♂️
ALSO the "author" field does not appear in the Rich Embed either (see the top part of it in the screenshots)

By the way, I really appreciate your work!! The UI looks soo good and Discord should defintively make a native version instead of electron... Can't wait to see Voice channels haha

Version 0.4.3(10)

Stacktrace

DiscordKitCore.DecompressionEngine.push_data(Foundation.Data) -> Swift.String? (DecompressionEngine.swift:58);Swiftcord

closure #1 (Swift.Result<(extension in Foundation):__C.NSURLSessionWebSocketTask.Message, Swift.Error>) -> () in DiscordKitCore.RobustWebSocket.(attachSockReceiveListener in _A386195F83E543A29375DB207BC98EE8)() -> () (RobustWebSocket.swift:147);Swiftcord

Reason

SIGSEGV

Link to App Center

• https://appcenter.ms/orgs/Swiftcord/apps/Swiftcord/crashes/errors/2066844195u

Describe the bug
Closing the window quits the app.

To Reproduce

1. Open Swiftcord
2. Close the window using ⌘W or "Close" menu item

Expected behavior
On macOS, closing a window of an app should not quit the app.