search

shaps80 / SwiftUIBackports

A collection of SwiftUI backports for iOS, macOS, tvOS and watchOS
MIT License
931 stars 59 forks source link

Does .backports.onChange {} really work on macOS 10.15 Catalina? #33

Closed ShikiSuen closed 1 year ago

ShikiSuen commented 1 year ago

Have you read the Contributing Guidelines?

General Information

I tried this on my macOS 10.15 virtual machine but find that it doesn't execute the {}-bracketed contents at all.

Describe the bug

(See general information.)

I have no way to create a standalone project demonstrating this issue due to the failure of compiling this package in a new project (targeting macOS 10.15). Once this compilation issue gets solved, I can provide a bare-bone project demonstrating this issue.

image

Steps to reproduce

Provide numbered steps to follow that reproduce the bug.

Expected behavior

Clearly and concisely describe what you expected to happen.

Stack trace, compiler error, code snippets

Paste the full output of any stack trace or compiler error. Include a code snippet that reproduces the described behavior, if applicable

Screenshots

If applicable, add screenshots, gifs, or videos to help explain your problem.

Additional context

Add any other useful information about the problem here.

shaps80 commented 1 year ago

I’m confused by the title here. Are you saying the project doesn’t compile against macOS using the latest release?

If you’re talking about an unreleased version that could be true but I wasn’t aware of any release builds having this issue atm?

ShikiSuen commented 1 year ago

Hi. Thanks for your response.

I mean... it gets compiled successfully, but the things bracketed in .backports.onChange {} simply doesn't execute in macOS Catalina.

It's just my case and I decided to letting you know that there's a thing of such. I just want to hear whether it works fine on your side (in macOS 10.15).

Thank you for stating that your release builds are proved fine on your side. This indicates that my issue might be project-specific, and I'm gonna close this issue for now (unless something new happens).

shaps80 commented 1 year ago

@ShikiSuen thanks for letting me know.

It could be in the framework but I’ve not had other reports like this and its been working for me fine across several projects so I’m unaware of any issues sorry.

Do let me know if you discover it is on my end though, as I’d want to know for sure 👍🏻