I can reproduce the constraints warnings in iPad Pro 11" iOS 14.3 Xcode 12.3. Among the first warnings issued, this was the first: "<NSAutoresizingMaskLayoutConstraint:0x600003318dc0 h=--& v=--&

It runs fine with the 4th gen iPad Pro Simulator for me (using Xcode 12.3). Nothing shows up in the console. There's one warning: warning: Auto Layout Localization: Views without any layout

https://github.com/tridiak/ConstraintsBug/tree/main Constraints error also occurs in the iPad simulator.

Can you post your simple dummy project someplace, if it reproduces the constraints error?

Created a simple dummy project. Text field Begin, Changing and End actions work fine. (Been a while since I did iOS programming. Noob mistake). The wall of constraints error still occur

This is the view hierarchy. I have not added in ANY constraints. There is no top bar or bottom bar. I have not selected or coded any option to remove them. <UIWindow: 0x113e09050; frame = (0 0; 768

Autolayout should have nothing to do with target/action. Check in your changes and remove all constraints. See what happens then. Then revert and remove 1/2 of your constraints. Lather, rinse,

Ok. Thanks for help. I look into it. Using Storyboard. Note: I have set no constraints. The bug prevents IBAction from working.

That's only correct if you're setting constraints on them. If you're positioning them old-school, i.e. by expressly setting frame and thus using the autoresizing mask, then this property must remain

<snip other auto layout errors> If you're creating the views in code then for each UIView subclass you create, you need to set translatesAutoresizingMaskIntoConstraints to false. If you're create

I have an iPad app with ~60 labels and text fields. Whenever I start to edit one of the text fields, I get this: [LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least

In part of this thread, we talked about using build environment variables for um, stuff and things. Here’s a short little write up I did last year to show how massively useful they can be. Using

Ah! The answer is "Yes"! I never clicked on the little reveal icon. Thanks for pointing it out, Marco! -Carl

Am I clicking on the wrong thing?

Am I clicking on the wrong thing? The target is the uppermost item in the left column in Xcode? Or is it under the "Targets" column in Edit Scheme -> Build? Neither one gives me a Duplicate ... I'm

That’s what I’ve used..

I still see Duplicate on the menu that pops up when I right-click a target.

A better explanation is that the info.plist uses that build setting, that environment variable as the name of the executable. There’s a little relationship between $(TARGET_NAME), $(PRODUCT_NAME)

What about using NSUserDefaults -addSuiteNamed: https://developer.apple.com/documentation/foundation/nsuserdefaults/1410294-addsuitenamed Could you add subdomains for each of the areas for which you

Yes - $(TARGET_NAME) is the correct identifier! Setting this also changes the executable name under ../MacOS and CFBundleName and CFBundleExecutable in the Info.plist. Thx! -Carl