Post

Replies

Boosts

Views

Activity

Reply to usernotifications.filtering entitlement prevents a contact with an image from being added/updated
Did some more investigation, and the issue is down to the fact that UIScreen.main.bounds is (0.0,0.0,0.0,0.0) if the com.apple.developer.usernotifications.filtering entitlement is present. Without the entitlement is has values for width and height. This was causing an image with 0 dimensions attemting to be added to the contact. So the question is why are the bounds empty if the entitlement is present?
Topic: Code Signing SubTopic: Entitlements Tags:
Sep ’22
Reply to OSLogStore can't access an app's extensions?
@MobileTen I mean an application extension, such as an action extension, notification content extension, notification service extension etc. I've rephrased the question to hopefully make it more understandable: Is there a way of using Logger/OSLogStore such that logging performed within an extension can later be retrieved by the application? For example suppose an app is logging like this: let logger = Logger(subsystem: "com.mysubsystem.log", category: "app") logger.debug("app stuff") and suppose an extension (such as a notification service extension for example) logs like this: let logger = Logger(subsystem: "com.mysubsystem.log", category: "ext") logger.debug("ext stuff") Then next time the app runs, if it attempts to retrieves the log with code such as: let logStore = try! OSLogStore(scope: .currentProcessIdentifier) let oneHourAgo = logStore.position(date: Date().addingTimeInterval(-3600)) let allEntries = try! logStore.getEntries(at: oneHourAgo) for entry in allEntries { look at the content of the entry Then within the for loop, there's lots and lots of stuff retrieved, including "app stuff", but there is no "ext stuff". Is there anyway the application can retrospectively retrieve logging performed within the extension?
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’22
Reply to Inconsistent CallDirectoryExtension behavior on iOS 14.5
Its not your phone, its iOS 14.5 that is the problem. In addition to getting the call extension status taking a very long time and then failing after app launch, attempting to update the extension does the same. Also try terminating the iPhone Settings app, then launching and going to the Call Blocking & Identification section - your call extension won't be there, it takes 30 seconds before it appears.
Topic: Programming Languages SubTopic: Swift Tags:
May ’21