I have two platform for my IOS app, tvOS and IOS , i created group by Manual Distribution in TestFlight, and added testers and build, But i see No Builds Available status in my tester account, and invitation also does not send

Seems that recent TestFlight update (3.8.0) is broken on iOS 14.1. It crashes on launch. It worked fine on the same device just few days ago (I assumed it was 3.7.1). I uninstalled the TF and installed it again but it doesn't help. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0 Attached is the crash report. I would appreciate if you guys can quickly fix it, or provide a solution. Thank you. Crash report

ola muito boa noite, tenho um app que estou testando, coloquei no grupo interno e tudo bem, porem o grupo externo, não aparece disponível para que eu possa vincular a minha versão, assim não consigo disponibilizar para testadores externos, podem me ajudar? Atenciosamente, Denis Fernandes

I'm developing a React Native app using Expo, and I'm encountering crashes on iOS devices. The app is deployed via TestFlight and is also being tested on a physical iPhone. However, I'm struggling to interpret the iOS crash logs and pinpoint the root cause of the crashes. Issue: -The app runs fine in development mode. -On TestFlight and physical devices, it sometimes crashes without clear error messages in the Expo logs -Having difficulty reading the error logs Errors: COSMCtrl applyPolicyDelta unexpected absence of policy on appRecord com.xxxxx.xxxx bg time + grace BBRemoteDataProvider: <BBDataProviderIdentity 0x300534a00; com.xxxxx.xxxx> does not respond to noteSectionInfoDidChange: Advisor: No handle found for currently focused PID: 72765; sceneIdentity: com.apple.frontboard.systemappservices/FBSceneManager:sceneID%3Acom.xxxxx.xxxxapp-default [<_UIKeyboardArbiterClientHandle: 0x30111f8e0; [app<com.xxxxx.xxxx(9BD12DED-F3C3-4C92-82E5-0810D8796F6F)>:72765] <<UIKBArbiterClientFocusContext: 0x302fe1be0; contextID = 6ae54085; sceneIdentity = com.apple.frontboard.systemappservices/FBSceneManager:sceneID%3Acom.xxxxx.xxxx-default >>; hosting PIDs {( )}; level 0.000000; active NO [wants NO]; suppression 0; iav 0.000000; on screen NO; isAcquiringFocus: YES>] Acquiring focus timer elapsed, clearing acquiring focus state What I've Tried: -Checked Expo & React Native logs (npx expo start --clear). -Enabled Debug Mode on a physical iPhone (device logs via Console.app). -Reviewed Crash Logs in EAS. -Checked Apple Developer Logs. -Looked into App State Changes (AppState.addEventListener) since crashes sometimes happen when the app moves to the background. Questions: -How can I properly decode iOS crash logs to identify the cause? -Are there specific Expo or React Native debugging tools for analyzing iOS crashes? -Are there common issues with background execution policies that might cause this in React Native? Tech Stack: React Native: 0.72+ Expo SDK: 49+ State Management: Context API + SQLite local storage Auth: SecureStore + JWT + API authentication Notifications: Expo Notifications API Backend: Node.js / Express (hosted on Heroku) Build System: EAS Build for iOS (Managed Workflow) iPhone Model: iPhone 13 (physical device)

So I submitted my app for TestFlight external testing and got this email: ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns. But here's the thing: everything this says is 100% bogus. My app uses no libraries and no push notification service registration APIs. The term register is used in my app, because I use table view cell registrations. Could that be the cause of this bogus warning?

On the developer portal , I have a mention of 13 feedback for my app in test. On the portal I have only access to 2 of them, the same in Xcode Organizer for the same version of course. This is important for us to have feedback from users betatesting our apps.

