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 19767 [details]
Image showing the hidden UI elements
Tested Device: Galaxy S4 GT-I9505 running Kitkat 4.4.2
When using FormsAppCompatActivity, on the device mentioned above, the interface of the app seems to be overlayed above standard Android OS UI elements like the keyboard and notification slider, as well as the contextual popups on text fields. You can still interact with these Android elements, but they aren't visible.
I'm attaching a screenshot demonstrating this. In this image, the notification panel has been slid down but doesn't render the parts of it that are supposed to appear above the application. You can still interact with the buttons that would have been there, but you can't actually see them.
I've not been able to replicate this with an emulator or on another device, so it might be specific to this single device.
The interface looks very simple based on the screenshot, although a reproduction would definitely be useful to confirm the fact. We'll need to see if it is in fact specific to that device (or just the S4 in general).
For upkeep, because we have not received a reproduction or more information, we are closing this for the time being as not reproducible (considering "other devices" were mentioned, it hasn't been brought to our attention by anyone else on this ticket).
That said, if you're still experiencing the problem on the latest prerelease or nightly build, please reopen this with a reproduction project and a list of any other devices you're aware of that are still exhibiting this behavior, as there's always a chance that this is still a problem, but we need more to work with.