Gwyn

@sithembiso `wails dev` exposes two ports, one on localhost:3000 and the other on localhost:34115. Not sure if this is your issue, but if you choose localhost:3000 you'll get this problem...

> I don't think so. But again, the problem was in my code, not in wails. I've miscommunicated, sorry! My question was aimed at the original reporter. I've updated it...

I've been taking a look at this, and I'd like to develop the fix. Here's what I've figured out so far. Building a macOS app comes in two parts: compiling...

This isn't a huge check-in, but as I've been fixing this I keep getting tripped up by the difference between the Universal and the individual architecture builds, so I decided...

Just a note to say I’m still on this, but during the week I have work and find it hard go get the time to redirect back. I did reach...

I have a draft PR for a fix up; I do need to finish the tests, but I wanted to ask some guidance. The request here was for the output...

It's time to get into spooky behaviour. I opened up Info.plist in my build app and added a CFBundleDisplayName key with a new value in it, but when I open...

This looks promising https://github.com/wailsapp/wails/blob/master/v2/internal/frontend/desktop/darwin/window.go#L68 I'll need to figure out what data is being sent in there. This'll be a stretch of my skills, I think 😅

Yes! I just reached the same point! In that case, I'm not sure how to handle this just yet, as it'd involve overriding user-provided source code. My thoughts are currently...

I think I'll have time to get the testing done on this over the weekend. There _is_ a draft PR at https://github.com/wailsapp/wails/pull/2358; the patch is surprisingly tiny. > p.s if...