Posts

Post not yet marked as solved
0 Replies
203 Views
This is a major issue. My iPad app is crashing in the App Store. In order to fix it, I found a post that recommended making the framework optional. I did so. Now I can't compile on simulator and besides, it did not fix the iPad App Store crash. ld: framework 'JournalingSuggestions' not found
Posted Last updated
.
Post not yet marked as solved
2 Replies
420 Views
https://developer.apple.com/forums/thread/731732 Possibly linked to the above issue The app compiles just fine, but SwiftUI Previews cannot build if there any any packages that lack support for visionOS I made sure that filters were enabled so that the package is only linked to iOS In a project that literally NEVER imports or uses an iOS only package, it fails completely == PREVIEW UPDATE ERROR: SchemeBuildError: Failed to build the scheme ”VisionHelloWorld” 'tracks(withMediaType:)' is unavailable in visionOS Compile LightCompressor.swift (arm64): /Users/bryananderson/Library/Developer/Xcode/DerivedData/VisionHelloWorld-dviwzruidaouzeeafminiifghzfe/SourcePackages/checkouts/LightCompressor_iOS/Sources/LightCompressor/LightCompressor.swift:123:47: error: 'tracks(withMediaType:)' is unavailable in visionOS guard let videoTrack = videoAsset.tracks(withMediaType: AVMediaType.video).first else { ^~~~~~ AVFoundation.AVAsset:17:15: note: 'tracks(withMediaType:)' has been explicitly marked unavailable here open func tracks(withMediaType mediaType: AVMediaType) -> [AVAssetTrack]
Posted Last updated
.
Post not yet marked as solved
3 Replies
1k Views
Unsupported Xcode or SDK Version. Your app was built with a version of Xcode or SDK that is not yet supported for upload to App Store Connect. For more information about supported versions of Xcode and SDK for Testflight or App Store submissions, view the App Store Connect What's New page (https://developer.apple.com/app-store-connect/whats-new/). (ID: 0e108b7e-0cc1-413e-99ad-8b081656a52c) How lovely.
Posted Last updated
.
Post not yet marked as solved
1 Replies
1.2k Views
Okay so I have a CloudKit backed CoreData model. I've been building in development for several months. I have a lot of data stored in the app on the development CloudKit. Then I installed the TestFlight version on that device. It is now missing a lot of data that used to be on that device. And it won't sync with my other apps. I assume this is because of the production vs development thing.. But even when I install the app via Xcode, syncing is broken. Its not updating and I'm just getting this error: I'm really worried about this and am totally reliant on CloudKit working. But now such simple thing broke syncing and I'm not sure how to get it back up and running CoreData: debug: CoreData+CloudKit: -[PFCloudKitSerializer applyUpdatedRecords:deletedRecordIDs:toStore:inManagedObjectContext:onlyUpdatingAttributes:andRelationships:madeChanges:error:]_block_invoke(1021): Failed to find matching objectIDs for <CKRecordID: 0x2823541c0; recordName=BFE5B0E0-E4BC-4151-B64F-771AF271DE6C, zoneID=com.apple.coredata.cloudkit.zone:defaultOwner> / <CKRecordID: 0x2823542c0; recordName=B342EDDF-8F2A-4496-B5AB-BEF29AF4018C, zoneID=com.apple.coredata.cloudkit.zone:defaultOwner> in pending relationship: 0x9eebd60aabec84c2 x-coredata://1DE90E1A-C7CF-4963-B10F-60142BFFCFD7/NSCKImportPendingRelationship/p11489
Posted Last updated
.
Post not yet marked as solved
0 Replies
797 Views
I try and add a new package. After that, it asks for my personal access token. Which I correctly enter. And then it repeats. I don't know how to get it to stop. I've noticed it has gone away. But each time I go to add a package I can almost guarantee I'll spend an hour trying to add
Posted Last updated
.
Post not yet marked as solved
2 Replies
729 Views
Seems like they might have missed this. . . But you can’t put widgets on an ipad home screen. No functionality has been added to widgets on iPad, except their new look. You can’t drag widgets in with apps the way you would OBVIOUSLY want or expect to be able to do now that iOS can. This is a prime example of why I was actually nervous about iPad and iOS being separated. They’ll just totally develop features for one devices and not do it for the other.
Posted Last updated
.