Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90338: Non-public API usage
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 Loupe: _CGImageGetImageSource. 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 There are two problems, one is that our release/production build is succeeding and uploading to TestFlight. The other problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have a
6
0
893
Nov ’22
ITMS-90338: Non-public API usage
ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _isKeyDown, _modifiedInput, _modifierFlags. 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/
1
0
533
Nov ’22
itms-services link not working on Azure Devops Wiki
I want to create a hyperlink for OTA installation of my iOS app on the Azure DevOps wiki page, has anyone tried it? I have tried using html tag, but when I click it, it only refreshes the wiki page. This is the link example using tag. My App I have also tried using markdown link, but it seems it doesn’t recognize itms-services syntax, this is the link example [My App](itms-services://?action=download-manifest&url=https://my.app.com/install.plist)
0
0
654
Nov ’22
ITMS-90334: Invalid Code Signature Identifier
I get the following error in Xcode Cloud when attempting to prepare a build for App Store: ITMS-90334: Invalid Code Signature Identifier. The identifier SwiftCharts-555549449cfa473253483215b74c174849d2ec9c in your code signature for SwiftCharts must match its Bundle Identifier SwiftCharts. This is an iOS app and Swift Charts is swift package dependency which the app depends on. Since it is a dynamic library, it is included via the Embed & Sign option. This was reported on SO by another user. They worked around it by making changes to the source package, I believe. That workaround may be difficult in my case as I do not control the source package. It's a 3rd party dependency that I'd prefer not to maintain a fork of. Any ideas of why Xcode cloud is hitting this issue or any other workarounds? I've confirmed via a codesign check that the Identifier is resolving to that special hash when doing this from Xcode Cloud. It does not have that hash when I attempt to build/archive/upload locally. $ codesig
2
0
1.2k
Oct ’22
Xcode Cloud & App Clips
Has anyone successfully used Xcode Cloud with App Clips. Every time I do a build I get an error from App Store Connect for Missing Entitlement. ITMS-90876: Missing entitlement - This app contains an app clip. The entitlement 'com.apple.developer.associated-appclip-app-identifiers' should be present and include the value of the app clip's application identifier. Xcode adds this automatically and an archive direct from Xcode works successfully. It seems that Xcode cloud is not automatically adding this entitlement which causes an error on submission.
7
0
1.9k
Oct ’22
Codesign and AppStore verification failure after manually lipo'ing two dylibs
We are creating a universal build of our application for the Mac App Store by merging separate x86_64 and arm64 bundles using a script. Codesign verification fails for some dylibs if they are signed after merging: % lipo -create x86_64/test.dylib arm64/test.dylib -o universal/test.dylib % codesign -s *** -f --timestamp universal/test.dylib % codesign --verify --verbose=2 universal/test.dylib test.dylib: invalid Info.plist (plist or signature have been modified) It seems verification fails for only those dylibs that have an Info.plist embedded in them. We were able to work around this issue by signing the individual dylibs before merging, but now AppStore verification is failing with the following error: ITMS-90336: Mismatched Embedded Info.plist: The executable 'test.dylib' has mismatched embedded Info.plists. This could be due to the use of 3rd party build tools. Does this mean that the __info_plist section in all the slices in the universal binary should be exactly the same (bitwise)? Some of these
3
0
1.9k
Oct ’22
ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match
I am trying to upload a new build of my app from the new Xcode 14.1 RC but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. My bundle contains a watchOS 4.3 app which I thought might have been an issue, so I tried increasing it to watchOS 7.0 but still got the error. Bitcode is disabled for all targets. I don't have post-processing enabled either.
12
0
4.6k
Oct ’22
ITMS-90338: Non-public API usage automatic refuse
Hello, The problem is we do not understand what the issue is even when reading your automatic message. Detail, before updating to version 14 it worked perfectly, so much so that it was deployed to the store. Today it works perfectly on the emulator and on the device, by xcode. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? Xcode: 14.0.1 macOS: Monterey Pro Chip M1 React Native: 0.69.5
3
0
415
Oct ’22
Reply to ITMS-90334 error when executing a Xcode Cloud TestFlight build
There is an issue with Ad-Hoc signing of dynamic libraries built either through a Swift Package, or through an Xcode target with a non-standard Bundle ID (i.e. one not using reverse DNS format), resulting in the ITMS-90334 error message. We'd appreciate getting reports of this filed through Feedback Assistant, and then posting the FB number here so that I can follow-up on the reports internally. Even if the following workaround information is helpful to you, we'd still appreciate getting the Feedback reports. The best practice for Swift packages is to not explicitly specify the LibraryType in the Product. By not specifying this value, you let Xcode decide the best linkage type for your app's usage of the package. If you have a package that is explicitly marked as dynamic, removing the library type means Xcode will link the package statically if the package is only imported by one target, which will avoid the issue. If the package is imported by more than one target, Xcode will choose dynamic linkage
Oct ’22
Reply to ERROR ITMS-90334: Invalid Code Signature Identifier. 
Me too, but a simple app using Swift Playgrounds on iPad. I sent a message to support about this describing what I was doing, and a copy of the error and got the response: “We're unable to determine the nature of your request. Please reply to this email with clarification”. This was the error I get back in email: ITMS-90334: Invalid Code Signature Identifier - The identifier 'Johnboxgame-numbers_and_letters_that_forums_thinks_are_offensive' in your code signature for 'Johnboxgame' must match its Bundle Identifier 'Johnboxgame' WIth the iPad app there’s not really much I can control as far as what goes in the bundle, and it’s worked in the past.
Oct ’22
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing
I have recently added some Swift files to my Objective C project that I had been successfully publishing to the AppStore. I'm able to debug on my devices and simulators but when submitting to AppStoreConnect I get the following email: Dear Developer, We identified one or more issues with a recent delivery for your app, ...... . Please correct the following issues, then upload again. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Best regards, The App Store Team From the internet I gather the following build settings are required for the project but that doesn't seem to help my case: 1. Defines Module -> YES 2. Always embed Swift Standard libraries -> YES To reproduce the problem, do the following: Create new Objective C project in XCode Add a single Swift file and choose YES when prompted to make the bridging header Set Defines Module and Always embed Swift Standard libraries to YES in buil
0
0
2.3k
Oct ’22
Swift Playgrounds for iPad: ITMS-90334: Invalid Code Signature Identifier
ITMS-90334: Invalid Code Signature Identifier - The identifier 'bundle id followed by 30 random characters' in your code signature for 'bundle id' must match its Bundle Identifier 'bundle id' Currently, any app I’ve tried is getting this error when submitting from the app. I’ve got all the places where you put the name, the sku, and bundle id set with the same value (copy/paste), and I’ve tried different variations, but now that long string of random characters is appended and I can’t use TestFlight. Maybe because this is a beta iPad OS? Been on a beta for what seems like forever. It’s worked in the past. Great. Totally innocuous post that has something that is not permitted. Be nice if you TELL me what’s NOT PERMITTED!
3
0
883
Oct ’22
How can I provide the application to iOS users in a country where the store (apple services) does not work?
I found several services that allow you to distribute applications to users(ios). diawi appsonair deployninja unicornlab but I think they all use Apple services in their work. this is from the documentation Diawi: How wireless app installation works on iOS Over-the-air installation of apps on iOS is based on tools and features provided officially by Apple: itms-service and a valid manifest file providing information on the app. but if apple services do not work in this country - how can I install the application? or is it not possible? maybe Enterprise account can help me with this? or is it not possible?
0
0
604
Oct ’22