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 for Bug 58716 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 24138 [details]
strange widget behavior
While running my iOS widget I discovered that it sometimes shows a strange background screen with Cancel/Post button and a textfield. I attached a screenshot, my widget should be empty but contains the Cancel/Post screen.
I can reproduce this behavior on my iPhone (6 with iOS 10.3) by executing the following steps:
- Go to widget screen
- Then press the Search area on the top
- Then press cancel
- Now the widget shows up with this Cancel/Post area as a background.
In the simulator I can sometimes reproduce it (1 out of 10 times) but still I will always see it flashing in the simulator and then disappearing quickly after doing the steps above.
Is this screen something build in in the Xamarin platform ? How to get rid of it ?
Microsoft Visual Studio Enterprise 2017 (2)
Version 15.2 (26430.16) Release
Microsoft .NET Framework
Installed Version: Enterprise
Visual C# 2017 00369-90250-47883-AA538
Microsoft Visual C# 2017
Mono Debugging for Visual Studio Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
Xamarin 126.96.36.1996 (fec6f88)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 188.8.131.52 (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.10.0.37 (ad35de4)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Could you share the project or a sample project that can reproduce this issue? If you can share the project and it's private, please attach and make sure to mark it private (Xamarin Team only).
Created attachment 24163 [details]
VS solution to reproduce bug
Very simple solution to reproduce behaviour
Hereby a link to a small movie of me reproducing it on my mac simulator after a few tries:
Any news on this ? Are you able to reproduce ?
I just upgrade to VS 15.3 and I still have the problem.
I was not able to reproduce with the sample you provided. Could you provide detailed steps on what I should do with the solution to see this issue?
OK, please do the following:
1) Run the solution on iPhone 6 simulator (not s) or iPhone 6 real device.
2) Goto today screen
3) Add solution widget as first widget on today screen
4) Now on today screen click in search area at top
5) Now press cancel (returning to today screen), sometimes you see the widget flickering with the cancel/post buttons and then recovering, sometimes the cancel/post buttons stay on the widget.
6) repeat steps 4-5 a few times
On real device it almost always fails on simulator 1 of 5/10 tries it fails.
Please let me know if you can reproduce ?
Any news on reproducing this ? Because this is still a big showstopper for our app.
I was able to reproduce this with the steps provided in Comment 6.
## Regression Status
Does not appear to be a regression.
Hi! What's the status of this bug please? I experience the same issue using iOS 11.2.6 and the current stable versions of Xamarin Forms and Visual Studio 2017. Is there any workaround to prevent this behaviour?
Just checked the default code that is generated when adding an iOS Today Extension project.
Problem is that TodayViewController class inherits Social.SLComposeServiceViewController. Replacing that with a UIViewController and doing a complete solution Clean + Rebuild fixed the problem.