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 16239 [details]
If I put something in the Entry, it will show up, but after I lost focus I can't see the Text which I put it in. I think maybe there is some color problem.
I upload some picture for you check.
Still can't believe this kind of simple coder Bug not fixed after 5 month.
Yes, happend to me too. Did you find a workaround for now?
@Christoph Nope, I'm using white theme, ugly but at least working.
Updating Xamarin.Forms helped for me...
I think it and worked fine now. Looks like fixed. I close it.
@Christoph @Mike the latest Forms version doesn't even compile. Which version are you using?
Oh wait, the pre4 fixed it! Too bad the last 5 updates (including the latest one) are still throwing compilation errors (red underlines).
@email@example.com I don't remember, I think it was 2.3.2 which I tested.
But the black theme still too ugly, I give up and continue use white theme.
This bug is still not solved.
XF 126.96.36.199 pre4 still shows this mis-behaviour when phone is on dark theme!
the same bug is also with the Editor-class.
Still not solved on 188.8.131.52 (both for entry and editor controls)
For me the problem just reappeared:
Xamarin Forms 184.108.40.206 does not have it, but with 220.127.116.110 it is back :-(