I was able to build an XCFramework of OpenSSL v1.1.1h based on
https://github.com/adib/openssl-xcframeworks/tree/develop/BigSur
for all platforms with fat binaries for all architectures, including:
macOS (x8664, arm64)
iOS Mac Catalyst (x8664, arm64)
iOS (armv7, arm64)
iOS simulator (x8664, arm64)
tvOS (arm64)
tvOS simulator (x8664)
watchOS (arm64_32, armv7k)
I'm using it with a macOS deployment target 10.11...
Cheers, Mattes
Post
Replies
Boosts
Views
Activity
"+1", unchecking debug symbols upload helps. Apple, your QA sucks...
Just to finally close this thread: Kudos to @NateP ... The last days I looked up my old git branch and integrated additional infos by extended file attributes using the required flag XATTRFLAGSYNCABLE (#S), and iCloud synching is working like a charm!
Thanks again, Mattes
You could use a workflow with two actions: The first running your Audi shortcut and a second with Siri reading some static text. There are iOS 14 default actions for both purposes.
Mattes
I solved this issue by adding Siri intents in the app delegate after launching the app. Works nicely with iOS < 14: The user can define a workflow with one shortcut, e.g. "Next Lesson", and Siri reads the result from my intent definition (voice only dialog response).
With iOS 14 Siri isn't reading responses anymore, so the shortcut is run, displaying the result, but without any audio feedback. Unfortunately this was the main purpose of my intents, asking Siri just for some information to be read loud.
Is this a general design decision in iOS? What do I need to implement to make Siri (again) reading intent results? Currently I can only think of a bypass, putting the result text into the clipboard and adding a second shortcut reading the clipboard (with is an iOS-provided one). Any thoughts?
Mattes
@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
Receiving the same error since yesterday w/o having touched the StoreKit / IAP part in my code...
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
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
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
Just joining to stay in the loop ... same issue here.
Looks - https://developer.apple.com/forums/thread/130930 like I'm not the only one... Any ideas?
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
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
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