Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ERROR ITMS-90085 when validating archive only in Xcode 10
When I archive my iOS app in Xcode 10 and then validate, I get this error:ERROR ITMS-90085: “No architectures in the binary. Lipo failed to detect any architectures in the bundle executable.”I have checked the executable with lipo and I can see that both arm architectures are present. I have Googled around and tried a few other things associated with this error: I checked that all Product Names are set correctly, I have verified that no static libs are being embedded in a framework, I checked that all CFBundleExecutable values for Frameworks' Info.plist files match up to their respective binaries.I also tried archiving and validating in Xcode 9. That passes validation. I also tried validating that Xcode 9 archive with Xcode 10, that also passes!So it seems that something is different with how Xcode 10 makes archives, or how it validates them. How do I fix this? The error message is completely unhelpful.
4
0
6.3k
Jan ’19
Reply to Xcode errors when submitting an app
So the issue has gotten worse with Beta 2. Very confusedPackage Summary:1 package(s) were not uploaded because they had problems: /var/folders/yc/65_yjgfd0g76td7376jb4xnw0000gn/T/BC872C8A-7723-4C91-9F2B-DDC14B002E9C/1000756457.itmsp - Error Messages: ERROR ITMS-90171: Invalid Bundle Structure - The binary file 'SwiftSupport/watchos/libswiftCore.dylib' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https:/ ERROR ITMS-90171: Invalid Bundle Structure - The binary file 'SwiftSupport/watchos/libswiftCoreLocation.dylib' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https:/ ERROR ITMS-90171: Invalid Bundle Structure - The binary file 'SwiftSupport/watchos/libswiftUIKit.dylib' is not permitted. Your app can’t contain standalone executable
Jun ’15
Test Flight Rejection : ITMS-90338: Non-public API usage
Today, I'm getting Test Flight builds rejected with the following reason: ITMS-90338: Non-public API usage - The app references non-public selectors in MyRedactedAppName: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion However, I'm uploading the exact same code (working on a CI/CD pipeline) as I did last Thursday and that build passed. Pretty sure this is on the Apple side of things. Anyone else seeing this today? I know a few folks have had similar rejections since June 6, when things got updated for WWDC. Some seem to have been resolved by Apple, but I've tested this twice today and received the same result.
3
0
3.7k
Jun ’22
Manual signing app - ITMS-90078: Missing Push Notification Entitlement
Hi, Maybe someone here can help me ... I have an app (ios xcode swift) that I need to distribute unsigned. So far so good (in the xcode project target settings I have inserted the field: 'CODE_SIGNING_ALLOWED setting for release' NO '. In this way using' Archive 'I get the package in xcarchive format. Just a problem, the app has some 'entitlement' settings like push notifications, background use of bluetooth .. .etc. When my client tries to distribute the app with 'Organizer', he signs it with his certificate and provisioning file, and then downloads to the app store. but I always get the error 'ITMS-90078: Missing Push Notification Entitlement' Has anyone of you already distributed an app with the 'manual' signature as I do in practice?
1
0
2.1k
Feb ’22
ITMS-90809: Deprecated API Usage - for UIWebView not going away
Hi, I have replaced all uses of UIWebView with WKWebView in my project so there is no reference of UIWebView in the code anymore but I still keep getting ITMS-90809 every time I upload my App to the App store. I also used grep to identify any usage of UIWebView in the project but only getting a single reference in UserInterfaceState.xcuserstate. Can anyone help me getting rid of this please? I already tried to delete the workspace and taken fresh clone from remote repository but this keeps coming: $ grep -r UIWebView . Binary file ./project.xcworkspace/xcuserdata/manishrathore.xcuserdatad/UserInterfaceState.xcuserstate matches Can you please help me sort out the issue? Appreciate your help. Thanks & regards, Manish
3
0
1.5k
Nov ’20
ITMS-90338: Non-public API usage, but no results included.
ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/
0
0
331
Jan ’23
ITMS-90338: Non-public API usage automatic refuse
Recently, I've got automatic response after archive my App into the testflight as above. 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 selectors in Runner: initWithParentViewController:. 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 Problem is that I can't find the way to identify Non-public API usage on my code. I've build my app with Flutter, not swift. And there were no problem previous build, ver 2.0.15. Please let me kn
0
0
516
Jan ’23
xcode cloud build failed ITMS-90055: This bundle is invalid
Environment info Local machine: macos xcode 16 beta macOS Sequoia beta xcode cloud: Xcode latest release version (15.4). MacOS latest version I checked my project bundle identifier several times, it absolutly match to Apple Store connect. IIs failed occurred when workflow archive - distribution select testfight. If I select None in distribution, it Build success in Xcode cloud. Ps: I cannot archive from local machine, it shows Xcode version should be released version. Anyone meet the same problem? --- failed notification email attached below --- We noticed one or more issues with a recent delivery for the following app: WGesture Watch App Version 1.0 Build 8 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, 'com.war.WGesture.watchkitapp'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect.
2
0
798
Aug ’24
ITMS-90683: Missing purpose string in Info.plist - NSLocationAlwaysAndWhenInUseUsageDescription
In our latest two pushes to AppStore Connect, we've been getting the following message, where we hadn't previously: Dear Developer, We identified one or more issues with a recent delivery for your app, XYZ 1.2.3 (123). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xyz.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. Oddly though, we've not really made any changes to our codebase that should trigger this. Just wondering if others ar
10
0
16k
Dec ’22