How I can I have both versions of the app installed on the same phone? 1 for testing and 1 that’s live to see current version users are using?
I had this setup before but now TestFlight installs replace the live version instead of the test version.
TestFlight
RSS for tagTestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.
Posts under TestFlight tag
83 Posts
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello,
i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere.
so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device.
however when I try to archive and sent to Testflight/AppStore, I get:
ITMS-90426: Invalid Swift Support
and when I try to followup guides to create it manualy, copying libs from:
$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)
plese here note, that ALL guides indicate to use folder "swift", however there are no *.dylib files... they are only in "swift-5.0" folder
then I receive an error type:
ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftSceneKit.dylib, libswiftCoreData.dylib, libswiftGameplayKit.dylib, libswiftUIKit.dylib, libswiftMetalKit.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftModelIO.dylib, libswiftWatchKit.dylib, libswiftDarwin.dylib, libswiftARKit.dylib, libswiftAssetsLibrary.dylib, libswiftSpriteKit.dylib, libswiftNaturalLanguage.dylib, libswiftCoreAudio.dylib, libswiftIntents.dylib, libswiftQuartzCore.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftVision.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftGLKit.dylib, libswiftSwiftOnoneSupport.dylib, libswiftXCTest.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/Filmtoro.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.
here please also note that actually *.xcarchive does not contain any "Payload" folder, the package contains only two folders "dSYMs" and "Production/Applications/myapp.app" (inside it I can find "Frameworks" folder...
this link was also very interested:
https://indiestack.com/2017/03/implicit-swift-dependencies/
tho id didnt help a bit :)
so what I would like to know, is what actually forces xcode to generate the SwiftSupport folder to the archive... the must be some direct setting inside *.xcodeproj/pbxproj which forces it... or dirrect setting in xcode/Build Settings which if not work I can submit an ticket to investigate.
I am sure after a month of trying everything, whatever tip you can point out I already tried, however Please lets try everything again to get bottom of this.
Many thanks for any tip
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode
Swift Packages
TestFlight
Objective-C Runtime
I'm having an issue with an app installation on my iPhone where it keeps installing the latest TestFlight version instead of the public App Store version. Here are the details:
I initially installed version 1.24 of the app via TestFlight.
I then uninstalled both the app and TestFlight and tried to reinstall the app from the App Store, which should be version 1.6 (the current public release).
Despite this, the App Store keeps installing version 1.24, which is the TestFlight version.
Here’s what I’ve tried so far:
Uninstalled both the app and TestFlight.
Restarted the iPhone to clear any cached data.
Tried offloading and reinstalling the App Store app through Settings to clear its cache.
Reinstalled only the App Store version, but the device still downloads the TestFlight release.
Has anyone experienced this before? Are there additional steps I can take to reset the association to the App Store version? Any insights would be greatly appreciated. Thank you!
I’m encountering a problem with my iOS app with new Live Caller ID extension when uploading to TestFlight. Here’s what's happening:
When I try to upload the app to TestFlight without the NSExtensionPrincipalClass, I get the following error:
Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found in extension Info.plist for foo.app/PlugIns/bar.appex
However, if I include the NSExtensionPrincipalClass in the Info.plist of my extension, the app fails to launch on both the dev build and through TestFlight. The error message I receive is:
bar.appex with id <bundle_id> defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.live-lookup
Has anyone experienced a similar issue? How to fix it?
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Extensions
iOS
SMS and Call Reporting
TestFlight
I'm currently experiencing the same problem that many have had with error 422 "Beta contract is missing."
I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem.
I get the message "There was an error processing your request. Please try again later."
And when I inspect with Safari it shows me this information:
"errors" : [ {
"id" : "9be0314c-3bd5-4143-a625-602322d7156e",
"status" : "422",
"code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING",
"title" : "Beta contract is missing for the app.",
"detail" : "Beta Contract is missing."
} ]
This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error
"The requested app is not available or doesn't exist."
Could someone tell me what process I should follow or where I can correctly generate the ticket for my error? Since the Apple support page does not load.
Thanks!
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Developer Tools
App Store Connect
TestFlight
Issue Submitting Builds for Beta Review - "Beta Contract is Missing"
We are currently facing an issue in Testflight when trying to submit new builds for review for external Beta testing. Each time we attempt to submit a build in the "What to Test" dialog, we receive the following error message:
"There was an error processing your request. Please try again later."
Upon inspecting the browser response when clicking "Submit for Review" in the "What to Test" dialog, we found the following details:
code: "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING" detail: "Beta Contract is missing." id: "4ed15cb2-2732-4100-a660-0899dcb0e25a" status: "422" title: "Beta contract is missing for the app."
However, after checking the Developer Console, we are unable to locate any missing information or steps that need to be addressed.
We would greatly appreciate your assistance in resolving this issue as soon as possible, as we are currently unable to push any new builds for testing.
What we’re currently trying to do:
Contact Apple Developer Support (no response for about 2 weeks)
Create a new app bundle
Build on a different machine/Mac
Rebuild a previous version of the game that worked before
Create a new app on another account (it worked, but the build was rejected—THANK YOU FOR NOTHING—because it’s considered a copy of our own game)
We need to test before release, and we’re now three weeks behind our plans!
Problem: One of my QA Device crash while launch the iOS 15.5.
Background: Previously, I update my os to macOS Sequoia & update my Xcode to 16 Release Candidate. Previously when the app was build in Xcode 15.4, it run/launch perfectly, but it seems the app is crash below iOS 15.5
---- HERE THE CRASH LOG ------
Incident Identifier: 6E80706A-C8FA-4E6F-8F14-5746E6CA5129
Hardware Model: iPhone13,3
Process: Runner [79635]
Path: /private/var/containers/Bundle/Application/ED368AA9-3A69-45CE-89CA-438440BB8781/Runner.app/Runner
Identifier: -
Version: 1.0.7 (3273)
AppStoreTools: 16B39
AppVariant: 1:iPhone13,3:15
Beta: YES
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: - [872]
Date/Time: 2024-10-29 08:56:13.5458 +0700
Launch Time: 2024-10-29 08:56:13.4479 +0700
OS Version: iPhone OS 15.5 (19F77)
Release Type: User
Baseband Version: 2.54.02
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD 4 Symbol missing
Symbol not found: _objc_claimAutoreleasedReturnValue
Referenced from: /Volumes/VOLUME/*/Runner.app/Frameworks/KSCrashCore.framework/KSCrashCore
Expected in: /usr/lib/libobjc.A.dylib
(terminated at launch; ignore backtrace)
Triggered by Thread: 0
Thread 0 Crashed:
0 dyld 0x00000001025007a0 __abort_with_payload + 8 (:-1)
1 dyld 0x0000000102506388 abort_with_payload_wrapper_internal + 104 (terminate_with_reason.c:102)
2 dyld 0x00000001025063bc abort_with_payload + 16 (terminate_with_reason.c:124)
3 dyld 0x00000001024d6828 dyld4::halt(char const*) + 328 (DyldProcessConfig.cpp:2067)
4 dyld 0x00000001024d3960 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3560 (dyldMain.cpp:0)
5 dyld 0x00000001024d1cc4 start + 488 (dyldMain.cpp:864)
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000006 x1: 0x0000000000000004 x2: 0x000000016eee1690 x3: 0x00000000000000d8
x4: 0x000000016eee1290 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000016eee0cd0
x8: 0x0000000000000020 x9: 0x0000000000000009 x10: 0x0000000000000001 x11: 0x000000000000000a
x12: 0x0000000000000000 x13: 0x0000000000000037 x14: 0x00000002301c9625 x15: 0x0000000000000002
x16: 0x0000000000000209 x17: 0x00000001024fae54 x18: 0x0000000000000000 x19: 0x0000000000000000
x20: 0x000000016eee1290 x21: 0x00000000000000d8 x22: 0x000000016eee1690 x23: 0x0000000000000004
x24: 0x0000000000000006 x25: 0x000000016eee3728 x26: 0x0000000000000001 x27: 0x000000016eee3590
x28: 0x0000000000000000 fp: 0x000000016eee1260 lr: 0x0000000102506388
sp: 0x000000016eee1220 pc: 0x00000001025007a0 cpsr: 0x1000
esr: 0x56000080 Address size fault
Binary Images:
0x1024b8000 - 0x10250ffff dyld arm64e <7c9c7851823738a7b1eb9cd2deb4b746> /usr/lib/dyld
EOF
For my app Find Any File, of which both releases and TestFlight betas were released many times, the TestFlight page tells me that several users have submitted crash reports. And I'm sure the same is true for the MAS releases:
(Yes, this shows quite recent ones, but I've seen similar supposed crash report submits in this list before.)
However, the actual "Crashes" listing on the appstoreconnect sites hasn't show any new crash reports for many months now:
(This is the entirety of crash reports I can get listed, even when removing all filters.)
Something appears to be stuck, on Apple's end.
The same issue is with Xcode's Organanizer window, for "Crashes": It also used to list only the same very old reports and nothing since May 2024. And just now, when I retried this in Xcode, I'm shown a weird error message I never saw before:
Error Downloading Crashes List
An error occurred… Access Restricted with adam id: 1207815783
And yes, I'm logged in just fine, under Prefs / Accounts.
How am I going to get this investigated? I had already sent an email about this to the Review team, who didn't react to it at all. DTS is only for Code level support, which this isn't.
Any help?
Sir/Maam, I want to tell you to personally meet me at Apple Saket Citywalk Mall, as I am from India Uttar Pradesh Noida or my nearest Apple authorized store is in Saket. Your request is, please meet me. In Delhi Apple store, please provide it to me in person because I want to explain my iOS app or share its features or I want to sell my app to apple developers....
Thank you team!!
Yours faithfully
Akansha
In this case, I used my project project to export the ipa to testflght. The tester installed the app on the test device, started the app, and received the payment voucher information pushed by storekit. At this time, the test device did not log in to the sandbox account. Of course, The test device has previously logged into the sandbox account and successfully paid for the subscription. When I used the same test device, connected to Xcode, clicked run, and ran the app, I did not receive the payment voucher information pushed by storekit. I am very confused, why does testflight receive the certificate information pushed by storekit?
I am using an iPhone 14, with IOS 18 on a managed account and keep getting "Temporarily Unavailable" error when trying to launch TestFlight. This app worked on another organization managed device (same device, IOS) but several others are giving temp unavailable errors. Can anyone help guide me on how to fix this error? I have tried uninstalling, restarting, reinstalling several times with no luck.
Can someone tell me how to fix the TestFlight “temporarily unavailable” error? I am using an iPhone 14 with IOS 18 and the device is under an organized managed account TestFlight works on another phone on the same account but gives error on others.
Hi,
I have an error while uploading to test flight by fastlane and transporter.
07:13:05 [Transporter Error Output]: Return status of iTunes Transporter was 1: ERROR ITMS-90165: Invalid provisioning profile signature. The provisioning profile included in the com.test.example bundle [“Payload/Example.app”] can't be used to upload apps to App Store Connect until it has a valid signature from Apple.
My xcode version is 15.4 and the iTMSTransporter is 3.3.0.
It seems like this error has been reported the other internet recently.
https://stackoverflow.com/questions/79118087/getting-error-invalid-provisioning-profile-signature-in-transporter-while-ios-ap
https://www.yunedit.com/article/error90165
Has anyone solved this?
Hi guys, I’m writing an app that integrates Screen Time API more specifically one that has only DeviceActivityReport.
The app runs as expected but I have an issue when pushing it to AppStoreConnect:
Provisioning profile failed qualification: Profile doesn't support Family Controls (Development).
Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.family-controls entitlement.
Provisioning profile failed qualification: Profile doesn't support Family Controls (Development).
Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.family-controls entitlement.
My app has Family Controls (Development) set in Capabilities, entitlement file, provisioning profile and distribution certificates.
I have already requested Apple for the entitlement key for Family Controls (I’m waiting for them to reply).
So, I have few questions now:
Can I distribute a build for internal testers via TestFlight without waiting for Apple’s reply to my request?
Do I need to wait Apple’s reply to distribute the app to internal tester under Family Controls (Development) ?
Has anybody had the same issue and solved it without waiting for Apple to approve the request during development (no distribution)?
I have done a deep search about this topic but it is still not clear to me if an internal build could be distributed under Family Controls (Development) or if it is mandatory to wait for the distribution one
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Entitlements
TestFlight
Family Controls
Unable to upload new ipa builds to TestFlight since today
Same scenario described here:
https://forums.developer.apple.com/forums/thread/738942
User clicked accept for an internal tester invitation sent to their work apple id on their personal device which was signed in with their personal apple id.
This seems to have redeemed the code to the users personal account. However, the user has removed themselves from testing the app and we're trying to get their work apple id registered but the invite code that keeps being sent is coming back saying invalid.
Things we've tried:
We located the last build the user installed on their device and expired the builds
deleted / readded the work apple id to internal testing group
It's still sending the same invitation code from TestFlight and saying that the code cannot be redeemed.
What happens after 12 renewals? Does the subscription expire completely? The next day when I try to manage settings for my sandbox account it says it cannot connect.
I cannot see the status of subscription in:
Settings-> App Store -> Sandbox Account -> Manage
Logging out and logging in of my regular account does not fix that.
When I login with a different non-testflight sandbox account I can finally edit those settings. There are some missing details in documentation explaining testflight sandbox accounts. Do these accounts stop working after 12 auto-renewals? I need more specific details in order to ensure subscriptions will work properly during production.
We are trying to upload iOS app in Test Flight.
The iOS SDK version we are using is 18 and Xcode Version is 16.
While uploading the app (we are using Jenkins & Fastlane), we are getting an error saying the app is built with iOS SDK 16.4. Due to that we the upload is failing.
The error text says
An error occurred during the build: Error uploading ipa file:
[Application Loader Error Output]: [ContentDelivery.UploadError c0000171810C] Asset validation failed (90725) SDK version issue. This app was built with the iOS 16.4 SDK. All iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. (ID: 671ae668-d311-43de-b85c-1d142f6a8fbd) [Application Loader Error Output]: Error uploading '/var/folders/qq/2qkbtw5s7657 5cmd3kq0kmwh80gm7/T/73c3d853-ddb3-48b6-a78f-
bfbb979afbb.ipa'. [Application Loader Error Output]: Asset validation failed SDK version issue. This app was built with the iOS 16.4 SDK. All iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. (ID: 671ae668-d311-43de-b85c-1d142f6a8fbd) (90725)
[Application Loader Error Output]: The call to the altool completed with a non-zero exit status: 1. This indicates a failure."
Hello,
We haven't been getting crash logs for internal TestFlight builds.
I've tried intentionally causing a crash by calling fatalError() directly. The TestFlight feedback dialog appears and crash logs appear on the iPhone device itself, but they never appear in App Store Connect or Xcode Organizer.
The builds are all created by an Xcode cloud workflow and the Share analytics with App Developers setting is on.
I filed a radar ticket at FB15453505, but I wonder if others might have run into the same thing.
Has anyone else had this issue and figured out how to resolve it?
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
iOS
App Store Connect
Debugging
TestFlight
Hi,
I run a midsize business. Apple recommends for company owned devices and for other reasons to use Apple Business managed Apple IDs for the employees. After that, you have to use a MDM System for e.g. deploying apps and licenses.
Testflight is an app that can be deployed too. But....Testflight can not more than to say "Hello" on a managed device. The use of Testflight and to test our developed apps is not possible with a managed ID.
Can anyone explain to me this thinking or what is recommended than. Setting up a private Apple ID for that purpose...which on the other hand, Apple do not want or does not recommend.
Topic:
Business & Education
SubTopic:
General
Tags:
Sign in with Apple
TestFlight
Business and Enterprise
Managed Settings