title: ITMS-90338: Non-public API usage - The app references non-public selectors in [App]
body: <p>I am building a Xamarin.Forms app that is building properly and deploying to the Apple App Store but keeps getting rejected for the following reasons:</p>
  <blockquote>
  <p>ITMS-90338: Non-public API usage - The app references non-public
  selectors in [App].Mobile.iOS: accessibilityBrailleMapRenderRegion,
  accessibilityBrailleMapRenderer, accessibilityColumnRange,
  accessibilityRowRange, activePlayer, beginAuthorizationWithRequest:,
  cancelAuthorizationWithRequest:, errorForCHIPErrorCode:,
  errorToCHIPErrorCode:, playerId, serviceExtensionWillTerminate,
  session:didReceiveData:fromPlayer:,
  session:didReceiveMessage:withData:fromPlayer:,
  session:player:didChangeConnectionState:, session:player:didSaveData:,
  setAccessibilityBrailleMapRenderRegion:,
  setAccessibilityBrailleMapRenderer:. If method names in your source
  code match the private Apple APIs listed above, altering your method
  names will help prevent this app from being flagged in future
  submissions. In addition, note that one or more of the above APIs may
  be located in a static library that was included with your app.</p>
  </blockquote>
  <p>I coded the app on a PC in Visual Studio Community 2019 v16.9.1. And built and deployed the app via Appcenter.ms.</p>
  <p>Packages that I am using are:</p>
  <ul>
  <li>Microsoft.AppCenter.Analytics v4.5.0</li>
  <li>Microsoft.AppCenter.Crashes v4.5.0</li>
  <li>Xamarin.Essentials v1.7.1</li>
  <li>Xamarin.Forms v5.0.0.2337</li>
  </ul>
  <p>Target Framework: .NET Standard 2.0</p>
  <p>Information that I have confirmed from other sources:</p>
  <ul>
  <li>Build Configuration: Release</li>
  <li>Linker Behavior: Link Framework SDKs Only</li>
  <li>Additional mtouch arguments: --linkskip=[selectors]</li>
  <li>Additional mtouch arguments: --linkplatform</li>
  </ul>
  <p>I have found all of the non-public selectors in <code>xamarin/xamarin-macios</code> and <code>xamarin/apple-api-docs</code> but I have not been able to find out how to fix the errors.</p>
  <p>Thanks</p>
  <p>Edit: I was not able to fix the issue. Instead, I got a Mac VM and was able to publish the code that way.</p>