Recent searches
No recent searches
Support SDK HelpCenterUi, RequestUi operation error
Posted Apr 06, 2023
HelpCenterUi.buildHelpCenterOverviewUi, RequestUi.buildRequestList from iOS Support sdk
There is a problem.
It is being developed in SwiftUI and works normally during debugging, but
Infinite loading occurs on normal app launch.
call view
.fullScreenCover(isPresented: viewStore.binding(\.$isPresentingZendeskRequest)) {
ZendeskHelpCenter(supportType: .request)
}
implementation
struct ZendeskHelpCenter: UIViewControllerRepresentable {
enum SupportType {
case FAQs
case request
}
let supportType: SupportType
func makeUIViewController(context: Context) -> UIViewController {
var vc: UIViewController!
switch supportType {
case .faq: vc = HelpCenterUi.buildHelpCenterOverviewUi(withConfigs: [RequestUiConfiguration.default])
case .request: vc = RequestUi.buildRequestList(with: [RequestUiConfiguration.default])
}
return UINavigationController(rootViewController: vc)
}
func updateUIViewController(_ uiViewController: UIViewController, context: Context) {
}
}
The moment you call the screen, you will see the log as below.
Error log calling HelpCenterUi.buildHelpCenterOverviewUi
[Warning] Custom views and layout for UITableViewHeaderFooterView should be contained within the content view. Offending view: <ZDKHelpCenterOverviewHeaderView: 0x12990ada0; baseClass = UITableViewHeaderFooterView; frame = (0 0; 600 44); text = ''; autoresize = W+H; layer = <CALayer: 0x283d2a580>>
RequestUi.buildRequestList call error log
[TableView] Warning once only: UITableView was told to layout its visible cells and other contents without being in the view hierarchy (the table view or one of its superviews has not been added to a window). This may cause bugs by forcing views inside the table view to load and perform layout without accurate information (e.g. table view bounds, trait collection, layout margins, safe area insets, etc), and will also cause unnecessary performance overhead due to extra layout passes . Make a symbolic breakpoint at UITableViewAlertForLayoutOutsideViewHierarchy to catch this in the debugger and see what caused this to occur, so you can avoid this action altogether if possible, or defer it until the table view has been added to a window. Table view: <UITableView: 0x10b851000; frame = (0 22; 414 672); clipsToBounds = YES; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x283365da0>; backgroundColor = <UIDynamicSystemColor: 0x2828063c0; name = tableBackgroundColor>; layer = <CALayer: 0x283d283a0>; contentOffset: {0, 0}; contentSize: {414, 93}; adjustedContentInset: {0, 0, 0, 0}; dataSource: (null)>
0
10
10 comments
Sangyong Kim (Edgar)
Could you tell me the progress?
I've been waiting for the team's answer for a long time.
working environment
xcode version - 14.2
App Minimum Support Version - iOS 14.0
Zendesk Support SDK for iOS version - 7.0.0
0
Eric Nelson
Are you able to replicate this issue on version 6.0.0? Per our support guide are you able to replicate this behavior in a sample application that you can then provide to us?
Thanks!
0
Sangyong Kim (Edgar)
0
Sangyong Kim (Edgar)
Waiting time is so painful because of the late reply. Any other way to get a quick answer?
0
Eric Nelson
Apologies, for some reason we didn't receive notification of your previous message. In my last message I asked if you could replicate an issue in our sample application and then provide a copy to us. Are you able to do this?
0
Sangyong Kim (Edgar)
We already have an app "ovey" that works in the same environment as the sample project and it works normally.
It's just an issue that arises in the process of transferring "ovey" to another project in the "SwiftUI" environment.
If necessary, we will create and provide a sample application for the "SwiftUI" environment
Sends console logs that are generated when problems occur.
0
Sangyong Kim (Edgar)
I ask you again.
Need a sample application for the "SwiftUI" environment?
0
Eric Nelson
Your comments aren't creating notifications for us, I'm not sure why. Please @ mention me in your future posts so that I can get notified. Unfortunately if you're not able to replicate the issue in the sample project than it sounds like this is most likely something to do with a conflict with something else in your project. If you can create a sample app for the swift ui environment that'd be great.
0
Sangyong Kim (Edgar)
Hey Eric,
The cause has been found.There is a problem when the UINavigation Controller adopts the UIGestureRecognizerDelegate protocol within the project and then expands to override the viewDidAppear. Have you found any problems related to this?
0
Greg Katechis
Hi Sangyong! I checked internally and have not seen any reports of this. If you have the sample app with only this relevant code causing the issue, please send that to me and I'll review it and pass it along to the dev team if it looks like a bug on our end!
0