Support SDK HelpCenterUi, RequestUi operation error

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)>