Post

Replies

Boosts

Views

Activity

UIDocumentPickerViewController in Audiounit Extension unable to receive touches
Hello, I have an existing AUv3 instrument plugin. In the plug in, users can access files (audio files, song projects) via a UIDocumentPickerViewController In Logic Pro, (and some other hosts, but not all), the document picker is unable to receive touches, while a keyboard case is attached to the iPad. Removing the case (this is an Apple brand iPad case) allows the interactions to resume and allows me to pick files in the usual way. One of my users reports this non-responsive behavior occurs even after disconnecting their keyboard. I have fiddled with entitlements all day, and have determined that is not the issue, since the keyboard disconnection appears to fix it every time for me. Here is my, very boilerplate, presentation code : guard let type = UTType("com.my.type") else { return } let fileBrowser = UIDocumentPickerViewController(forOpeningContentTypes: [type]) fileBrowser.overrideUserInterfaceStyle = .dark fileBrowser.delegate = self fileBrowser.directoryURL = myFileFolderURL() self.present(fileBrowser, animated: true) {
2
0
448
2w
Designed for iPad / macOS asking users to re-purchase
I spoke with the developer support people on the phone and they referred me here with Case No. 102577694114 I have an existing iPad app. Today, I updated the app and made it available to users on macOS with the "Designed for iPad" setting. Unfortunately, my existing users are reporting that when locating the app on the Mac App Store, it shows the price of the app, when the app will should instead be free for them. They can click on the purchase button and download the app without having to pay, however, in the long run this will create a support headache for me and will lower sales. Please let me know if there is something I can do to fix this! For reference, the app is here : https://apps.apple.com/us/app/patterning-3-drum-machine/id1631913793
0
0
31
Apr ’25
CoreData Transformable Types and SecureCoding
I have a CoreData entity with a transformable property data that stores an NSDictionary. All of the classes inside the dictionary conform to NSSecureCoding I have been getting many instances of this warning : 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release In trying to clean up the warning and future-proof my app, but I am running into a lot of trouble. My understanding is that using NSKeyedUnarchiveFromData as the transformer in my data properties attribute should work, since the top level class is a dictionary and all of the contents conform to NSSecureCoding. However, my data dictionary is now coming back as NSConcreteMutableData so I cannot access the data in it. I have also tried creating a custom value transformer with additional allowedTopLevelClasses, but that hasn't helped, and again, the topLevel type is an NSDictionary, which should be allowed. Thank you for any guidance.
3
0
994
Feb ’24
Simulators not appearing for certain targets
I'm having a problem where the iOS simulators are not showing up for a certain target, but are showing up for others within the same workspace. I've checked that the deployment target is compatible with my simulator versions. I've tried re-installing Xcode, restarting the computer, cleaning the build folder, deleting DerivedData, and various other superstitious activities with no luck. I've also tried reverting to old versions of the project to see where things went wrong, but haven't been able to get them to appear that way either, though I know they were working previously. The one thing that changed recently that may be relevant is that I had to switch to using manual provisioning profiles for the target, since it uses the multicast networking entitlement. However, removing that entitlement and reverting to automatic signing doesn't fix the issue either. Any advice is much appreciated.
0
0
514
Dec ’20
XXX requires a provisioning profile
Because my app requires the Network Multicasting entitlement, I am required to change to use manual signing of my (already published) app. I've generated the profile and double checked that all of the entitlements are included in the profile. However, I'm getting this error when trying to run my app : XXX requires a provisioning profile with the Associated Domains, App Groups, Inter-App Audio, iCloud, and Push Notifications features. Select a provisioning profile in the Signing & Capabilities editor. I've regenerated the profile multiple times, restarted Xcode, and unchecked and checked all the entitlement boxes to try to reset them to no avail. Again, I am required to use manual signing, so please don't suggest that I check the "automatically manage signing" box. :) Thanks in advance.
2
0
17k
Nov ’20