[Bug]: Desktop app on macOS budget loading error #2705

Stryd3r · 2024-05-04T17:45:51Z

Verified issue does not already exist?

I have searched and found no existing issue
I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

I successfully downloaded the desktop app on my Mac and when I connect to my fly.io account and load the budget I’m getting an error. Errors are “We had an unknown problem opening “My Finance dcb1c51” and I’m also unable to browse to the exported .json file. Occasionally I’m also getting the “something went wrong trying to download that file error”.

Additional information:
I’m facing this issue on- Client version: v24.5.0
Server version: v24.5.0

Screenshots attached.

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

cjtodaro · 2024-05-04T18:23:43Z

I'm having the same issue. Trying to run desktop app on MacOS 14.4.1. ActualBudget hosted on unRAID 6.12.8

The error message file name doesn't match the budget file I'm trying to open either.

FeralFlora · 2024-05-04T20:46:26Z

I have a similar issue on Windows 11, but in my case, the download load screen just goes on forever:

My Actual server is hosted on Pikapods, and the server version is 24.4.

lukebouch · 2024-05-04T21:09:26Z

I'm having the same issue.

moobaabaa · 2024-05-05T15:00:53Z

Same with desktop app. Browser access works fine.

Self-hosted (local)
Apple M1 Mac mini
Sonoma 14.1.1

youngcw · 2024-05-06T15:22:59Z

Can someone try out the build available here and confirm if its working for you or not? https://github.com/actualbudget/actual/actions/runs/8971187425?pr=2715

It should fix the loading issue. You will need to download the file listed as "actual-electron-macos-latest". That is a zip file that contains the desktop app.

cjtodaro · 2024-05-06T22:37:02Z

Can someone try out the build available here and confirm if its working for you or not? https://github.com/actualbudget/actual/actions/runs/8971187425?pr=2715

It should fix the loading issue. You will need to download the file listed as "actual-electron-macos-latest". That is a zip file that contains the desktop app.

That fixed it for me!

moobaabaa · 2024-05-07T14:29:58Z

Excellent! Thanks for the updated file. Works for me.

psybers · 2024-06-05T03:07:55Z

This seems to be broken again.

MatissJanis · 2024-06-05T18:40:05Z

Ok, so I'm really confused. Building the desktop app locally works just fine. Building the same source via CI/CD - creates a broken build.

Code signing and other things are all turned off. So I'm really lost as to what is going on which makes it very hard to debug and patch the issue.

youngcw · 2024-06-05T18:56:25Z

@MatissJanis Could you upload a good working build to the release? That way people can use it while we try to determine why the autobuild is broken.

MatissJanis · 2024-06-05T20:53:02Z

Good idea. Uploaded my local build to the release as a temporary solution: https://github.com/actualbudget/actual/releases/tag/v24.6.0

MatissJanis · 2024-06-05T21:26:29Z

@youngcw had a brilliant idea: the issue might have to do with the Github CI runners.

Here's a CI job that was building a working artefact: https://github.com/actualbudget/actual/actions/runs/8971187425/attempts/1

So I re-ran the same exact job and it failed: https://github.com/actualbudget/actual/actions/runs/8971187425/attempts/2

This points to the issue being in the runner. Now we just need to figure out what changed and how to change it back.

psybers · 2024-06-06T18:10:18Z

@MatissJanis I would guess the issue is the non-pinned OS version:

The passing run:

