I commented out the HStack in my code this morning and it started working. I have no idea. Thanks for your reply.

I am seeing the same problem as R4N in his second quote (when using Swift). Specifically, NSItemProvider.loadDataRepresentation(for: UTType, completionHandler: (Data?, (any Error)?) -> Void) -> Progress (when used with UTType .heic) returns the expected result with no error to the completion handler, but issues the message to the console: -[_EXSinkLoadOperator loadItemForTypeIdentifier:completionHandler:expectedValueClass:options:] nil expectedValueClass allowing {( NSNumber, NSMutableDictionary, NSDate, NSString, NSError, NSDictionary, NSData, UIImage, CKShare, NSMutableString, NSMutableArray, NSUUID, NSMutableData, NSValue, NSURL, _EXItemProviderSandboxedResource, NSArray )} I don't know how to look at someone else's feedback (by the number) so don't know if there's been any progress on that.

I've created a demo project. I've saved it as an "xcworkspace" but this system won't let me upload that as a "File", even if I zip it. Tell me how to get it to you.

Official feedback is FB13195763

I was already at the latest version of Xcode. If it's working for you now it's only because they fixed the problem. After 20 hours one of my two builds was finally processed. (The other one is still MIA.) I did open a case with Apple Support so perhaps they "carried" mine thru the process.

My submission was processed after about 20 hours, perhaps because I opened a case with support.

As I said in another post (I'm sure you read that before posting, right?)... when I contacted Apple they told me they were unaware of the problem. My opened ticket may have helped. This has noting to do with iOS14 (unless it's taking up their available CPU power).

I've been waiting 19 hours for my builds to show up in Activity. I just did "Contact Us" with the App Setup and Distribution area; Build Delivery and Processing and they tell me THEY ARE TOTALLY UNAWARE OF ANY ISSUES/PROBLEMS. Please contact them, which will open a Case, so they can let the appropriate people know about this.

It lets me into Activity page now ... but doesn't show the upload I did hours ago. I tried deleting from the Archive, re-archive, re-upload and it told me I'd already used that build number (ok; where is it then?). I uploaded a different build then, and it was "successful" but still doesn't show up in Activity (for almost two hours now). I guess this is one way to reduce the number of apps that have to be approved by an overworked staff.

You are right. Very confusing. When I did this (some months ago now) I did create a Sandbox user account, but never found that it was used. My experience is that if you are running a version installed from Xcode, or (I hear) a version from TestFlight, the IAP stuff recognizes this and let's you proceed as normal, except that all of your transactions are done in a "Sandbox" mode, where it doesn't actually charge whoever makes the purchases any real $$. In other words, just use your normal Apple account and it works. The only thing that isn't "automatic" is that Receipt verification for testing purchases has to be directed to the test Apple server in your code. There are plenty of examples of "try one and if it fails, fallback to the other". Hope that helps.

They did the same thing to me a few weeks ago. I finally gave up and just re-submitted. I contacted App Review support about this and the conclusion was that the reviewers hadn't followed protocol.

Without any notification and subscription capability it is DOA. Back to the drawing board guys. I don't care about "top posts". I'd be way more interested in newest posts.

A restart fixed it. Thanks Claude!

This answer is addressing allowing fonts to shrink rather than vary dynamically.I just wanted to mention (for others who find this answer in a search) that in 2020, there is another step that is necessary, which is: button.titleLabel?.lineBreakMode = .byClipping(or any of the ".byTruncating..." options; it can NOT be either of the "wrapping" options, which are the default inside a button.)You might also want to do button.titleLabel?.numberOfLines = 1or some other value of your choice. The default inside a button is 0, which means as many lines as needed, which might give you less reduction that you want. Now here's an interesting tip. If you change lineBreakMode, it sets numberOfLines to 1! If you want to set numberOfLines to something else, you have to do that last.I recommend the following:extension UIButton{ func allowTextToScale(minFontScale: CGFloat = 0.5, numberOfLines: Int = 1) { self.titleLabel?.adjustsFontSizeToFitWidth = true self.titleLabel?.minimumScaleFactor = minFontScale self.titleLabel?.lineBreakMode = .byTruncatingTail // Caution! The above causes numberOfLines to become 1, // so this next line must be AFTER that one. self.titleLabel?.numberOfLines = numberOfLines }} Barry

Thanks Claude. So it might be a Catalina thing (I'm on 10.15.3).Anyone else on Catalina can try this? Barry