unoplatform / uno

Open-source platform for building cross-platform native Mobile, Web, Desktop and Embedded apps quickly. Create rich, C#/XAML, single-codebase apps from any IDE. Hot Reload included! 90m+ NuGet Downloads!!
https://platform.uno
Apache License 2.0
9.04k stars 734 forks source link

`AsyncValuePresenter` not able to respond only for first 4 `ListView` items. #6260

Open ac2021-June opened 3 years ago

ac2021-June commented 3 years ago

Current behavior

We have an AsyncValuePresenter control inside a ListView item template alongwith other static information. For some reason, for the first 4 rows the AsyncValuePresenter users are not able to refresh the content. After the 4th tile, everything seems to be working.

<u:FeedView>
    <ListView.ItemTemplate>
        ------
        ------
        <u: AsyncValuePresenter
            -------
            -------
UseRefreshingState="True" />

    </ListView.ItemTemplate >
</u:FeedView>

Expected behavior

All the sub-tiles which have the AsyncValuePresenter, should be able to refresh.

How to reproduce it (as minimally and precisely as possible)

We have the structure of the UI elements as follows:

<u:FeedView>
    <ListView.ItemTemplate>
        ------
        ------
        <u: AsyncValuePresenter
            -------
            -------
UseRefreshingState="True" />

    </ListView.ItemTemplate >
</u:FeedView>

Workaround

None. Generally observation though, the issue goes away when we get the following message in the Output window: Received XPC error Connection interrupted for message type 3 kCFNetworkAgentXPCMessageTypePACQuery

Environment

All environments.

Nuget Package:

Nuget Package Version(s):

Affected platform(s): Only iOS is affected.

IDE: Microsoft Visual Studio Enterprise 2019

Relevant plugins:

Anything else we need to know?

jeromelaban commented 3 years ago

Thanks for the report.

In order to help troubleshoot the issue, we'll need a simple reproduction project that clearly demonstrates the issue.

To create a minimal reproduction project:

no-response[bot] commented 3 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. We don't monitor discussions on closed issues thus please open a new GitHub issue if you need the team to revisit this matter.

renecnventive commented 3 years ago

Reopening with Repo link. Please reach out to Rene Charbonneau for info on downloading the attached file if need. https://nventive-my.sharepoint.com/:u:/p/rene_charbonneau/EWPutwbOk6NFm0SJfb12fD4Bv6eAPeEb1wCWhAEjjf1oWw?e=unmK8H

no-response[bot] commented 3 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. We don't monitor discussions on closed issues thus please open a new GitHub issue if you need the team to revisit this matter.

ac2021-June commented 3 years ago

Steps to reproduce alongwith the sample application shared on the shared folder.

AC-ACL3 commented 3 years ago

Hello, Here's some context about this issue and why it is for us a high priority bug that we need to have fixed as soon as possible. (Note that the same applies for #6263 and #6264.) This issue is a blocker for a major app version update we are planning to do on Aug 11. We are looking to release our 3.0 version of our app which contain many important (and very cool!) new features expected by our stakeholders. Your help is very much appreciated!! Let us know if anything else is needed. Thanks a lot!

AC-ACL3 commented 3 years ago

Update: looks like the issue is related somehow to the tabs displayed on the Homepage. Here are a few findings from our investigation:

A new application sample was provided last Friday with only the Homepage with tabs and the flight search/results. Investigation is still ongoing.

ac2021-June commented 3 years ago

Even after attaching .Unloaded method, the method is not getting called. This happens only on iOS devices. On Android devices, we are able to hit the .Unloaded method. Please help us as what needs to be done in this situation.