Did you verify this is a real problem?
Yes, I verified that the issue occurs outside of my application, and created a minimal reproduction repo. I searched for similar issues on stack overflow and in the issue tracker and could not find any.
Tell us about the problem
When applying borderRadius to a user's profile image that is fetched over https://, rather than res://, the image stops rendering entirely. Removing the borderRadius brings the image back.

Which platform(s) does your issue occur on?
iOS
Please provide the following version numbers that your issue occurs with:
- CLI: 3.1.3
- Cross-platform modules: 3.1.1
- Runtime(s): tns-ios@3.1.0
- Plugin(s):
Please tell us how to recreate the issue in as much detail as possible.
- Clone this repo: https://github.com/justindujardin/nativescript-image-border-radius-bug
- tns run ios and run on either the simulator or a device.
The repo is just the default angular app (--ng), with the routing removed so as to be focused on reproducing the bug.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
<StackLayout>
<Image src="https://cdn.rawgit.com/justindujardin/angular-rpg/gh-pages/assets/icon/icon.png"
borderRadius="100" width="32"></Image>
</StackLayout>
or
<GridLayout rows="auto">
<Image src="https://cdn.rawgit.com/justindujardin/angular-rpg/gh-pages/assets/icon/icon.png"
row="0" borderRadius="100" width="32"></Image>
</GridLayout>Reactions are currently unavailable
Did you verify this is a real problem?
Yes, I verified that the issue occurs outside of my application, and created a minimal reproduction repo. I searched for similar issues on stack overflow and in the issue tracker and could not find any.
Tell us about the problem
When applying borderRadius to a user's profile image that is fetched over https://, rather than res://, the image stops rendering entirely. Removing the borderRadius brings the image back.
Which platform(s) does your issue occur on?
iOS
Please provide the following version numbers that your issue occurs with:
Please tell us how to recreate the issue in as much detail as possible.
The repo is just the default angular app (--ng), with the routing removed so as to be focused on reproducing the bug.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
or