Open JBishopJr opened 7 years ago
scobbe
commented
7 years ago @JBishopJr: Based on some Googling, it seems like it may be related to have a superfluous .dSYM file.
Checkout out the thread here and try some of the suggestions and let me know if any of them help.
JBishopJr
commented
7 years ago I've followed all these threads without success. I have only 1 .dSYM onboard - ObjectiveDropboxOfficial.framework.dSYM, which is dictated in the installation instructions (which have worked fine up through v. 3.0.18). This app has been on the App Store and outside delivered with Developer ID for years, and for a month or so with the new Dropbox API. The ObjectiveDropboxOfficial info.plist contained the CFBundleSupportedPlatforms "MacOSX" previously without incident. This seems to be a new failure.
There may be threads online that claim removing ALL .dSYM's from the Project fixes this issue... it doesn't here. I've successfully validated and submitted with the Dropbox .dSYM to the Mac App Store today, and failed to validate a Developer ID signed version with AND without the .dSYM included. My surmise at the moment is that validation of a Developer ID signed app via Apple fails every time now. I'm continuing to try to track this down.
John Bishop
On Jun 19, 2017, at 3:12 PM, Stephen Cobbe notifications@github.com wrote:
@JBishopJr: Based on some Googling, it seems like it may be related to have a superfluous .dSYM file.
Checkout out the thread here and try some of the suggestions and let me know if any of them help.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
John Bishop Mulligan Software mailto:jb@mulligansoftware.com http://www.mulligansoftware.com Twitter: MulliganGolf
scobbe
commented
7 years ago Hmm that's strange. Any chance the .dSYM in your bundle is somehow cached from the 3.0.18 SDK, instead of the latest SDK?
I'll look into the "MacOSX" issue, but that frankly would be a surprisingly aggressive name deprecation from Apple to suddenly start failing validation like this (and without an appropriate error message).
JBishopJr
commented
7 years ago No chance the Dropbox .dSYM is old. But, there is a chance that Apple now can identify the difference between an App Store version of the app and a Developer ID version of the app and fail if the there's ANY .dSYM onboard the Developer ID target.
I agree about the "MacOSX" deprecation, but Apple also has documentation that there is ONLY one valid CFBundleSupportedPlatforms key: "iPhoneOS". But that documentation might be deprecated too! (One of the threads online discusses valid entries for CFBundleSupportedPlatforms).
I have the app into review at Apple, and I have the app, unvalidated via Xcode, ready to go outside the App Store. So,.. I'll survive.
Thanks for looking at this. John
On Jun 19, 2017, at 4:57 PM, Stephen Cobbe notifications@github.com wrote:
Hmm that's strange. Any chance the .dSYM in your bundle is somehow cached from the 3.0.18 SDK, instead of the latest SDK?
I'll look into the "MacOSX" issue, but that frankly would be a surprisingly aggressive name deprecation from Apple to suddenly start failing validation like this (and without an appropriate error message).
John Bishop Mulligan Software mailto:jb@mulligansoftware.com http://www.mulligansoftware.com Twitter: MulliganGolf
Cannot pass online validation from Xcode of an app using latest ObjectiveDropboxOfficial signed with Developer ID credentials. Validation error message is: An error occurred during validation Couldn't find platform family in info.plist CFBundleSupportedPlatforms or Mach-O LC_VERSION_MIN for ObjectiveDropboxOfficial
version 3.1.2 info.plist contains a CFBundleSupportedPlatforms array item with 1 entry "MacOSX". I believe this key is either in error or being improperly validated. Apple seems to be phasing out the "MacOSX" nomenclature (it doesn't survive on their web site for example) and instead is using "macOS" or "MacOS". Why was this CFBundleSupportedPlatforms item added to Dropbox's framework? Is it an error? Was it tested vs. Apple's application validation checks?