Post not yet marked as solved
So, I had a similar circular warning for this same method where I wanted to identify a JPG or a PNG image and create an image with the appropriate extension. Although a good example of how to use it was not clear to me and here's what worked for me (Objective C).
Import the newer identifiers:
@import UniformTypeIdentifiers;
Create a property to hold the identifiers:
@property (strong) NSString *imageType;
Assign one of the identifiers to the property:
if ([theImageExtension isEqualToString:@"png"]) {
_imageType = (NSString *)UTTypePNG.identifier;
} else {
_imageType = (NSString *)UTTypeJPEG.identifier;
}
Use it:
CGImageDestinationRef destinationRef = CGImageDestinationCreateWithURL((__bridge CFURLRef)theURL, (CFStringRef)_imageType, 1, NULL);
And that worked! (after many permutations)
BTW, I also took a completely empty (no additional code, nothing added to blank xib) Automator Action template (found in MacOS) in Xcode 13.2.1 and followed the Technical Q&A QA1885 exactly and still get this error.
Force Quit Xcode, restarted, opened project. Fixed. Thanks everyone.
Post not yet marked as solved
The documentation still says to select checkboxes for each family of complications BUT that is outdated for Xcode 12.3. I think I found only one line in thousands from WatchOS that, now, you need to add a key to Info.plist for the extension named ClockKit Complication - Supported Families and add Modular, Circular, etc. to that key.
No extra coding just template/glyphs in the right sizes for each sub-family.
Post not yet marked as solved
Ha, that thought has entered my mind. I don't think my app is popular enough to bother pirating on ****-broken phones. Haven't heard back from either although one of their email addresses was from a community-based biblical teaching center (not that there is anything wrong - or right - with that ;).
Post not yet marked as solved
Yes, it's a univeral app, but the restore process works perfectly on my iPads (and has for several years on dozens/hundreds of other customer iPads since 99% of users purchase the upgrade to control their iPads).
Post not yet marked as solved
Unfortunately, even grabbing the pickerview instances and measuring them in viewDidLayoutSubviews every time I hid all of them and unhid one of the pickerviews (I didn't know that would necessarily happen - so thank you for the hint), the frame measurements of the visible pickerview was still showed the previously-sized frame and not what is actually visible.For example, when a picker view starts with a height of 350, and then a selection from the segment control displays that same picker but the visible height is 310, in viewDidLayoutSubviews will stil lists that picker with a height of 350. When one of the other segments is chosen, the original picker now shows a height of 310 (what I expected it to be once everything was completed before) but the new segment has a height of 0.Something happens with pickerviews after viewDidLayoutSubviews, and that's what I'm looking for. But since I only really have two sizes, I suppose I can hack something together (get the two heights from the wrong pickerview and use them somehow) and hope it doesn't break with the next iOS version.
Post not yet marked as solved
Right or wrong, I use a PickerView subclass where I add a labelView calculated to be positioned next to the picker values. I don't add the label until drawRect: and I found that it is the ultimate place to know the completed view and doing the position calculation works.
Post not yet marked as solved
As I trace the view cycle, viewWillAppear actually comes before viewDidLayoutSubviews. At each step, I check for the frame/bounds of the picker and the width/height of the picker is 280,247, and in the simulator it looks and measures much bigger. But when I make a selection from the picker, it goes back to the viewDidLayoutSubviews of the viewController and the width/height is 335,433 (what it looks like).So, I still have no idea when the height goes from 247 to 433.
Post not yet marked as solved
I'll have to Google "Clean Build Folder" but I did not do that. After exiting and reopening Xcode several times it worked on the third time (no updates). I did create a new blank project and the same thing showed up initially in IB. But problem solved (for me).
Post not yet marked as solved
Setting "Use Trait Variations" allowed the iPad icons, but selecting Landscape for any of the devices does nothing (even though allowed in the plist attributes).
For the record, the solution that worked for me was found at https://stackoverflow.com/questions/28564072/there-are-one-or-more-errors-on-page-on-application-submissionI chose to just submit screenshots for 5.5" and 12.9" devices. Figured that would populate the rest automatically. No, you have to still go to the Media Manager and explicitly say (by checkbox) that you want each device to use these screenshots as appropriate.Wish Apple would create explanatory error messages instead of just an exclamation mark next to the base language.
OK, would still like to know when one can set properties of a child view of a view controller placing the view in IB, but solved the problem by just instantiating the subclass programmatically in viewDidLoad the old-fashioned way 😉
#35319272 Althought Apple makes it very difficult to complain about the forum because there is no item or section except OTHER.