Operating System
  macOS
  14.4.1
  2[3](https://github.com/actualbudget/actual/actions/runs/8971187425/job/24636381309#step:1:3)E224
Runner Image
  Image: macos-1[4](https://github.com/actualbudget/actual/actions/runs/8971187425/job/24636381309#step:1:4)-arm64
  Version: 20240422.3
  Included Software: https://github.com/actions/runner-images/blob/macos-14-arm[6](https://github.com/actualbudget/actual/actions/runs/8971187425/job/24636381309#step:1:7)4/20240422.3/images/macos/macos-14-arm64-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-14-arm64%2F20240422.3

and the failing run:

Operating System
  macOS
  14.5
  2[3](https://github.com/actualbudget/actual/actions/runs/8971187425/job/25863389615#step:1:3)F79
Runner Image
  Image: macos-1[4](https://github.com/actualbudget/actual/actions/runs/8971187425/job/25863389615#step:1:4)-arm64
  Version: 20240[6](https://github.com/actualbudget/actual/actions/runs/8971187425/job/25863389615#step:1:7)03.1
  Included Software: https://github.com/actions/runner-images/blob/macos-14-arm64/20240603.1/images/macos/macos-14-arm64-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-14-arm64%2F20240603.1

What exactly changed in macOS that is causing the issue, I do not know. But other than that, and the fact the artifact size is slightly different, I do not spot any differences in the logs of the two runs.

MatissJanis · 2024-06-06T18:25:36Z

Any ideas how to pin to a specific runner version?

youngcw · 2024-06-06T18:27:36Z

Looks like we can only pin to major versions so even if we specified macos-14 we would probably still have the same issue

youngcw · 2024-06-06T18:30:19Z

Maybe this project could help. https://github.com/pd4d10/debugtron

psybers · 2024-06-06T18:32:06Z

Any ideas how to pin to a specific runner version?

AFAIK you can not. You can only select major release, e.g. -13 or -14 instead of -latest.

psybers · 2024-06-06T18:36:56Z

I used the debugtron and see this when opening a local file:

[Exception] Error: dlopen(/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS, 0x0001): tried: '/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h' or 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (no such file), '/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h' or 'x86_64')), '/private/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h' or 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (no such file), '/private/var/folders/gf/vvdfvl3939lgvrcnb11djrgsxvgdnv/T/.com.actualbudget.actual.hUXpBS' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h' or 'x86_64'))
    at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:2131)
    at Object.<anonymous> (node:internal/modules/cjs/loader:1356:18)
    at Object.func [as .node] (node:electron/js2c/asar_bundle:2:2358)
    at Module.load (node:internal/modules/cjs/loader:1126:32)
    at node:internal/modules/cjs/loader:967:12
    at Function._load (node:electron/js2c/asar_bundle:2:13327)
    at Module.require (node:internal/modules/cjs/loader:1150:19)
    at require (node:internal/modules/cjs/helpers:121:18)
    at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)
    at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {
  code: 'ERR_DLOPEN_FAILED'
}

psybers · 2024-06-06T18:37:30Z

Have we ever confirmed if the mac images fail on both Intel and M1/M2 macs? I am on an Intel mac.

GitHub's latest macos image is arm only.

MatissJanis · 2024-06-06T18:39:53Z

I'm on Intel too.

cpisto · 2024-06-06T18:42:12Z

I'm on Apple silicon and the original released 24.6.0 image fails for me, suggesting it is not an architecture specific issue.

MatissJanis · 2024-06-06T18:47:42Z

Maybe related: actions/runner-images#9995

cpisto · 2024-06-06T18:54:08Z

Between 24.5.0 and 24.6.0 better-sqlite3 was upgraded from 9.1 to 9.6, between those versions better-sqlite3 was updated to support native arm builds on macOS, perhaps something broke there if the GitHub runner changed from x86 to arm between working and not working?

cpisto · 2024-06-07T19:08:07Z

This is quite the rabbit hole. I'm wondering if the actions/cache is caching the node_modules from the previous arm node runtime. Something like this:

vitejs/vite-plugin-react-swc#74

cpisto · 2024-06-07T19:21:17Z

It looks like it is- the cache key is only based on the os, not the architecture. So the now x86/x64 node runtime is using the cached node_modules for arm, which is likely where the "Bindings not found." error is coming from during the Electron build step.

tdeebswihart · 2024-08-03T20:41:09Z

I'm encountering this on the most recently released version:

Actual.app/Contents/MacOS took 6s
$ ./Actual
[Exception] Error: dlopen(/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V, 0x0001): tried: '/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (no such file), '/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (no such file), '/private/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))

$ file /var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V
/var/folders/hg/lsbm785s2p7g5t7ltsw8ddnr0000gn/T/.com.actualbudget.actual.J0n83V: Mach-O 64-bit bundle x86_64

Neosaurus · 2024-08-04T06:56:20Z

I'm experiencing this bug on the latest version also.

geeklihui · 2024-08-08T07:31:03Z

Same here, version: 24.8.0
M1 Macbook Pro.
Running in locally.

Kidglove57 · 2024-08-08T10:43:07Z

Same here, version: 24.8.0 M1 Macbook Pro. Running in locally.

This might just be the error I had on Silicon? Solved for me by enabling Rosetta for now.

geeklihui · 2024-08-09T07:04:08Z

Same

Are you using the latest version too? If so, then maybe relative with chip type. I'm using M1Pro with Rosetta on. But why it need Rosetta? It's arm architecture.

MikesGlitch · 2024-08-10T19:25:50Z

To keep this thread in the loop, I think it's fixed here:

https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

For those with Arm CPU's, can you try out the latest build and tell me what you see?

I think some of you may see "this file is damaged" due to some Apple nonsense about notarizing the app (we plan on fixing that).

If you see the damaged file warning, I think running the below command will fix it:

 xattr -c <path/to/application.app>

Can someone confirm?

TheRebootr · 2024-08-11T06:58:42Z

Hello @MikesGlitch ,

I just downloaded and installed the current Release today [v24.8.0].

I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.

Machine:
Macbook Pro M3

MikesGlitch · 2024-08-11T12:11:59Z

Hello @MikesGlitch ,

I just downloaded and installed the current Release today [v24.8.0].

I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.

Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?

https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

MatissJanis · 2024-08-11T17:51:26Z

Thanks for checking. I think I fixed it here, can I get someone to try again?

https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

✅ This works on Intel if that helps (don't have an ARM machine).

MikesGlitch · 2024-08-12T09:31:12Z

I have a PR up with the fix, thanks for the help everyone! 🚀

MikesGlitch · 2024-08-12T21:52:32Z

Fixed by #3220

geeklihui · 2024-08-14T05:43:38Z

To keep this thread in the loop, I think it's fixed here:

https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

For those with Arm CPU's, can you try out the latest build and tell me what you see?

I think some of you may see "this file is damaged" due to some Apple nonsense about notarizing the app (we plan on fixing that).

If you see the damaged file warning, I think running the below command will fix it:
 xattr -c <path/to/application.app>
Can someone confirm?

It worked for me too! (M1Pro) Thanks!

Neosaurus · 2024-08-14T09:11:44Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?

https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

MikesGlitch · 2024-08-14T09:15:20Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?
https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220
Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

Can you confirm that you have the latest artefact and have run the command? If so, what error do you get?

Kidglove57 · 2024-08-14T09:18:37Z

I'm testing the latest build on my M2 Mac. As expected I get the damaged file message. I tried running the command you mentioned. However Terminal is throwing an error:
zsh parse error near \n

MikesGlitch · 2024-08-14T09:21:25Z

Are you running the command with the <> brackets? If you remove them it should work

A real life command might look similar to

 xattr -c path/to/Actual.app

Neosaurus · 2024-08-14T09:21:46Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?
https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220
Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

Can you confirm that you have the latest artefact and have run the command? If so, what error do you get?

The same as before, with an "unknown error opening x file". My server is running the latest version. I had to run the xattr command to get it to work

MikesGlitch · 2024-08-14T09:29:07Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?
https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220
Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

Can you confirm that you have the latest artefact and have run the command? If so, what error do you get?

The same as before, with an "unknown error opening x file". My server is running the latest version. I had to run the xattr command to get it to work

This is odd because others have reported it working - and an arm64 should work the same no matter what machine its on.

Can you try removing it from your system, then re-downloading it from https://github.com/actualbudget/actual/releases/tag/v24.8.0 ?

If you still get the error can you open up devtools by clicking the "View" menu > "toggle devtools" > "Console" until you get the error and screen grab it for me?

Kidglove57 · 2024-08-14T09:31:35Z

Still struggling a bit in terminal so?
xattr -c applications/actual.app

MikesGlitch · 2024-08-14T09:51:11Z

Still struggling a bit in terminal so? xattr -c applications/actual.app

For me it was:

xattr -c /applications/actual.app

Kidglove57 · 2024-08-14T09:55:56Z

xattr -c /applications/actual.app

Thank you for persevering with me. I'm not sure what I was doing wrong - maybe incorrect spacing in the command. Anyhow, now working really well and I can confirm that export works too.

Just in case others are reading this - don't expect any response when you enter this command in terminal. But it does work

Neosaurus · 2024-08-15T10:06:02Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?
https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220
Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

Can you confirm that you have the latest artefact and have run the command? If so, what error do you get?

The same as before, with an "unknown error opening x file". My server is running the latest version. I had to run the xattr command to get it to work

This is odd because others have reported it working - and an arm64 should work the same no matter what machine its on.

Can you try removing it from your system, then re-downloading it from https://github.com/actualbudget/actual/releases/tag/v24.8.0 ?

If you still get the error can you open up devtools by clicking the "View" menu > "toggle devtools" > "Console" until you get the error and screen grab it for me?

Here is the error:

I can confirm via Activity Monitor that this is the Apple Silicon release. The server runs on my x86 home server though, which could be the issue?

The previous release still works fine.

Edit: actually I see I'm using the intel release (unbeknownst to me) for the previous version - do I need to match the server architecture and my laptop architecture?

MikesGlitch · 2024-08-15T10:52:40Z

Hello @MikesGlitch ,
I just downloaded and installed the current Release today [v24.8.0].
I still have this error. However, as advised by @Kidglove57 above, I enabled Rosetta and that resolved the issue for now.
Machine: Macbook Pro M3

Thanks for checking. I think I fixed it here, can I get someone to try again?
https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220
Apologies for all this back and forward, I don't have a Arm64 mac so can't do it myself.

Sadly still present for me :( Also M1 pro MBP 14"

Can you confirm that you have the latest artefact and have run the command? If so, what error do you get?

The same as before, with an "unknown error opening x file". My server is running the latest version. I had to run the xattr command to get it to work

This is odd because others have reported it working - and an arm64 should work the same no matter what machine its on.
Can you try removing it from your system, then re-downloading it from https://github.com/actualbudget/actual/releases/tag/v24.8.0 ?
If you still get the error can you open up devtools by clicking the "View" menu > "toggle devtools" > "Console" until you get the error and screen grab it for me?

Here is the error: I can confirm via Activity Monitor that this is the Apple Silicon release. The server runs on my x86 home server though, which could be the issue?

The previous release still works fine.

Edit: actually I see I'm using the intel release (unbeknownst to me) for the previous version - do I need to match the server architecture and my laptop architecture?

Can we take this to Discord? Hard to have a convo on Github.

Here's the link to the support thread: https://discord.com/channels/937901803608096828/1271969489294200883

geeklihui · 2024-08-18T04:46:40Z

To keep this thread in the loop, I think it's fixed here:
https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220
For those with Arm CPU's, can you try out the latest build and tell me what you see?
I think some of you may see "this file is damaged" due to some Apple nonsense about notarizing the app (we plan on fixing that).
If you see the damaged file warning, I think running the below command will fix it:
 xattr -c <path/to/application.app>
Can someone confirm?
It worked for me too! (M1Pro) Thanks!

Hello @MikesGlitch, not sure if it related to this issue, but the export was error in macOS.

debug info:

MikesGlitch · 2024-08-18T07:26:24Z

Hello @MikesGlitch, not sure if it related to this issue, but the export was error in macOS.

That error was unrelated, but it's fixed in the latest release as well (you'll have to download it again to get it).

We also have automatic backups in the Electron app - there's not much reason to do a manual export 👍

Stryd3r added the bug Something isn't working label May 4, 2024

MatissJanis mentioned this issue May 6, 2024

🐛 remove mac electron app code-signing #2715

Merged

MatissJanis linked a pull request May 6, 2024 that will close this issue

🐛 remove mac electron app code-signing #2715

Merged

MatissJanis closed this as completed in #2715 May 7, 2024

MatissJanis reopened this Jun 5, 2024

MatissJanis mentioned this issue Jun 5, 2024

[WIP] ⬆️ (electron) upgrade electron dependencies #2844

Closed

2 tasks

MatissJanis mentioned this issue Jun 5, 2024

[WIP] Revert ":electron: Update Electron to latest stable version (#2763)" #2845

Closed

psybers mentioned this issue Aug 6, 2024

[Bug]: We had an unknown problem opening "<local actual file>" #3199

Closed

2 tasks

MikesGlitch mentioned this issue Aug 12, 2024

Fix "Unknown problem opening <local actual file>" on Electron #3220

Merged

MikesGlitch closed this as completed Aug 12, 2024

[Bug]: Desktop app on macOS budget loading error #2705

[Bug]: Desktop app on macOS budget loading error #2705

Comments

Stryd3r commented May 4, 2024 • edited Loading

Verified issue does not already exist?

What happened?

Where are you hosting Actual?

What browsers are you seeing the problem on?

Operating System

cjtodaro commented May 4, 2024

FeralFlora commented May 4, 2024

lukebouch commented May 4, 2024

moobaabaa commented May 5, 2024 • edited Loading

youngcw commented May 6, 2024

cjtodaro commented May 6, 2024

moobaabaa commented May 7, 2024

psybers commented Jun 5, 2024

MatissJanis commented Jun 5, 2024

youngcw commented Jun 5, 2024

MatissJanis commented Jun 5, 2024

MatissJanis commented Jun 5, 2024 • edited Loading

psybers commented Jun 6, 2024

MatissJanis commented Jun 6, 2024

youngcw commented Jun 6, 2024

youngcw commented Jun 6, 2024

psybers commented Jun 6, 2024

psybers commented Jun 6, 2024

psybers commented Jun 6, 2024

MatissJanis commented Jun 6, 2024

cpisto commented Jun 6, 2024

MatissJanis commented Jun 6, 2024

cpisto commented Jun 6, 2024 • edited Loading

cpisto commented Jun 7, 2024

cpisto commented Jun 7, 2024

tdeebswihart commented Aug 3, 2024

Neosaurus commented Aug 4, 2024

geeklihui commented Aug 8, 2024

Kidglove57 commented Aug 8, 2024

geeklihui commented Aug 9, 2024

MikesGlitch commented Aug 10, 2024 • edited Loading

TheRebootr commented Aug 11, 2024

MikesGlitch commented Aug 11, 2024 • edited Loading

MatissJanis commented Aug 11, 2024

MikesGlitch commented Aug 12, 2024 • edited Loading

MikesGlitch commented Aug 12, 2024

geeklihui commented Aug 14, 2024

Neosaurus commented Aug 14, 2024

MikesGlitch commented Aug 14, 2024 • edited Loading

Kidglove57 commented Aug 14, 2024

MikesGlitch commented Aug 14, 2024 • edited Loading

Neosaurus commented Aug 14, 2024

MikesGlitch commented Aug 14, 2024 • edited Loading

Kidglove57 commented Aug 14, 2024

MikesGlitch commented Aug 14, 2024

Kidglove57 commented Aug 14, 2024

Neosaurus commented Aug 15, 2024 • edited Loading

MikesGlitch commented Aug 15, 2024

geeklihui commented Aug 18, 2024

MikesGlitch commented Aug 18, 2024 • edited Loading

Stryd3r commented May 4, 2024 •

edited

Loading

moobaabaa commented May 5, 2024 •

edited

Loading

MatissJanis commented Jun 5, 2024 •

edited

Loading

cpisto commented Jun 6, 2024 •

edited

Loading

MikesGlitch commented Aug 10, 2024 •

edited

Loading

MikesGlitch commented Aug 11, 2024 •

edited

Loading

MikesGlitch commented Aug 12, 2024 •

edited

Loading

MikesGlitch commented Aug 14, 2024 •

edited

Loading

MikesGlitch commented Aug 14, 2024 •

edited

Loading

MikesGlitch commented Aug 14, 2024 •

edited

Loading

Neosaurus commented Aug 15, 2024 •

edited

Loading

MikesGlitch commented Aug 18, 2024 •

edited

Loading