Post

Replies

Boosts

Views

Activity

Reply to DeclaredAgeRange import error in Mac Catalyst app
Thanks for the guidance. I added screenshots just to show the situation more clearly: On iOS devices the app builds and runs fine with import DeclaredAgeRange. On Mac (Catalyst) the same code fails with an import error. I also looked into filing a Feedback report, but honestly the procedure felt quite complex, and I stopped midway. I understand that Apple wants to filter out low-quality reports, but from the perspective of a busy app developer it’s hard to dedicate that much time to reporting SDK issues. So please consider this thread as a reference. For now, I’ll conditionally compile the feature with #if canImport(DeclaredAgeRange) and ship the app that way.
Oct ’25
Reply to DeclaredAgeRange import error in Mac Catalyst app
These are the two cases I’ve tested (with screenshots attached): • First screenshot: Building for iPhone — import DeclaredAgeRange works fine. • Second screenshot: Building for Mac (Catalyst) — import DeclaredAgeRange fails with a module import error.
Replies
Boosts
Views
Activity
Oct ’25
Reply to DeclaredAgeRange import error in Mac Catalyst app
Thanks for the guidance. I added screenshots just to show the situation more clearly: On iOS devices the app builds and runs fine with import DeclaredAgeRange. On Mac (Catalyst) the same code fails with an import error. I also looked into filing a Feedback report, but honestly the procedure felt quite complex, and I stopped midway. I understand that Apple wants to filter out low-quality reports, but from the perspective of a busy app developer it’s hard to dedicate that much time to reporting SDK issues. So please consider this thread as a reference. For now, I’ll conditionally compile the feature with #if canImport(DeclaredAgeRange) and ship the app that way.
Replies
Boosts
Views
Activity
Oct ’25