What is the process named TestFlightServiceExtension on my iPhone 6S, iOS 14.4? Is it safe?

What is the process named TestFlightServiceExtension on my iPhone 6S, iOS 14.4? It also can be found in one (1) crash report over the internet. Is this process safe?

What is the process named "announced" on iPhone 6S, iOS 14.4? Is it safe? Found zero information about it.

Hi! I'm making a workout app for swimmers. Our QA is confused with the swimmingStrokeCount output. He's a sportsmen and when crawl he used to count 2 strokes per cycle, one for each arm. The output is incorrect and looking at numbers we suspect that HKWorkout counts only one arm. Documentation doesn't say anything about it.

I would like to test handle() in my ExtensionDelegate to make sure that WKWatchConnectivityRefreshBackgroundTasks are completed successfully. Is there any way to simulate background task? On real device or on simulator.

Is there any tool to automatically migrate data & data structure from Google Firebase to CloudKit?

Hi! I wanted to test my app with Xcode and see how it handles network errors. So, in Devices and Simulators I activated Network Link Condition - 100% packet loss. Then I run the app and see the popup saying that it's unable to verify app for obvious reasons: Unable to Verify App An Internet connection is required to verify trust of the developer "Apple Development: Vladimir Kelin (<#teamid#>)". This app will not be available until verified. How do I run the app with network condition, then?

Hello, fellow developers! How would you approach .watchface file to extract it's metadata? I need to know in which version of the app the face was created, to prompt the user to update the app if necessary. Looking at binary I suppose that a .watchface file consists of a PNG previews and JSON metadata and it all packed in one file somehow. Probably archived with gzip.

It's not a question, I just want to share my experience of resolving a bug. We where adding a new product to the app and couldn't get why it's not loading. StoreKit 2 simply did not return the product, so we switched to StoreKit 1 to get invalidProductIdentifiers from the response. The product was there of course. So many time was spend... We checked App Store configuration, everything was approved. Checked id, localization, multiple devices. Everyone start to get mad, we filled issues for RevenueCat and Apple. Then we uploaded a TF build (because product wasn't loading when running from Xcode). And, suddenly the product did appear there! I understood that it can be connected to StoreKit Configuration, since it works only in debugger mode (Debug or Release), but not in TF. But there was no any .storekit files in the project folder. I search it many times - no success. And finally the bug was resolved when I checked Run Scheme. As you can see on the screenshot, it has red value under StoreKit Configuration. That means there where a file before, but than it was removed. So I changed it to None and the product started to work in debug. Great! I hope this post helps, don't fall to the same error as me! Related article: Setting up StoreKit Testing in Xcode

I'm curious, why DynamicOptionsProvider is available on watchOS? Is there any way to present options to the user? For example in Emoji Rangers project: struct EmojiRangerSelection: AppIntent, WidgetConfigurationIntent { static let intentClassName = "EmojiRangerSelectionIntent" static var title: LocalizedStringResource = "Emoji Ranger Selection" static var description = IntentDescription("Select Hero") @Parameter(title: "Selected Hero", default: EmojiRanger.cake, optionsProvider: EmojiRangerOptionsProvider()) var hero: EmojiRanger? struct EmojiRangerOptionsProvider: DynamicOptionsProvider { func results() async throws -> [EmojiRanger] { EmojiRanger.allHeros } } func perform() async throws -> some IntentResult { return .result() } } On watchOS we usually use recommendations() to give the user predefined choice of configured widgets. Meanwhile in AppIntentProvider recommendations are empty: struct AppIntentProvider: AppIntentTimelineProvider { ... func recommendations() -> [AppIntentRecommendation<EmojiRangerSelection>] { [] } } Does it imply that there's a way to use DynamicOptionsProvider on watchOS somehow? BTW, WidgetConfiguration.promptsForUserConfiguration() is one of the methods that are not available on watchOS. And also, the Emoji Ranger project doesn't show widgets (complications) on watchOS out of the box.

