Post not yet marked as solved
I'd love to see a pie chart as well, which can be used in Lock Screen circular widget. However, this doesn't seem possible just yet.
You need to first use Xcode 14 beta, then embed the Swift Charts (which is SwiftUI view) to your code using one of the bridging tools below
https://developer.apple.com/documentation/swiftui/swiftui-views-displayed-by-other-ui-frameworks
Post not yet marked as solved
Thanks for confirmation.
So basically I have to subclass UIView and implements UITextInput to start with?
On Mac, this may mean subclassing NSView and implements NSTextInput / NSTextInputClient?
Post not yet marked as solved
Same with 2020 iPad Pro 12.9"
Post not yet marked as solved
I tested again, the issue is about multiple targets instead of frameworks (although I wanted to ask something about internal frameworks too)
I am adopting Mac Catalyst in our project. For reasons to include different frameworks between iOS and macOS apps, I setup one target for each. So this is where the issue starts...
1) Main app (iOS) exports to {Project}/en.lproj/Common.strings
2) Mac Catalyst exports to en.lproj/Common.strings
I confirmed by removing the Mac Catalyst target to export.
Post not yet marked as solved
Hi @Hiren Gujarati,
Did you figure out a solution to ITMS-90736 error?
I'm recently adding iOS 14 configurable widget with its WidgetIntent. Since the new API requires iOS 14, I must set the new target for WidgetIntent to deployment target 14.0. However, it's complaining when I submit to App Store with the following error:
ERROR ITMS-90736: "Invalid Intent Extension. The MinimumOSVersion key in the 'MyApp.app/PlugIns/WidgetIntents.appex' Info.plist file can't be greater than '11.4'."
My main app is still supporting 11.4
Post not yet marked as solved
In my existing project, I tried to remove the target-independent strings files and share the same one among targets. However, by exporting localisation it still results in two files based on the two targets?
Is there a guideline or tutorial somewhere to show the proper setup?
I filed rdar://40009122 as well.I'm surprised that EventKit didn't receive any update for years. Guess the force unwrap is a result of auto generated code in order to comply swift syntax.
Post not yet marked as solved
I created an empty project, with just scheduling notifications (nothing on setting badge). getDeliveredNotifications just keeps returning empty array. This started to happen since iOS 11.2
Thanks for the information. It works great when I intend to show FaceID for authentication to use the app.In applying the strategy to auto prompt Face ID for authentication when bringing the app from background (or within a viewDidAppear lifecycle), however, the evaulatePolicy method call gives a failure result with error as below.Optional(Error Domain=com.apple.LocalAuthentication Code=-10 "Lost connection to coreauthd." UserInfo={NSLocalizedDescription=Lost connection to coreauthd.})Is it expected?
Post not yet marked as solved
Submitted successfully since 10 Oct, no change to the setup at all since last time failure on 29 Sep.Here is my setup:High Sierra 10.13 PublicXcode 9 PublicCocoaPods 1.0.1
Post not yet marked as solved
I faced the same issue. This is how I fixed this.Migrate to Use Asset Catalog, which moved Primary Icons to Asset Catalog and kept alternate icons in Info.plistAfter that, I can submit to TestFlight using Application Loader.(For some other reasons, I cannot submit via Xcode for a long time)
Post not yet marked as solved
I'm not building ARKit app, but take advantage of SiriKit integration in iOS 11 (Task Lists and Notes)This is my setup for a successful submission.Xcode 9 Beta 6 (9M214v)Deployment Target
Main App: 10.0Intent Extensions: 11.0Use Asset CatalogInclude Alternate icons in Info.plist (Info.plist alone does not work)Archive (I use fastlane)Go to Organizer > Export > App Store
Keep Bitcode and Crash DataUse Automatic ProvisioningCheck each app and extension has unique provisioning profile selected (non-wildcard)Submit with Application Loader 3.7 (come with Xcode 9)Hope this helps someone.
