"changing property masksToBounds in transform-only layer, will have no effect" in Xcode 7

Asked 8/9, 2015 at 11:33 Answered 12/8, 2021 at 5:19

168

I am receiving this warning in the debugger console when I launch my app on iPad Xcode 7 beta 6. There was no such warning till Xcode 6. I don't understand why it may have come and that too, only on iPad.

According to an Apple forum thread it could be a bug from Apple's side. Has anyone found a solution for this?

Cindycine answered 8/9, 2015 at 11:33 Comment(14)

Just wanted to let you know that the same bug occured to me when launching a custom keyboard on the iPad – Absorptance 13/9, 2015 at 18:44

Has this been resolved in the GM ? – Superfetation 15/9, 2015 at 23:5

No I am still getting the warnings in GM – Cindycine 16/9, 2015 at 12:34

I have this warning when presenting modal UIActivityViewController. – Strut 17/9, 2015 at 14:58

Just migrated to Xcode 7 and I have the same warning as soon as a UITextView becomes first responder... – Environ 17/9, 2015 at 23:32

I have this pop-up when a UITextField has to becomeFirstResponder, the time the textField needs to actually becomeFirstResponder is also increased significantly. – Luxuriate 18/9, 2015 at 13:10

Same issue. It only seems to appear on the iPad for me. And yes the lag for the keyboard to become first responder is ridiculously long. It doesn't even happen some times. – Allegedly 19/9, 2015 at 5:39

Having same problem when presenting UIActivityViewController. Only occurs on iOS9 iPads. iOS8 is fine and iPhones are fine. – Chilton 21/9, 2015 at 18:47

@Cindycine Have you solved this problem? – Nystrom 29/9, 2015 at 4:35

No unfortunately not.. plus I'm looking into other issues my application has, so I'm occupied with those.. – Cindycine 29/9, 2015 at 6:38

Any luck solving this ? , I'm on Xcode 7 and it only occurs on iPad when presenting the keyboard. I'm not using any external libraries. – Legible 3/10, 2015 at 12:31

See this SO Question - looks like a bug and logged with Apple as such. – Doralin 19/10, 2015 at 15:26

I've got the same problem, only 3x... and I can't see what's causing it... will have to spend some time on it when I have some time... :-{ – Gleda 30/10, 2015 at 2:13

If you do not interact using the keyboard (i.e, if you use the trackpad or the mouse only), this warning is not happening. Was using Cmd+Q to quit the simulator from a particular ViewController and this happened whenever i was doing it. Instead, i tried with the Simulator->Quit option using mouse and this did not show up. Its a bug. – Danonorwegian 1/11, 2015 at 2:22

In order to get rid of this error un check clip to bounds option and put scale to fill to view to all view,UIStackView you have used in your project.

Peeples answered 8/5, 2017 at 9:57 Comment(2)

Verified. I am on Version 9.2 (9C40b) and this was the cause for me. Nice one – Contemplation 1/3, 2018 at 10:54

Thanks, uncheck Clip to Bounds from UIStackView removed the warnings – Cynthiacynthie 17/10, 2018 at 9:36

This is a bug in iOS, and still exists in the latest version, iOS 9.1. If you're reading this, please do us all a favor and file a bug report with Apple.

You may duplicate my radar (id: 23666339), which can be viewed on Open Radar here: https://openradar.appspot.com/23666339

The bug causes the keyboard to take forever to appear, and exists only on iPad as well as the iPad simulators.

UPDATE: This issue has been resolved as of iOS 9.2 (13C75).

Dimitris answered 25/11, 2015 at 21:16 Comment(2)

thank you for validating me on this - thought it was a problem with our app! – Zawde 7/12, 2015 at 21:5

I have noted that this still exists on 9.3 - – Costanzia 20/2, 2017 at 14:6

It could happen because you changed drawing attribute of the StackView:

when I set clips to bounds to true I get this warning

Sakai answered 2/7, 2019 at 14:32 Comment(0)

In case anybody is facing this issue because of a UIStackView in iOS 14, please check out this article:

https://useyourloaf.com/blog/stack-view-background-color-in-ios-14/

Long story short:

In iOS 14, UIStackView has changed from using a CATransformLayer to using a CALayer. I saw this first mentioned by Renaud Lienhart (@layoutsubviews) and then confirmed by David Duncan (@rincewindsama). This change is not (yet) mentioned in any release note or documentation (bug report FB8363575).

Winglet answered 28/10, 2020 at 15:51 Comment(0)

Problem Warning -> <CATransformLayer: 0x600000946e40> - changing property masksToBounds in transform-only layer, will have no effect

Solution = Simply uncheck the clip to bound from UIstackview box.

Picofarad answered 12/8, 2021 at 5:19 Comment(0)

Recommended topics

Hot tags