I have an app that relies heavily on AppIntents and Shortcuts and it seems like the latest iOS update broke those but I can't quite figure out what's the issue.
The is that no matter what parameter I pick, when running the shortcut it always uses the defaultResult()
Here's an example AppEntity:
struct IntentBrokerAppEntity: AppEntity {
static var typeDisplayRepresentation = TypeDisplayRepresentation(name: "Intent Broker")
@Property(title: "Name")
var name: String?
@Property(title: "Ip")
var ip: String?
@Property(title: "Port")
var port: String?
@Property(title: "Username")
var username: String?
@Property(title: "Password")
var password: String?
@Property(title: "Tls")
var tls: Bool?
struct IntentBrokerAppEntityQuery: EntityQuery {
func entities(for identifiers: [IntentBrokerAppEntity.ID]) async throws -> [IntentBrokerAppEntity] {
return try await suggestedEntities().filter { identifiers.contains($0.id) }
}
func suggestedEntities() async throws -> [IntentBrokerAppEntity] {
let context = PersistenceController.shared.viewContext
let brokerService = BrokerService(context: context)
return brokerService.getFavorites().map { IntentBrokerAppEntity(broker: $0) }
}
func defaultResult() async -> IntentBrokerAppEntity? {
try? await suggestedEntities().first
}
}
static var defaultQuery = IntentBrokerAppEntityQuery()
var id: String // if your identifier is not a String, conform the entity to EntityIdentifierConvertible.
var displayString: String
var displayRepresentation: DisplayRepresentation {
DisplayRepresentation(title: "\(displayString)")
}
...
This used to work perfectly fine before 17.2, but now instead of choosing the entity the user picked it always falls back to defaultEntity().
In the console I get this warning
Failed to build EntityIdentifier. IntentBrokerAppEntity is not a registered AppEntity identifier
But I'm not sure if that's related.
Does anyone have any ideas on what's going on here? Input much appreciated!
Lucakaufmann
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I'm currently implementing interactive widgets for my app. The widget calls an intent that is also used by Shortcuts and this interaction seems to work with no issues. Now I'm looking to get that running in Standby and on the lockscreen with the phone locked. I figured static var authenticationPolicy: IntentAuthenticationPolicy = .alwaysAllowed would do the trick, but the phone still asks to be unlocked before running the intent. Is there any way to get this working? I've seen some examples for widgets that can be run with the phone locked, but they all seem to be audio intents that play some audio.
Example of the intent code: