Nativescript-ui-feedback: RadListView stoped working after Xcode update to version 9

[bozhidarc]

Did you verify this is a real problem by searching Stack Overflow?

_Yes_

Tell us about the problem

The RadListView stoped rendering any content. It was working until I update my Xcode version to 9.
I'm using the latest version of nativescript-pro-ui 3.1.3.
Here is a gist of my component
https://gist.github.com/bozhidarc/ae7d3fe2a16d8e15c4882103eb5bd33e

Which platform(s) does your issue occur on?

I'm using iOS 11 on iPhone 7 emulator.

Please provide the following version numbers that your issue occurs with:

• Progress NativeScript UI version: 3.1.3
• CLI: 3.2.1
• Cross-platform modules: 3.2.0
• Runtime(s): "version": "3.2.0"

Please tell us how to recreate the issue in as much detail as possible.

I'm using the RadListView inside a modal, but I don't think the problem is in the modal, because first it was working and second if I replace the with a Label for example it works fine.

Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.

https://gist.github.com/bozhidarc/ae7d3fe2a16d8e15c4882103eb5bd33e

[VladimirAmiorkov]

Hi @bozhidarc ,

We are aware of this and other issues with RadListView when running on iOS 11. The good news is that a fix for this one has already been implemented it in our "in development" (next npm tag) version. You can test it by changing your package.json to:

"nativescript-pro-ui": "next"

Please let us know if you notice any other issues when running on iOS 11, als okeep in mind that the "next" version is taken from our development branch which is being update on daily/ hourly basis and should not be consider for release versions of your app. We plan to release a minor patch 3.1.4 that addresses this and other iOS 11 related issues in the coming week.

[bozhidarc]

Thank you for the fast reply!
I will definitely let you know if I found something else and I'm looking forward to the release of the 3.1.4 version.

[VladimirAmiorkov]

Hi @bozhidarc ,

This issue has been resolved and a fix for it is available in our latest patch version 3.1.4. Release notes can be found here.

Closing the issue.