[iOS] PullToRefresh activity indicator improvements - fix#20824
[iOS] PullToRefresh activity indicator improvements - fix#20824jfversluis merged 2 commits intodotnet:inflight/currentfrom
Conversation
|
Hey there @kubaflo! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
| await Task.Delay(500); | ||
|
|
||
| //The test passes if the activity indicator is above the header | ||
| VerifyScreenshot(); |
There was a problem hiding this comment.
ValidateScreenshot will compare the screenshots pixel by pixel. Taking into account the animation of the position of the loading indicator as well as the rotation of the indicator itself, I would say that it would be better to create a device test to validate that it is within a range as well as the size.
There was a problem hiding this comment.
You're right this test will probably fail in most of the cases. However, I'm not sure if the device test will be useful in this case. Maybe we should just not write a test for this issue?
There was a problem hiding this comment.
Yeah, i think in this case have sense a tests checking Frames etc. Take a look to the GetRect extension method used in UITests. Let me know if need help with something.
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
5ebde61 to
d17ded2
Compare
|
Any news on this bug? This is one of the latest bugs preventing us from publishing our application. |
|
Same for me... is there a timeline to finally fix this bug? |
d17ded2 to
70d4639
Compare
|
Here we go again lol. Hi, @metalium84 @taenito The MAUI team's priorities are not up to me, but you can have this fix in your app by following this @jfversluis's video if it is a major blocker for your migration https://www.youtube.com/watch?v=B2FOBjZKm9k&t=301s&pp=ygUWZ2VyYWxkIG1hdWkgcHIgdGVzdGluZw%3D%3D |
|
Azure Pipelines successfully started running 3 pipeline(s). |
If you do test this out and let us know if this works for you that will give us more confidence that this is a right fix and we can merge it sooner. So please let us know, thanks! |
|
I tested the branch and the loader is no longer hidden behind the header. We still have a lot of bugs with the |
|
@taenito cool! Thanks for confirming it! |
70d4639 to
fa05236
Compare
|
/rebase |
fa05236 to
7909d39
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
7909d39 to
2ef173c
Compare
|
This PR solves the same issue with CV2: Screen.Recording.2025-03-08.at.02.56.37.mov |
|
Hi - any update on this fix. Still not been reviewed by the looks of it? |
* [iOS] Fixed hidden indicator * [iOS] Fixed hidden indicator
* [iOS] Fixed hidden indicator * [iOS] Fixed hidden indicator
* [iOS] Fixed hidden indicator * [iOS] Fixed hidden indicator
* [iOS] Fixed hidden indicator * [iOS] Fixed hidden indicator
* [iOS] Fixed hidden indicator * [iOS] Fixed hidden indicator


Issues Fixed
Fixes #20723
Fixes #24960
bug.mp4
fixed.mp4
Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-10-15.at.11.33.09.mp4
Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-10-15.at.11.28.24.mp4
The same issue happens with CV2
#20824 (comment)