The framework layout doesn't meet Apple's Bundle Guidelines. Everything is in the root of the bundle, with no "Versions" folder. I suspect it works because the main executable and the "Resources" folder are in the root. However Code sign doesn't complain about it either, unlike some other incorrectly formatted bundles. I ask because the documentation for bundle structures hasn't been updated since 2017 (https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html#//apple_ref/doc/uid/10000123i-CH101-SW1) and I am wondering if there is newer documentation or perhaps Framework bundles no longer need to organized according to that documentation.

Was under the impression that all executable components needed to be signed with the same certificate as the bundle. However I've just encountered a recently Notarized application where that isn't the case. These components are in the "/Contents/Resources/" folder of the main bundle. While I can suggest the developer to sign these with the same identity and move them to a more suitable location. It would appear that codesign, GateKeeper and Notarization has accepted these. Or are these restrictions for the Mac App Store only?

Hi All, Trying to validate some altool credentials, produces this error message. "Failed to get authorization for username '<username/>' and password with errors:( "Error Domain=NSCocoaErrorDomain Code=0 "Status code: 0" UserInfo={NSLocalizedDescription=Status code:0, NSLocalizedFailureReason=The auth server returned a bad status code.}") This is returned when altool is called in the following way. xcrun altool --notarization-history 0 -u <username/> -p <password/> --output-format xml macOS 11.2.3 and Xcode 12.5 Things that have been tried already. Making sure the Apple system status page shows no issues. Different networks. Checked to see if any agreements need to be "activated". Recreated the app-specific password multiple times. Any other suggestions? @Quinn - Hi Quinn, it's Sam Rowlands (again) and this is with another App Wrapper customer experiencing this issue (so not me directly).

Trying to upload an application for Notarization, fails with the following error message. Any ideas? 2021-04-22 12:32:29.127 altool[71379:2755143] Error: Error: Could not find or load main class Drive.Moved Caused by: java.lang.ClassNotFoundException: Drive.Moved 2021-04-22 12:32:29.138 altool[71379:2755143] Out: ?xml version="1.0" encoding="UTF-8"? !DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "urlsNotAllowedInSupportForums" plist version="1.0" dict keyos-version/key string11.2.3/string keyproduct-errors/key array dict keycode/key integer-18000/integer keymessage/key stringCould not find or load main class Drive.Moved/string keyuserInfo/key dict keyNSLocalizedDescription/key stringCould not find or load main class Drive.Moved/string keyNSLocalizedFailureReason/key stringCould not find or load main class Drive.Moved/string keyNSLocalizedRecoverySuggestion/key stringCould not find or load main class Drive.Moved/string /dict /dict /array keytool-path/key string/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework/string keytool-version/key string4.029.1194/string /dict /plist

https://developer.apple.com/documentation/bundleresources/information_property_list/lsminimumsystemversionbyarchitecture?language=objc Shows the values for PPC, PPC64, i386 & x84_64. But there's no values for ARM. Can someone from Apple please provide what the values should be. I'd hate to use the wrong value, i.e. "arm64" when it should be "arm64e" or vice versa. Maybe it's not even arm64 and it's something else?

For days I've been banging my head against an issue with developing an In-App-Purchase based application on a 2 day old 16" MacBook Pro running macOS 10.15.4.When my application calls [[SKPaymentQueue defaultQueue] finishTransaction:inTransaction] it gets stuck in an infinte login loop.This ONLY happens on this brand new 16" MacBook Pro running 10.15.4. It works on a 12" MacBook running macOS 10.15.4 and a (2012) 15" MacBook Pro running macOS 10.14.6.There's two things here I want to know.1. I can't find any evidence online of this ever occuring, is there someone who's come across this before and if so, how did you solve it?2. As it only occurs on this machine, I've tried the following to see if I can fix it (thinking that the machine is a lemon).a) Boot into "Safe" mode [no change].b) Run Disk Fist Aid from Recovery [no change].c) Re-installed the OS from Recovery [no change].d) Created and tried a new user [no change].e) Reset PRAM & NVRAM [no change].There was one change which kinda worked, but is back to failing again this morning. I deleted all the cache relating the App Store that I could and rebooted. I still got stuck in an infintie login loop, but the transaction did actually complete and the item was added to the receipt. However this morning when I tried it again, it's back to just getting stuck in the loop and transaction is never added to the receipt.There two options left that I can think of right now.1. Obliterate the drive (using Disk Utility) and with just a clean OS, test my app. I am reluctant to do this because of the increased down time in testing a theory that I suspect will not show any difference.

As the title suggests I've hit a brick wall and don't know what do about it.I can't submit my application with IAP because I can't submit my IAP item, because it's missing meta-data. The only information I am unable to add is the screenshot for the reviewer.According to the Apple documentation, the screenshot needs to be macOS requires 1280 x 800 pixels. However trying to add an image of that size, gets refused saying "Invalid Size". I've tried different file formats and even different file names, same thing happens again and again.If I add an image of another size, it's initially gets accepted, but then when I try to save, a new error dialog appears saying I need to submit an image of valid size.In desperation I tried to submit and see if the App Store Reveiewer could assist; even after explaining the situation to the reviewer and providing the images, the reviewer just blockaded everything and told me I need to submit my IAP item with my application. Which I don't seem able to do so.I have spent two years developing this application, then months on top as I had to re-wire everything to use IAP because I was told by App Store to make it In-App-Purchase, and now I've completed this, I still can't sell my app on the Mac App Store.Is there anything I can do?Yours DesperatelySam Rowlands

I have a customer who has a 2010 Mac Pro running macOS 10.14.6, this customer is trying to use my application with RAW images from their Nikon camera ( 8256 x 5504 ).The customer gets an image at the correct size, but with only 1 row of pixels, the rest is black. When I test the images on a 2012 MBPr, it works fine, or a 2015 MacBook, it also works.The customer also tried an image that is 8166 x 5302 and that works for them. When my app does it's processing, it logs as much information about the CIContext as possible, including [CIContext inputImageMaximumSize] and [CIContext outputImageMaximumSize], which both report 16384 x 16384, yet the context doesn't return the results I'd expect when the images exceed 8192 x 8192 on this customers machine.I am leaning towards the idea that the macOS is returning incorrect information and the graphic card on their Mac Pro doesn't actually support anything higher than 8192 x 8192.If it helps, here is the log from the context. priority: default workingSpace: (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; Generic HDR Profile) workingFormat: RGBAh downsampleQuality: High max sizes, in{16384 x 16384} out{16384 x 16384}Any ideas or suggestions?To create the context it calls [CIContext context].To create the data it calls [CIContext render:toBitmap:rowBytes:bounds:format:colorSpace:]