I'm trying to delete many records with one CKModifyRecordsOperation and getting this error:
<CKError 0x600000dbe4f0: "Limit Exceeded" (27/1020); "Your request contains 552 items which is more than the maximum number of items in a single request (400)">
This obviously means, that Modify Operation has record limit of 400 which is equal to CKQueryOperation.maximumResults. The good solution here would be to chunk the array of records into subarrays with length less than 400 and add multiple delete operations to the database.
The only problem is that the limit for CKModifyRecordsOperation is neither documented nor provided with a constant, so it's basically a magic number.
In hope that my prayers would be heard I want to ask to add maximumResults constant to CKModifyRecordsOperation.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Is there any tool to automatically migrate data & data structure from Google Firebase to CloudKit?
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
CloudKit
CloudKit Dashboard
CloudKit Console
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.
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.
There is a such method in Bundle:
func classNamed(_ className: String) -> AnyClass?
The description says it loads the Class object for className. It's, obviously, an Objective-C stuff. I started from Objective-C but didn't used it, preferring NSClassFromString.
Now I suddenly tested it in various applications. I was surprised that it doesn't work in iOS apps neither in Playground:
import Foundation
class TalkingFruit {
func greet() {
print("Hello, playground")
}
}
@objc class LagacyFruit: NSObject {
}
print(Bundle.main.classNamed("TalkingFruit") ?? "no class")
// no class
print(Bundle.main.classNamed("LegacyFruit") ?? "no class")
// no class
print(Bundle.main.classNamed("NSObject") ?? "no class either")
// no class either
And now I have a question: Does it even work? And how it's supposed to be used? Working use case example would be great.
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.