Request permission for each target:request form
I received approval emails about 3 weeks later.
A website doesn’t seem to be mandatory; no one visited the URL I provided.
Post
Replies
Boosts
Views
Activity
Find a solution for iOS 17+.
Reduce Data Struct into a one-dimensional Array.
/**
✅
Make sure LazyVStack is always visible.
*/
ScrollView {
LazyVStack {
ForEach(data) { item in
switch item.viewStyle { // dynamic config view by data
case 1:
DynamicHeightView1()
case 2:
DynamicHeightView2()
default:
DynamicHeightView()
}
}
}
}
/**
❌
The contents inside a LazyVStack may disappear from view when the user is scrolling or when the keyboard changes the focus state.
*/
ScrollView {
ForEach(data) { section in
LazyVStack {
ForEach(section) { row in
DynamicHeightView()
}
}
}
}
// ❌ or
ScrollView {
View()
LazyVStack {
ForEach(section) { row in
DynamicHeightView()
}
}
LazyVStack {
ForEach(section) { row in
DynamicHeightView()
}
}
View()
}
I have a familiar issue and no workaround. :-(
Scenario:
iOS17 + LazyVStack + ScrollView, ScrollView flitters, and Views inside LazyVStack disappear when TextField changes FocusState.
Same issue and my solution.
Scene:
iOS17 + ScrollView + LazyVStack + Textfields.(iOS16 working as expected)
Log:
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID.
Solution:
Replace LazyVStack with VStack solved my problem.
Meet same issue and find a solution:
Don't use initializeCloudKitSchema(),
instead of creating an entity, then the system will auto generate schema, without creating extra field( CD_***_ckasset).
Example:
You use 「PublicEntity」 in 「Public」Configuration;
Create a 「PublicEntity」
set value for every field
use context.save()
then schema 「CD_PublicEntity」 will auto generate.
I got the same message twice.
My account is new too.
Fisrt time, after 3 days, the Apple Developer Contact says that I violate the 「in-app-purchase」rule.
I didn't write any in-app-purchase code, but I did import an third library(SwiftyStoreKit) before, uninstalled before submit.
Some auto generated pay-related string left in my project cause this problem.
I removed the file and re-submit again, now I got this problem again, some 「other-other」...
It's really frustrating...