Bug 58716 - iOS Widget shows strange background in some cases with cancel post screen ?
Summary: iOS Widget shows strange background in some cases with cancel post screen ?
Alias: None
Product: iOS
Classification: Xamarin
Component: General (show other bugs)
Version: XI 10.14 (d15-4)
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-08-11 10:07 UTC by jeroen.bernsen
Modified: 2017-08-28 14:46 UTC (History)
2 users (show)

See Also:
Tags: ac
Is this bug a regression?: No
Last known good build:

strange widget behavior (157.37 KB, image/jpeg)
2017-08-11 10:07 UTC, jeroen.bernsen
VS solution to reproduce bug (27.65 KB, application/x-zip-compressed)
2017-08-14 10:02 UTC, jeroen.bernsen

Description jeroen.bernsen 2017-08-11 10:07:10 UTC
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 ?

My environment:

Microsoft Visual Studio Enterprise 2017  (2)
Version 15.2 (26430.16) Release
Microsoft .NET Framework
Version 4.7.02046

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 (fec6f88)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK (ad35de4)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Comment 1 John Miller [MSFT] 2017-08-11 12:41:33 UTC
Hi Jeroen,

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

Comment 2 jeroen.bernsen 2017-08-14 10:02:37 UTC
Created attachment 24163 [details]
VS solution to reproduce bug

Very simple solution to reproduce behaviour
Comment 3 jeroen.bernsen 2017-08-14 10:14:29 UTC
Hereby a link to a small movie of me reproducing it on my mac simulator after a few tries:
Comment 4 jeroen.bernsen 2017-08-18 07:11:39 UTC
Any news on this ? Are you able to reproduce ? 

I just upgrade to VS 15.3 and I still have the problem.
Comment 5 John Miller [MSFT] 2017-08-18 20:46:34 UTC
Hi Jeroen,

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?

Comment 6 jeroen.bernsen 2017-08-19 14:44:01 UTC
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 ?
Comment 7 jeroen.bernsen 2017-08-28 07:08:23 UTC
Any news on reproducing this ? Because this is still a big showstopper for our app.
Comment 8 John Miller [MSFT] 2017-08-28 14:46:02 UTC
I was able to reproduce this with the steps provided in Comment 6. 

## Regression Status

Does not appear to be a regression. 


Note You need to log in before you can comment on or make changes to this bug.