In Control Gallery Sample, iOS Displaying Incorrect Text in TableView
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
On Control Gallery solution, files dated 11/29/2023, as downloaded on 2/5/2024, unmodified. Built in Visual Studio 2022, version 17.8.0, on Windows 10.
This behavior is shown in the attached video. On iOS device running the Control Gallery app, displaying the Activity Indicator then returning to the main screen works correctly (time 0 to 14 seconds). I then scroll down to the bottom of the menu, then back to the top (15 to 22 seconds). The text displayed in the TextCells on the main menu is now incorrect. The top one says VerticalStackLayout instead of AbsoluteLayout, and the second one down says WebView instead of ActivityIndicator. However, when I tap the second one, I get the ActivityIndicator (23 to 30 seconds), which is correct behavior for that position. Somehow the Text property of the TableCell is not being correctly shown, although the Command and CommandParameter properties are being correctly used.
I observed this behavior on the following devices:
iPhone SE, iOS 17.2.1
iPad 7th generation, iOS 16.5.1
iPhone 6s Plus, iOS 15.8.1
The Control Gallery solution performed this operation correctly on Google Pixel 4 running Android 13, and on the Windows Machine running Windows 10 (although see the adjacent issue for a different problem with the Control Gallery on Windows Host).
Any ideas as to fix or workaround? Tx
https://github.com/dotnet/maui-samples/assets/24593474/391e1db6-578c-460b-b0d2-b0757f837447
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the Control Gallery solution and reproduce the issue on an iOS device by visiting the Activity Indicator, scrolling to the bottom of the menu, and returning to the top. Inspect the TableView TextCells and compare their displayed Text values with the commands and command parameters; done means the labels remain correct after scrolling while navigation still works on the affected iOS devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, ios
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100