Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Arcade Options Entitlements for TestFlight Deployment
We're attempting to build and distribute our MacOS game via TestFlight and are met with an error or multiple errors regarding com.apple.developer.arcade-operations. Either we exclude the entry from our entitlements file used to sign and get this single error: ITMS-90769: Invalid Bundle - Apple Arcade apps require the 'com.apple.developer.arcade-operations' entitlement. Or we add it to the entitlements and get this error: ITMS-90287: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.arcade-operations' in 'com.[CompanyIdentifier.GameName].pkg/Payload/[GameName].app/Contents/MacOS/[GameName]'. We're unsure of how to properly include the key'' in the provisioning profile. There are no options to do such a thing on the developer.apple website where they're created/editable and I can't just add it to t
3
0
3.2k
Jan ’22
Build the .pkg file without Xcode and verify it with the Transporter app. An error occurred after adding Scripts
Hi there, I encounter a problem when submitting software to App Store and have tried to solve it for several days. My attempt on this didn’t work out, so I would like to post my question here and discuss with anyone who might know the solution. I write this macOS app with Python and build a “.pkg” file, without using Xcode, and use Transporter app to verify. I successfully build the “.pkg” file which can pass Transporter app’s verification after some time of researching. Everything seems to be good. Then I add the scripts to the “.pkg” file and test the process of installation in my computer. Everything seems to be good. Below is my command: pkgbuild --scripts mac/build_pkg_scripts --install-location /Applications --component my.app my.pkg productbuild --synthesize --package my.pkg /Application ./dist.xml productbuild --distribution dist.xml --package-path ./my.pkg ./my_final.pkg However, an error message appears when the “.pkg” file verified by Transporter App: ERROR ITMS-90254: The product archive
0
0
1.1k
Jan ’22
Invalid Binary After Upload
Hello. Please let me preface my question with this: I am new to IOS development, XCode and Mac computers, in general. So, apologies if my question sounds uniformed. I have built a prototype game, which I would like to put on the App Store, so that my friends and partners can test. I only want this available via the internet, so that they can access the app and test, internally. It is not ready to go into production. I build the app in Unity and ported to Xcode. I build the applications Archive and follow the process to upload it. I receive no errors. But, after I upload the application, and it finishes processing, the status (under iOS Builds) is Invalid Binary. I also received an email that said: ITMS-90562: Invalid Bundle - The app cannot be processed because options not allowed to be embedded in bitcode are detected in the submission. It is likely that you are not building the app with the toolchain provided in Xcode. Rebuild your entire app with the latest GM Xcode and submit the app again. How c
1
0
2.1k
Jan ’22
.ipa resign issue during App Store Connect
Hi all, I am facing an error when I try to upload my resigned .ipa file to the App Store. Basically what we want to achieve is that we get an unsigned .ipa file from an external company (we don't own the source code for this app), and we want to distribute that with our company developer account. (as a private app) We already have a Developer Account, I registered the App, Bundle Id, created certificate, App Store provisioning profile etc. And with these I resigned the .ipa file. But when I try to upload to the App Store (via altool command) I have the following error: parameter ErrorMessage = ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '***.com.company.myappname' for key 'application-identifier' in 'Payload/FSARN.app/Frameworks/FMDB.framework/FMDB' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle ide
0
0
1k
Jan ’22
Xcode cloud and multiple bundle ids?
Is it possible to set up Xcode Cloud so it distributes the app to different bundle id? (for example, mock, test and release environment) Right at the moment we are only limited to deploy TestFlight for the bundle ID that configured Xcode Cloud? I would really like to be able automate several different build with different bundle id's... When i try to archive using Xcode Cloud to a different bundle id that the one configuring Xcode Cloud i get the following errors: ITMS-90054: This bundle is is invalid. ITMS-90345: Metadata.Info.plist Mismatch. When I archive manually it works perfectly fine.
6
0
3.6k
Jan ’22
Invalid Code Signing Entitlements - com.apple.application-identifier
Our app uploads successfully, but then I get the following message in an email from App Store Connect about an Invalid Code Signing Entitlements: ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value 'BFZC26JH2W.humansarehuman.blue2factor.macosbackground' for key 'com.apple.application-identifier' in 'Blue2Factor.app/Contents/Library/LoginItems/Blue2FactorBackground.app/Contents/MacOS/Blue2FactorBackground' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The value for the key mentioned, BFZC26JH2W.humansarehuman.blue2factor.macosbackground, IS our TEAMID, followed by a dot, followed by the bundle identifier. The bundle is a target in our project, though it is not only target, and it is not the bundle ID that is identified as the BundleID on the App Store Connect - App Information page under the Gener
1
0
970
Jan ’22
Reply to App can't start because of broken/unverifiable dylib
Ok, I found something new in the Console. exec of /Applications/***.app/Contents/Resources/jre/bin/java denied since it was quarantined by Hexx20Fiend and not approved by Gatekeeper, qtn-flags was 0x00000082 I have a feeling what this means. Originally when uploading my app to the App Store I got this error: ITMS-90511: CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value 'net.java.openjdk.cmd' of 'java' is already in use by another application. I searched around a bit and found that I should replace the CFBundleIdentifier in the java binary with a hex editor. I changed it to something unique under my domain with the same length as net.java.openjdk.cmd. I used Hex Fiend to do that, and apparently that has marked the binary as quarantined. I did not notice that, and the App Store also did not notify me of that. I now used xattr -d com.apple.quarantine to remove the quarantine tag. I am currently uploading the App again to see if that solved the issue.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’22
Reply to Log4j XCode vulnerability - resolution eta?
Krampus gave us another log4j remote code execution vulnerability (CVE-2021-44832), with the patch coming about 10 days after XCode 13.2.1 was released. XCode might be vulnerable; it's 13.2.1 release notes don't mention patching this newer vulnerability. I'm with donmontalvo and wish XCode would excludes all log4j versions less than 2.17.1. When I scan my system with CloudStrike's CAST tool, XCode pops in a big way. If XCode could upgrade /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/share/OSGi-Bundles/org.apache.logging.log4j.core-2.11.2.jar to a secure version, my company would be much less worried.
Jan ’22
ITMS-90430: Invalid Swift Support - React Native
Hi, community, when I build my project I have the same reject from App Store: ITMS-90430: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have a signing ID. Sign the file, rebuild your app using the current public (GM) version of Xcode, and resubmit it I follow a procedure before the build, but this works one time on X times... cleanup pods - cd ios & pod deintegrate & pod update cleanup Xcode derived data - rm -rf ~/Library/Developer/Xcode/DerivedData/* clean build folder Product->Clean Build Folder in Xcode Specs below: OSX: big sure 11.4 XCode: 13.2.1 Libs: native-base: ^2.15.2, npm: ^7.10.0, react: 17.0.1, react-native: 0.64.1, react-redux: ^7.2.4, redux: ^4.1.0, rxjs: ^6.6.7, @types/react-native: ^0.64.0, typescript: ^3.8.3 This bothers me ... I waste hours on builds. Regards AA
2
0
1.5k
Jan ’22
postinstall is not called
I have developed MacOS App and tried to make installer which has postinstall by productbuild. productbuild --component App/App.app /Applications --scripts ./Scripts --sign 3rd Party Mac Developer Installer: MyCompany (******) App.pkg Scripts directory has postinstall. -rwxr-xr-x@ 1 name staff 171 1 7 11:36 postinstall* I can install App.app under /Applications. But postinstall is not called. App.pkg is validated by Transporter. I tried to use pkgbuild. pkgbuild --root ./App --identifier com.mycompany.App --version 1.0 --install-location /Applications --scripts ./Scripts --ownership preserve App.pkg productbuild --synthesize --package App.pkg Distribution.xml productbuild --distribution Distribution.xml --sign 3rd Party Mac Developer Installer: MyCompany (******) --package-path . AppInstaller.pkg This dose work well, postinstall is called. But AppInstaller.pkg is not validated by Transporter with following errors. What should I do ??? ERROR ITMS-90230: Invalid product archive metadata. Error in keyPat
0
0
1.4k
Jan ’22
Qualify Mac Build for TestFlight
I want to upload a MacOS App to App Store Connect and have it be available to test in TestFlight. I have already managed to sign the application as needed, as I can upload builds. The problem is, that they get marked as Not Available for Testing. At first App Store Connect notified me of this issue: ITMS-90889: 'Cannot be used with TestFlight because the bundle at “RougeLike.app” is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight.' I added a provisioning profile to the app bundle at Contents/embedded.provisionprofile. Now I don't get this notification anymore, but the app still is marked as Not Available for Testing. Does anybody know how to solve that?
1
0
1.3k
Jan ’22
About handling in-app purchase `paymentQueue(_:shouldAddStorePayment:for:)` from the App Store for Subscription Offer Code
Hi, I was wondering could we tell the difference if a user is redeemed among Subscription Offer Codes and the others two types of Offers (Introductory Offers, Promotional Offers) when receiving shouldAddStorePayment callback? I didn't see there is a SKProductDiscount.Type for it. https://developer.apple.com/documentation/storekit/skproductdiscount/type When a user redeem offer code by typing manually in AppStore App or via itms-apps://buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/freeProductCodeWizard?code=YOUR_CODE URL , I think we could expect that there should be a paymentQueue(_:shouldAddStorePayment:for:) to inform SKPaymentTransactionObserver about the event according to the document. https://developer.apple.com/documentation/storekit/skpaymenttransactionobserver/2877502-paymentqueue If your app is not yet installed when the user starts the in-app purchase in the App Store, the user gets a notification when the app installation is complete. This method is called when the user taps the notifi
0
0
578
Jan ’22
Missing Purpose String in Info.plist but plist contains everything AppStore needs
I got next error: ERROR ITMS-90683: Missing Purpose String in Info.plist. Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSHealthShareUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. 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. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy). But it's just a new build of a project and Info.plist seems to be ok (nobody has changed it):
2
0
2.6k
Dec ’21
ITMS-90429: Invalid Swift Support
Hi, I am unable to upload my app with mac book pro (13 inch ,M1) , Xcode 13.2.1 (13C100), swift 5, and cocoapods-1.10.1 version, receiving following mail from App Store connect after 10 mins of upload to TestFlight or AppStore. Error : We identified one or more issues with a recent delivery for your app, MyApp 1.4.6 (89). Please correct the following issues, then upload again. ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswift_Concurrency.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftMediaPlayer.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/MyApp.app
1
0
1.1k
Dec ’21
Reply to xcodebuild proxy settings
In the latest version of Xcode, you can simply edit the file /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/conf/net.properties accordingly. After changing the following line (which is set to false by default), notarization was able to connect from behind out proxy server. java.net.useSystemProxies=true
Dec ’21