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.
Created attachment 17362 [details]
When trying to sign and distribute our app this error is popped out.
We have a Today Extension, and didn't do any changes to it.
As for now we can't submit our build to appstore
We would need a bit more information in order to precess this bug properly.
- The full and verbose build logs. (To change the verbosity go to Xamarin Studio > Build > Log Verbosity and set it to Diagnostic).
- Your product versions. (About information found in Xamarin Studio > About Xamarin Studio Show Details).
Optional (but super helpful)
- Possibly a test case or the full app in order to reproduce the issue.
Created attachment 17374 [details]
Example project, logs and info
Empty project with widget
diagnostic build log
and Studio info
I can build this project successfully. Errors occurs when try to Sign and Distribute archive
Created attachment 17375 [details]
forgot to add studio info
Icing Jeff who has more knowledge about this area.
This should already be fixed in the Xamarin.iOS 10.0 builds. Or is that what you used? Just want to make sure this wasn't a 9.99 preview build.
We have not received the requested information. If you are still
experiencing this issue please provide all the requested information
and re-open the bug report. Thanks!