Hi, I’m experiencing an issue where my React Native (Expo) app crashes immediately in TestFlight after launching, but it works fine in Expo Go and the iOS Simulator. This is my first time building an IOS app, so I'm not sure where I'm going wrong. Are there known issues with JS bundle loading, native module compatibility, or API entitlements that could be causing this? What tools or logs should I use to track the exact source of failure? Any guidance would be greatly appreciated! Thank you. Steps Taken: The app runs fine in Expo Go (npx expo start --no-dev --minify) and in the iOS Simulator (npx expo run:ios --clean). I also did (npx expo-doctor) and it passed all 15 checks. After building with EAS (eas build --platform ios --profile production), the TestFlight build crashes on launch. I checked Xcode logs (Devices & Simulators > View Device Logs) and found this error: `Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: LoungeNavigator [4666] Triggered by Thread: 6 Thread 6 name: Thread 6 Crashed: Thread 6 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 My app.json file: "expo": { "name": "appname", "slug": "app", "owner": "baint", "version": "0.5.2", "orientation": "portrait", "icon": "./assets/images/IOS-App-Icon.png", "scheme": "myapp", "userInterfaceStyle": "automatic", "newArchEnabled": true, "ios": { "supportsTablet": true, "bundleIdentifier": "bundleIdentifier", "icon": "./assets/images/IOS-App-Icon.png", "buildNumber": "7", "infoPlist": { "NSLocationAlwaysAndWhenInUseUsageDescription": "This app requires access to your location at all times.", "NSLocationAlwaysUsageDescription": "This app needs your location even when the app is in the background.", "NSLocationWhenInUseUsageDescription": "We need your location.", "ITSAppUsesNonExemptEncryption": false } }, "android": { "adaptiveIcon": { "foregroundImage": "./assets/images/IOS-App-Icon.png", "backgroundColor": "#ffffff" }, "package": "identifier" }, "web": { "bundler": "metro", "output": "static", "favicon": "./assets/images/favicon.png" }, "plugins": [ "expo-router", [ "expo-splash-screen", { "image": "./assets/images/IOS-App-Icon.png", "imageWidth": 200, "resizeMode": "contain", "backgroundColor": "#ffffff" } ], "expo-asset", [ "@rnmapbox/maps", { "RNMapboxMapsImpl": "mapbox", "ios": { "RNMapboxMapsDownloadToken": "token", "RNMapboxMapsAccessToken": "token", "NSLocationAlwaysAndWhenInUseUsageDescription": "This app requires access to your location at all times.", "NSLocationAlwaysUsageDescription": "This app needs your location even when the app is in the background.", "NSLocationWhenInUseUsageDescription": "We need your location." } } ], [ "expo-build-properties", { "ios": { "useFrameworks": "static", "useModularHeaders": true } } ] ], "experiments": { "typedRoutes": true }, "extra": { "router": { "origin": false }, "eas": { "projectId": "projectid" } } } } My eas.json file: "cli": { "version": ">= 14.7.1", "appVersionSource": "remote" }, "build": { "development": { "developmentClient": true, "distribution": "internal" }, "preview": { "distribution": "internal" }, "internal": { "distribution": "store", "ios": { "credentialsSource": "remote" }, "autoIncrement": true, "env": { "EXPO_PUBLIC_NODE_ENV": "production" } }, "production": { "autoIncrement": true, "distribution": "store", "env": { "EXPO_PUBLIC_NODE_ENV": "production" } } }, "submit": { "production": { "ios": { "ascAppId": "ascAppId", "appleId": "appleId", "ascApiKeyPath": "ascApiKeyPath" } } } }

I have an app currently in beta testing, and my primary QA person tries to send the crash log for this one particular bug: The night before, he finished testing the app on an iPhone, left the app running in the background and the phone charging. The phone went to sleep. The phone is running the latest release of iOS 18. In the morning he wakes up the phone and gets the alert that the app "*** Crashed. Do you want to share additional information with the developer?" He taps Share, but I don't get a crash log in the organizer. I've gotten other crash logs in the organizer as recently as 2 weeks ago, This one has occurred several times and always fails to produce a report. I have tried doing the same steps without seeing any crash. Any ideas? Mike

Lately I have been having a lot of issues with TestFlight and uploading new builds for a project I am playing around with: issues are wide ranging. Going straight from "Waiting" to processing without having to setup the encryption or French distribution. Once the above is setup the new builds do not appear as being downloadable, so I cannot test changes in the App. New builds taking hours (Vs minutes) to appear as an Update in TestFlight Has anyone else been running into these problems? Thanks Jason

Our test application has the status "Approved" on the test build list view. However, when adding testers to the test build, the process failed with the error message "An error has occurred. Try again later." **Here is the API request: ** https://appstoreconnect.apple.com/iris/v1/builds/d9bc89fa-e94d-4a33-a39c-20550c0673ec/relationships/individualTesters Here is the response: { "errors" : [ { "id" : "5b833be8-18d1-4ce9-b47d-7a315ef49a50", "status" : "409", "code" : "STATE_ERROR", "title" : "The request cannot be fulfilled because of the state of another resource.", "detail" : "Tester(s) cannot be assigned" } ] } Does anyone experience the same issue? Any insight on the root cause? I am wondering if this could be fixed by itself. Any input and help is appreciated.

My app is deployed my internal testers. It is being tested on iPhone 16, iPad (M4) and iPad(older), and VisionPro. All of these continue to work in the simulators. I get the crash on all devices except the iPad(m4). The only notable change in the latest build is Mac support. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$s7SwiftUI23_GeometryActionModifierV5valueyxAA0C5ProxyVYbcvi crashlog.crash

I'm having trouble launching TestFlight on my iPhone 15. As soon as I open the app, I see the welcome screen, but then I immediately get the following error message: TestFlight Unavailable TestFlight is temporarily unavailable. Try again. I can't proceed further – after tapping "OK," the message disappears, but TestFlight remains unusable. I've tried: Restarting my iPhone Uninstalling and reinstalling TestFlight Checking my internet connection (both Wi-Fi and LTE) Signing out and back into my Apple ID The issue persists. Is anyone else experiencing this? Is this a known issue on Apple's end? Attaching a screenshot for reference. Device: iPhone 15 iOs: 18 Any help would be appreciated!

A few days ago I migrated my purchases from my secondary AppleID to my primary. One of the requirements was to stop testing apps in Testflight. I stopped testing in the app as directed. After the migration I am not able to rejoin my testing app. It says it is connected to my secondary ID and I need to sign in with it. The whole point of migration was to not have two IDs for iCloud and Media and Purchases. I have no intention of signing in with my other ID, it's impractical. How can I get TestFlight to relinquish the secondary ID? Developer sent a new invitation but to no avail. Deleted app and data, reinstalled, to no avail.

Hi everyone, I built a new app and pushed it to the Testflight but call/sms is not working. Doesn't Testflight support call/sms feature?

I see the app in TestFlight. I press install, after a while the circular icon appears fills for a while and then stops and goes right back to install. How can I install an Apple Watch only app from TestFlight? I have restarted both iPhone and watch. Same thing.

TestFlight has suddenly stopped distributing new builds to internal testers. I can't even manually add those groups the latest builds.

Hi Everyone, Over the last week, some of the dev team has suddenly lost access to our test flight builds. Stating "builds expired", we've tried a few things including: removing the users from both test flight and apple connect reinstall the apps after the entire process, they're still stuck with the same "build expired" prompt. Originally only two devs were having this issue but more have started to follow. Has anyone seen something similar before? Thanks,

I want to create test flight for my unity project. But every time I create test flight for internal testing its say couldn't install your app. Please help

I didn't receive an invitation email in my email when I added management or developer Appleid to my developer account

I have been trying to set up testing on my app using testflight. However for internal testing the app version uploads, says it is testing however when i go to download it I get that error 'The requested app is not available or doesn’t exist.' this occurs on multiple devices so I believe it is an issue on apples end. Furthermore, I also get an error when I try to set up external testing. When I press on submit for review, I receive this error: 'There was an error processing your request. Please try again later.' I believe this may be related and there may be some issues with my account. I have contacted apple support 4 days ago and I am waiting for a reply. My case ID is 102542659560