New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android: When used on a stack on top of a circle-shape container, the CirclePercentIndicator widget is not rendered properly. #13
Comments
Hello, I tested your code on my android device running Android Pie (9.0) and it works fine. flutter doctor what version are you using? |
Hi. This is what I'm running: And the emulator: |
Try changing to 'stable' version. run : flutter channel stable |
I changed to stable and the issue remains. Just for fun, I tried running it on Android Pie and same thing. Anything else I might try? |
Could you add a screenshot to check how it looks like? Also add the flutter
doctor log here.
…On Sun, Jan 20, 2019, 6:58 PM Maximiliano Diaz ***@***.*** wrote:
I changed to stable and the issue remains. Just for fun, I tried running
it on Android Pie and same thing. Anything else I might try?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEq90O9aMJ7uW5qh5zT05LCB4gjNHVCJks5vFQKggaJpZM4aJ3fi>
.
|
Here is the doctor log:
And a video, in which you can see for a couple of frames that it draws correctly before being over imposed by the black circle container: |
Oh ok , I thought stable version had an upper version. so try using dev channel , just for testing: run: flutter channel dev |
It works completely fine on the iOS simulator, but there is something weird happening while using the Circle Percent Indicator in a Stack widget on top of a container also made to look like a circle using BoxShape.
What is even weirder is that when Debug Paint is on, it looks properly rendered.
I think the images make it clear.
The text was updated successfully, but these errors were encountered: