Not sure how this should work: Opening the mail should automatically add a calendar event without any user interaction? I doubt this is either technical achievable, in alignment with app store policies (without user consent) and what I would like a mail to do as an end-user... Why not go with an .ics attachment and let the user save the event?

Short update:The observed behavior is confirmed by DTS: if the PreviewViewController's view is extended to its superview's edges, all UIGestures are consumed and not processed by QL. Potential bypass: Reduce the view's size left / right (e.g. by constrains) to allow some area for swiping. A bug report is filed and will be brought to the engineering team's attention.Mattes

Hi Quinn,Feedback ID is FB7530945.Take care, Mattes

Thanks a lot, your post made my day after two days of frustrations ... the property scrollEdgeAppearance of UINavigationBarAppearance finally made the trick.With regards to your other problem I filed a RADAR in January 2018 without any success so far.Greetings, Mattes

Sorry to say, but I can just confirm your observation, and I'm going with your workaround (4): A mandatory, undeletable record is created in Group and used by default if Item has no Group assignment. Kind of a hack, but IMHO the best bypass. Mattes

A lot of eye candy ... by jeopardizing usability: I hope that's not the new Apple way. Please provide a way to browse through most recent posts, e.g. by tag: I often don't look for a specific solution, but like to know current discussions, hick-ups, issues and work-arounds. Please consider the most important purpose of a developer forum: It's about content, not marketing... Mattes

Following these - https://stackoverflow.com/questions/56459036/how-does-one-build-a-openssl-library-for-project-catalyst instructions I was at least able to have my project build with Mac Catalyst and OpenSSL: Edit "Configurations/main-10.conf" to add the line "CFLAGS => add("-target x8664-apple-ios13.0-macabi")," into the "darwin64-x8664-cc" section Run "./Configure darwin64-x86_64-cc -shared" Run "make clean" Run "make" Copy libcrypto.a & libssl.a into the library search path, as already used before for iOS targets Copy include/internal and include/openssl into the (recursive) header search path, as already used before for iOS targets The project compiles, links and can be run ... I still need to figure out how to conditionally use the libraries only when linking to Mac Catalyst and not for iOS. Unfortunately receipt validation still fails, assuming because of different paths in the app bundle? I will post a different question addressing this topic. So one step forward and the next challenge identified, Mattes

The OpenSSL libraries librypto.a and libssl.a cannot be defined as conditionally being linked: Due to the same names Xcode is only reflecting one platform version in its build phases, and it is not possible to define them platform specific. The solution is to combine these libraries into an XCFramework, so the right architecture for a build target is used automatically. I've done this using <https://github.com/balthisar/openssl-xcframeworks/releases> ... actually I downloaded the binaries (although they could be built using the sources / scripts in the GitHub repo). I still had to add OpenSSL header files (and their header search path) as the dynamically generated Receigen file cannot include the frameworks headers. So my project runs on iOS simulator, iOS device and Mac Catalyst, and I "only" need to figure out the receipt validation thing... Greetings, Mattes

Looks - https://developer.apple.com/forums/thread/130930 like I'm not the only one... Any ideas?

Just joining to stay in the loop ... same issue here.

Reviving this thread as I'm currently struggling with state restoration in an app with multi-scene support. I'm assigning a stateRestorationActivityForScene in the SceneDelegate and checking for it when (re-) connecting a scene. View controllers have userActivity assigned to this activity and their updateUserActivityState method is called when the scene is disconnected. So far so good, and I think I've understood the concept of storing state-relevant information in the activity. What really makees me head spin is restoring the view hierarchy: Using a split view with two navigation stacks, master / detail view controller etc. make this quite complex, especially with support on iPad and iPhone... The legacy state restoration was taking care of the complete hierarchy and I could focus on view controller specific settings. Do I really have to mimic the whole storyboard setup, tracking and replaying all transitions etc.? I can hardly believe this step back, what did I miss? Massively confused, Mattes

BTDT - for an iOS app: I used the version information of the original purchase in the receipt to distinguish if the user has purchased the app before I made it freemium: Former customers get the full functionality enabled, others are working with a trial version and need to use IAP to unlock all functions. Works like a charm for years. Greetings, Mattes

Hey Jaime, thanks for mentioning the exit(173) ... I completely forgot it is required to request the receipt on macOS (although I'm using it in other apps). Will shortly give it a try and let you all know! At the moment I have classified the Mac Catalyst app "internal use only" as it still has some hick-ups and is not yet mature enough for production... Greetings, Mattes

Receiving the same error since yesterday w/o having touched the StoreKit / IAP part in my code...

@NateP: Wow, thank you so much for pointing me to the new article at electiclight ... I had abandoned my test using xattribs and was continuing using additional files ... with a lot of complications and limitations. Looks like I will revive the deserted git branch, once I can spend some time on the corresponding project! Thanks again, Mattes