ITMS-90158

Hi guys, I am getting the following error when trying to upload for macOS. The same code works fine for iOS. Dear Developer, We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/MacOS/XXX: _CMTimebaseCreateWithMasterClock. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team Just FYI: I am not using CMTimebaseCreateWithMasterClock at all, but rather the preferred variant CMTimebaseCreateWithSourceClock. Neither of these are private AP

I am trying to upload an app using Xcode 8 beta 6. It is compiled against iOS 10 beta SDK. It has extensions which are also compiled for that SDK. The watchOS app is compiled against watchOS 3 SDK. When I upload it to Testflight through Xcode and Application Loader, it returns back with an errorERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for WatchOSApp must match its Bundle IdentifierCan some one help me solve this issue ?Thanks!

App Store Connect rejects the build with the following error: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90058: This bundle is invalid - The value for key CFBundleVersion [iphoneos] in the Info.plist file must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion But we double-checked at the app level; in all places the CFBundleVersion and versions is mentioned in the correct format. Even though we tried to upload via Xcode and Transporter, both show success. but the build is not reflecting in TestFlight. Receive the above error message via mail. data: { attributes: { cfBundleShortVersionString: 3.25.9, cfBundleVersion: 25, p Validated with the delivery log, but the delivery log also shows correct versioning only.

I am having trouble submitting my app with an iMessage extension to App Store.Using Xcode 8b4, I can export my app fine for AdHoc distribution over Hockeyapp.However when I try to use TestFlight, validation fails with [_NSCFConstantString isFileURL]: unrecognized selector sent to instance…I have no `isFileURL` calls in my code. I assume this is Xcode internal.Trying to submit the app anyway results in an ITMS-90168 invalid binary error:Anybody having similar issues?

I have added an alternate icon in my iOS app which I am setting using setAlternateIcon method. It works perfectly during development and local app distribution, however when I try to upload a build to App Store Connect, I get the following error: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIconTwo” that references asset “AppIconTwo” No such asset is present in the asset catalog. I'm unable to upload builds with this extra app-icon added. Kindly help me solve this.

I'm having a whole host of issues come back from iTunes Connect when trying to upload an iOS 9 app with watchOS 2 app and both Watch and CocoaTouch frameworks embedded. I've waited a week before posting this in case it was an issue with the iTunes Connect server.For the iOS 9 app, I received ITMS-90086: Missing 64-bit support. Architectures is set to $(ARCHS_STANDARD) (armv7, arm64) and Build Active Architecture Only set to NO for Release.For the Watch Framework, I receive ITMS-90087: Unsupported archtectures...[armv7k]. Architectures is set to $(ARCHS_STANDARD) (armv7k) and Build Active Architecture Only set to NO for Release.Also for the Watch Framework, I receive ITMS-90362: Invalid Info.plist value. The value of the key 'MinimumOSVersion' is invalid. The minimum value is 8.0. This key was not set in Info.plist at all. I manually added this key with the value 9.0, rebuilt, and resubmitted, with no change in error message.I also receive ITMS-90125: The binary is invalid.

Hi We're trying to publish an app build to Testflight. We've successfully done the build, but when we archive the build, we get this error: error itms-90168 null. We are able to upload the build, it then SEEMS like the build is successfully archived. Then we validate the app, which is successful, but then when we click distribute, it gives an error: error itms-90168 null We've been struggling with this for quite a while and have tried things to solve the issue, but we haven't been successful this far. It's difficult to try figure out what is wrong, as the error message merely says Null instead of giving specific details.

When attempting a routine* update to my tvOS app, I'm getting blocked by uploading from both Xcode and Application Loader with three errors:iTunes Store Operation FailedERROR ITMS-90471: Missing Image Asset. Your app is missing the Home Screen Icon asset in 'Payload/Lightbow.app'.ERROR ITMS-90471: Missing Image Asset. Your app is missing the App Store Icon asset in 'Payload/Lightbow.app'.ERROR ITMS-90471: Missing Image Asset. Your app is missing the Top Shelf Image Wide asset in 'Payload/Lightbow.app'.These assets exist, same as they ever did, in an asset catalog that was set up by Xcode. I deleted my asset catalog, manually re-added all my assets to a freshly created asset catalog with freshly-created Brand Assets folder inside with the templates usually there for tvOS, Cleaned, Nuked Derived Data folder, restarted Xcode, built a fresh archive and tried to upload to the App Store. Same result.Anybody else run into this or have a fix? I'm on Xcode 9.1 (9B55) and I believe the last s

When I try to submit my app build I get this error. I have no idea which API it is clashing with. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Frameworks/react_native_webrtc.framework/react_native_webrtc: addStream:, initWithBuffer:rotation:timeStampNs:, initWithURLStrings:, isBinary, localDescription, sdp, sendData:, setChannelId:, setIsEnabled:, stringForType:, typeForString:, videoSource. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

I have the nanopb.xcframework in my project that is used by FirebaseAnalytics. This issue is reported recently, and never before. ITMS-90338: Non-public API usage - The app references non-public symbols in CitytvVideoStaging: pbdecode, pbencode, pbistreamfrombuffer, pbostreamfrombuffer. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ What is the possible solution for this nanopb issue?

I'm trying to upload my app through application loader however I keep receiving error itms-90174: missing provisioning profile.However when I change the .ipa file to a zip file and view the contents of the app it shows the file named embedded.mobileprovision is there.Is this supposed to be in a different location? I've tried re creating all of my certificates, updating my Apple Mac however I am still receiving the same error.I am editing the Info.plist file as I kept recieving the error missing Info.plist key for NSPhotoLibraryUsageDescriptionKey and for NSCameraUsageDescription.

Hello. Icon fonts such as Font Awesome 6 and react-native-vector-icons are being rejected submission with the automated Invalid Binary error. ITMS-90853: Invalid font - There was an error validating the font named 'FontAwesome6Free-Solid' at 'private-app-name/FontAwesome6_Solid.ttf'. ‘glyf’ table instructions. These fonts have previously worked over the course of the last 3 years without issue and just stopped working on Monday. GitHub is filled with related issues and bug reports. This is likely affecting thousands of apps.