Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We have been using xamarin.forms to build our new app. However the last 2-3 times we have been trying to submit the app apple gives us an error regarding use of invalid API. However this should not be the case, as we only use xamarin.forms, together with the following components.
Azure mobile services
Here is the email that we receive each time we try to submit to the appstore.
We have discovered one or more issues with your recent delivery for "Hungry - Bestil Takeaway". To process your delivery, the following issues must be corrected:
Non-public API usage:
The app references non-public selectors in HungryAppiOS: _addRecorder:, _playbackEvents:atPlaybackRate:messageWhenDone:withSelector:, _removeRecorder:, applicationWillTerminate, terminateWithSuccess
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. If so, they must be removed.
If you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's nine-digit Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged, to email@example.com. For further information, visit the Technical Support Information page.
Once these issues have been corrected, you can then redeliver the corrected binary.
The App Store team
quick workaround, remove the reference to Xamarin.TestCloud.Agent
Please make sure that your code does not call into Calabash from your release build (or whatever other configuration you use to build for the App Store).
For example, set the ENABLE_TEST_CLOUD define only in your debug configuration, and conditionally include the initialization code:
If you still have the problem after making this change, could you please attach your build log so we can look into it?