Recently, our team bumped into a crash that we cannot resolve. We looked for help everywhere. I asked people here on forums, team asked about 10 fellow developers and the question on SO was created. Nobody knows the reason for the crash, nobody can find a workaround. So, as the last resort, I called for Apple Technical Support (aka code-level support). I assumed that people there understand how things work under the hood. Considering that this service is limited (2 TSI per year, otherwise paid), I expected the quality to be high. In fact, it didn't help us to resolve the problem, and I was disappointed how irrelevant the provided support could be. TLDR: The dev didn't even open the test project! I described the memory crash with WidgetKit-based complication. I spend my time capturing video, finding watch logs on my iPhone and creating a sample project. I attached console output, stack traces and a couple of screenshots. I even provided a .watchface file, so they can reproduce the configuration. This together took about 6-8 hours of work. I explained what happens in detail: steps to reproduce, what I've tried. I asked the support to recommend me way to present only the specified complications. Then I submitted the issue and started to wait. It took them 1 week to responsd. I pointed my sight on the email with excitement, expecting to finally get the resolution. But what I found there was disappointing. The software engineer, Rico, quoted only a couple of sentences from my list. His letter contained only 4 lines of text (not including greetings and cheers). In the first line he recommended to use preprocessor macro to enable only necessary complications, which is nonsense. Of course we need to change complications dynamically, when the user selects them. I two next lines he recommends to use if statement in WidgetBundle to dynamically unlock the complications. I already knew that it isn't possible. Because, quote: "if statements in a WidgetBundleBuilder can only be used with #available clauses" @available(*, unavailable, message: "if statements in a WidgetBundleBuilder can only be used with #available clauses") public static func buildOptional<W>(_ widget: W?) where W : Widget The last line cancelled everything before, Rico said that this can't be done at runtime. Probably, he added that after reading the documentation, but forgot to edit his previous statements. I didn't give up completely. I decided to skip the design discussions and get the info that Rico could probably have, due to his access to the software. Why the extension using so much memory? I also asked him, if he was able to build the project and reproduce the bug. Another week passed. I'm sending a follow-up message. That worked, after another 3 days I got the response: Finally some useful information! Timeline and views are being archived to disk (all simultaneously), that's why the memory usage is so high. Basically, a widget design issue. But anyway, we have what we have. Then next line, he has written this: "Complications are deprecated". What? But wait, he thinks that we use ClockKit, and recommends migrating to WidgetKit. So Rico completely forgot that we discussed WidgetBundle and SwiftUI before 🤡 He honestly tells me that he didn't open the project. Why? Because "Complications are unlikely to be supported", he says. So he "forgot" WidgetKit on intention, this gave him an excuse to ignore the sample project. My time was invested for nothing! I believe there's no need in further conversation with Rico. I will provide the detailed feedback to the Apple. And I'm posting it publicly to make sure that Rico gets the attention he deserves. If you want to know more technical details about the issue, you can check the following links: https://stackoverflow.com/q/77855303/1746142 https://developer.apple.com/forums/thread/744726

Trying to get the relevant app (it exists and published) by this endpoint: https://api.appstoreconnect.apple.com/v1/bundleIds/{id}/app Receiving error 404: "errors" : [ { "id" : "ec7b1469-fe54-4ad5-9f2b-f665c31a6358", "status" : "404", "code" : "PATH_ERROR_REALTIONSHIP", "title" : "The URL path is not valid", "detail" : "The relationship 'app' does not exist on resource 'bundleIds'" } ] Doing everything according to documentation. Tried to pass both Bundle ID id and Bundle ID itself. What could be the problem?

Is it ok to have latency about 4 sec? The amount of downloaded data is less than 1 MB. Maybe I need to setup an index for every field requested?

We have a watchOS app that provides many configurable widgets. Those widgets are configured and installed with help of AppIntent: public struct RectComplAppIntent: AppIntent, WidgetConfigurationIntent, CustomIntentMigratedAppIntent { @Parameter(title: "Style") var style: String? .... } However when I print WidgetInfos with getCurrentConfigurations(), I sometimes got nil for configuration. At the same time widgets are not loaded. Exact steps: User installs the pre-cofnigured .watchface. Complications are not loaded since configuration is missing. I print getCurrentConfigurations() and get entries like this: WidgetInfo: - configuration: nil - widgetConfigurationIntent: nil - family: accessoryRectangular - kind: Rectangle Then user force-touches a face and opens editing mode. Returns to watch app, prints infos: WidgetInfo: - configuration: <INIntent: 0x780d290> { style = vol1Logo; } - widgetConfigurationIntent: nil - family: accessoryRectangular - kind: Rectangle – Suddenly intent appears with the correct style and complications start to show up. How do you think, why it happens? Why after .watchface install all the WidgetInfo has nil intent (configuration)? What helps them to load later? You can try this face yourself: https://cdn.watchfaces.co/watchfaces/glance-minimalist.watchface

Hello! I want to clarify the usage scope of auto-renewable subscriptions. The guideline telling us:"If you offer an auto-renewing subscription, you must provide ongoing value to the customer. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multi-player support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support."So, it's emphasises, that there could be other cases. I want to be sure will my app be approved by the review, or not.My application is an offline business utility. It doesn't provide any cloud services or updating media content. The only reason to use subscriptions is that the app will be consistently updated according to: iOS updates, user suggestions, new features and bug fixes. So it's probably one of "apps that offer consistent, substantive updates", isn't it?What should I write to users and to Apple so that the app will be able to pass review?There are many reasons why I like auto-renewable subscription model, besides 85% revenue. It sufficiently lowers barriers for a user, thanks to the free trial and ability to cancel if the first experience was not satisfying. Moreover, it provides great feedback: looking at subscribed users count I'm able to decide, should I spend more time supporting this application, or should I pay attention to another, more successful aps. I also can release the app earlier, and gradually improve it constantly listening to user feedback. It's better than make a technically ideal paid app that nobody will buy. And I think it just more fair, because todays app are not "fire and forget" products and require continuous maintenance and updates.