Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

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.2k
Feb ’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
Getting ERROR ITMS-90345 when trying to submit to TestFlight
I'm build an iOS 15 app in Xcode 13 and whenever I try to submit to the App Store for TestFlight testing I get the following error: ERROR ITMS-90345: Metadata/Info.plist Mismatch. The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in xxxxx [Payload/xxxxx.app]. (App name removed because it doesn't matter) Based on some other forum answers, I doubled checked that there are no spaces in the bundle ID, and have tried repeatedly re-typing it, and copy and pasting it from an alternate version of the project that used to submit to TestFlight fine, but nothing has worked. Honestly, I have no idea where metadata.xml lives or how to even check what value is in it, which is part of the problem. Any advice or guidance here would be greatly appreciated, because I'm not sure what else I can do at this point, other than throwing everything away and starting over in Xcode 12 and iOS 14. Thanks!
3
0
3.1k
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
ERROR ITMS-90725 can't upload app with transporter
Hello everyone, I have been developing a game in UE4 and I would like to send my build to TestFlight. I'm working on a windows machine and remote build my project on a updated Mac book pro with Monterey and Xcode 13.1 I have no problem generating the development build and the shipping build on the windows side. However when I try to upload the .ipa using transporter I get this error message that suggest that the SDK used to compile is not the right one. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 13.2 SDK. All iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later. I should add that, in the past, I have been able to upload the game on iTunes connect. Any help would be greatly appreciate Best
1
0
755
Jan ’22
iOS 14 GM Inhouse apps disappear after install
When I install Inhouse apps on iOS 14, I see the progress view on the app icon both on the home screen and in the App Library. But when the installation is completed the app disappears and I can't even find it by searching. In the App Library there is a folder for enterprise apps, but it is empty. One time it showed up in search after some time. When I connect the phone to my Mac and open Devices and Simulators in Xcode I see that the app is installed under Installed apps. One of my colleagues sees the same on his device, but another colleague doesn't see it on his device. I've tried installing both with itms-services://?action=download-manifest&url=https:// and by dragging the .ipa file into Xcode's Devices and Simulators with the same result. I see that there have been problems with Inhouse apps in the iOS 14 betas (https://developer.apple.com/forums/thread/655207), but in my issue the app is installed, but disappears.
2
0
1.8k
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
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.4k
Jan ’22
ERROR ITMS-90045: "Invalid Code Signing Entitlements.
hola ! Tengo el siguiente problema al publicar en app store un archivo ipa ERROR ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/sul.iOS.app/sul.iOS' is not supported. ERROR ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleIdentifier' in 'Payload/sul.iOS.app/sul.iOS' is not supported. ERROR ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleName' in 'Payload/sul.iOS.app/sul.iOS' is not supported. ERROR ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleS
1
0
810
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
Jan ’22
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
Reply to Log4j XCode vulnerability - resolution eta?
Xcode does include a Java runtime environment - the App Store upload has always used Java tooling in its delivery mechanism and ships a Java Runtime Environment: % /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/bin/java -version openjdk version 14.0.2 2020-07-14 OpenJDK Runtime Environment 14.0.2-5906ce1373 (build 14.0.2+12-iTunesOpenJDK-8) OpenJDK 64-Bit Server VM 14.0.2-5906ce1373 (build 14.0.2+12-iTunesOpenJDK-8, mixed mode
Dec ’21
Info.plist file is missing for PassKit.framework
I am getting this issue on my apple developer mail. We identified one or more issues with a recent delivery for your app, 6.6 (6.7). Please correct the following issues, then upload again. ITMS-90036: This bundle is invalid - The Info.plist file for PassKit.framework is missing or could not be read. My app is running fine in debug mode and also it's archiving fine too.
2
0
2.1k
Dec ’21