Repository navigation
Switch not visible with NS 3.0 on ios #4175
Description
From @sebawita on May 12, 2017 15:22
When I use <Switch> with NS 3.0, the component doesn't get rendered on iOS (it does work fine on Android though), however there seems to be an empty space where the UI component should be.
<Switch
[(ngModel)]="profile.angularPro">
</Switch>
However when I use horizontalAlignment="left" the component appears just fine.
<Switch
[(ngModel)]="profile.angularPro"
class="switch"
horizontalAlignment="left">
</Switch>
Copied from original issue: NativeScript/ios-jsc#764
Activity
NickIliev commentedon May 15, 2017
@sebawita thanks for posting this issue - I can confirm that this is a reproducible bug for iOS with NativeScript 3.0.0. We will update the information here once we have released a fix.
Reproduced with NativeScript 3.0.0 in both non-Angular (here) and Angular apps (here).
For anyone interested, as a temporary workaround, use the solution provided by @sebawita by setting horizontalAlignment to left, center or right
vchimev commentedon May 16, 2017
This issue does not reproduce with {N} 2.5. Another workaround in 3.0 is to set
widthproperty.TODO: Update related test page by removing height and width properties when fixing the issue.
toddanglin commentedon May 17, 2017
Can further confirm that setting the
widthstyle property to any value will make theSwitchappear on iOS. So even settingswidth:1;will make theSwitchappear as expected.For a "global" workaround 'til a patch is released, I think you should be able to do this in your
app.cssstylesheet using an element selector:2 remaining items
Include scenario for issue 'Switch not visible with NS 3.0 on ios #4175'
SvetoslavTsenov commentedon May 19, 2017
The fix is available in tns-core-modules@next
Include scenario for issue 'Switch not visible with NS 3.0 on ios #4175'
dtopuzov commentedon May 22, 2017
Fix will be released in 3.0.1 later this week.
lock commentedon Aug 28, 2019
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.