Hello Apple Support Team, We are developing a macOS application that allows users to import and view PST files (Microsoft Outlook archives). These files contain a complex, proprietary format that requires specialized parsing libraries. To achieve this, we are using Aspose Email for Java, which is currently one of the few reliable libraries that support complete PST parsing across platforms. Why we are using Java & Aspose The Aspose Email Java library provides a comprehensive API to extract mail data (including metadata, attachments, and folder structure) from .pst files. A native Swift or Objective-C alternative with full .pst parsing capability does not exist, which is why we opted for a Java-based helper module that runs in the background and communicates with the macOS app over a Unix domain socket. How we bundle it We package the AsposeEmail.jar and a custom JRE (Java Runtime Environment) created using jlink, tailored to run only our jar. This entire setup (JAR + JRE) is bundled within the Contents/Resources directory of the macOS app, and we invoke the Java runtime using standard process launch APIs from Swift. Problem during App Store Submission When we archive the app and submit it to the App Store, the validation step raises an error: ITMS-90284: Invalid Code Signing - The executable 'com.app.sample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjsig.dylib' must be signed with the certificate that is contained in the provisioning profile. ITMS-90284: Invalid Code Signing - The executable 'com.app.aample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjvm.dylib' must be signed with the certificate that is contained in the provisioning profile. When we attempt to code sign the custom JRE, especially the .dylib files inside, the runtime breaks. Java is unable to launch correctly and throws permission errors and execution failures. Alternative we thought of (On-Demand Download) To avoid the code signing issue, we decided to remove the JRE from the bundle and instead download it on demand when the user performs an action like "Import PST". However, we realized this may violate the App Store Review Guideline 2.5.2: Our use case, while not dynamically modifying features, does download and execute a Java runtime, which could be interpreted as executing new code post-installation. How can we proceed? We are looking for Apple’s guidance on the correct and compliant path forward: Is there a recommended way to bundle and codesign a custom JRE so it is accepted by the App Store? Is on-demand download of a custom runtime for a very specific parsing task permitted, assuming it doesn't modify app features but simply supports user-initiated operations? We would greatly appreciate any guidance or best practices on how to handle this situation, particularly with respect to App Store compliance. Regards, Maaz Hussain

Hi, I have uploaded the Main App with App Clip to Apple Store Connect and launch in TestFlight. But at first build I wrote wrong App Clip's associated domains in the App build target ,and also mistakes in the AASA file. Then I correct it like appclips:com.***.***.AppClip in both places. However, I tried many uploaded version and it still display "The app clip in not currently available... " error. The domain is successfully verified in App Store Connect and the test version can dowloaded to device for testing. Only that it can't show the right Card as expected. I want to ask if I set the wrong domain in the beginning few builds, and correct it later. Will it work again or not? Moreover, the tester email is not the same as apple id for tester's mobile phone. I have corrected it . I don't know will it affect the result ,and maybe something have stored in Apple backend server for testflight data and need to be refresh to make it work. Thanks and please advise. Best regards Sunny.

Hello there! I have developed a website (https://finnia.ch). Now I have transformed it to an app (with webview). If anyone would like to check it out and test it here is the link: https://testflight.apple.com/join/hmyDw74t It is a administration tool (not a game). Simon

We’re seeing a strange issue with our TestFlight setup. We normally have 4 apps available in TestFlight (all of which are also live on the App Store). Today, 3 of them disappeared from TestFlight because their builds were marked as expired. I re-submitted new test flight builds, which made the apps reappear but now when trying to install ANY of our apps, we get an error saying: “The requested app is not available or doesn’t exist.” There are no issues or flags on the TestFlight pages in App Store Connect, all builds are validated, and all apps are still downloadable from the App Store without any problems. Has anyone else experienced this?

Hi everyone, I'm trying to submit the first app for Beta Review to do Beta in Testflight, created a separate workflow for Beta Build and stuck at the step of filling in the "Information for Beta Review" form. After filling in all the fields and clicking "Save" it just shows me an empty popup with "Close" button, and I see that request for https://appstoreconnect.apple.com/ci/api/teams//testflight/information-v2?product_id=ACTUAL_ID_REPLACED_HERE is failing with 404. Does anyone have any idea what I might be doing wrong? Thanks and appreciate the help

When adding a phone number in the contact information for submitting an app for external use, it doesn’t let me proceed. It says the number is invalid and that I should ensure it contains only numbers, but it still won’t let me continue. I need help with the external use configuration.

Can you help me how to upload it to TestFlight setting and distribution. I have try it but got this error. I have setting profile for camera access to but it still like this.

I managed to enter the beta program of WhatsApp during my vacation in Cyprus. I installed the app from the TestFlight app, and everything was ok. Now, when I am in my home country (Israel) - I can't see the WhatsApp app in the TestFlight (for example for updating it). I don't know what to do, and there is no information online 😕 Some screenshots to support my problem: This is the app itself in my home screen. It has the orange dot, indicating it is from TestFlight: This is my TestFlight app home screen - no sign for WhatsApp app: This is the WhatsApp app from the App Store app. We can clearly see that it is being recognized that the WhatsApp app is installed through the TestFlight app: When trying to "View in TestFlight" from the App Store, this is the screen in TestFlight I am seeing:

We have an existing app - "Pluralsight: Learn Tech Skills" which is built for mac using mac catalyst. The latest version here is 3.59.0. We are shifting to "Mac (Designed for iPad)" destination instead of catalyst. The build with this change, uploaded from xcode with version 3.60.0, is not visible under macOS/iOS tab under macOS testflight app. Also we are not able to see "iPhone and iPad Apps on Apple Silicon Macs" section under "Pricing and Availability" page. We believe that this needs to be enabled for the mac app built with "Mac (Designed for iPad)". Please help out.

My company has been sharing the redeem code to the company domain email address and allow staff to redeem the app with their personal Apple ID. However, we found that the redeem code is failing and claiming the Apple ID doesn't match the one associated with the invitation. I cannot find the documentation for this change, may I know if this is something permanent?

"Hello everyone, I'm experiencing an issue with App Store Connect and Xcode. My client has granted me admin access to upload an app to TestFlight. However, while I can see the account in App Store Connect, it's not visible in Xcode. I suspect the client's account might be a personal account rather than an organizational one. Can anyone suggest what I might be missing or what additional steps need to be taken? For context, I can see all other teams, but this particular team is not appearing in Xcode. Any help would be appreciated!"

Getting Same Error and App Rejection With XCode 14.2. we have pushed a successful build a week ago and there was no major change in code level and have not added and lib after that but now getting error and app rejected, stuck in this issue from last 1 day. anyone found any solution to this

Let's say my app has two versions: 1.x is the main version 2.x is the beta version - still in testing Is it possible to maintain both of them in parallel on TestFlight ? In the first phase, main version will still receive updates, which are released to the market. Beta version only receives updates for testing purposes. In the second phase, beta version will be published to the market and main version will stop receiving updates. Imagine the following scenario of uploads. Is it possible on TestFlight? version = versionName (buildNumber) upload main version - 1.10.0 (10) upload beta version - 2.0.0 (0) upload fix for main version - 1.10.0 (11) release main version - 1.10.0 (11) to the market upload beta version - 2.0.0 (1) upload beta version - 2.0.0 (2) upload main version - 1.11.0 (12) release main version - 1.11.0 (12) to the market upload beta version - 2.0.0 (13) release beta version - 2.0.0 (13) to the market

My app works fine from Xcode but once installed via TestFlight it drops out immediately without any explanation. It sits in the background with the launch screen showing. I not sure it is getting to run at all. Where can I find reports on what is happening or what could be the issue here? I am new to all this so any help would be appreciated.

I'm confused, and I can't find instructions. I have a build for internal testers. That works great! I created an external group, "Beta". I click Beta. I can set up testers. But when I go to builds, it says "No Builds Available" I filled out the test information form. I don't see any buttons like submit for review. What am I missing? Thanks in advance!

I'm encountering an issue when trying to submit a new build of my iOS app to the App Store. The app launches from TestFlight without any problems, but when attempting to submit it for App Review, I get the following error: "This build is using a beta version of Xcode and can’t be submitted." However, I'm not using a beta version of Xcode. I've tested this with both the public releases of Xcode 16.3 and 16.2. The build logs show no issues with the SDK or Platform versions, but in App Store Connect, the metadata is displaying the following: Build SDK: $(SDK_PRODUCT_BUILD_VERSION) Build Platform: $(PLATFORM_PRODUCT_BUILD_VERSION) Have anyone else experienced this? Any insights on resolving it? Thanks in advance.

I’m getting an error message that’s blocking me from using TestFlight. Once I log out of my account and log back in, it disappears - but then it pops up again after a few days. If anyone knows a long-term solution, I’d really appreciate it!

I get "No Builds Available" when adding new external testers to a build that has already been distributed to 100+ external testers. This happens for all external testers I try to add today: Existing testers still have access to the build. Creating a new group of external testers doesn't help. The issue happens with both new and existing groups. The build was previously approved by Apple Beta Review and expires in 36 days. What am I missing?

After I uploaded my app to testflight, the MinimumOSVersion was set to 14.0, and TestFlight showed MinimumOSVersion=14.0. However, after I distributed it, if the user's device is iOS 14, then the MinimumOSVersion in Info.plist=14.0, and if it is an iOS 15 or higher device, the MinimumOSVersion in Info.plist=15.0 will be changed. Because my app will detect this value, I had to change my code, but this is too strange, at least there will be no problem before April 27, 2025, because I checked my distribution records.

When I uploaded app to TestFlight to test, it shows missing compliance. And I tried this way: https://stackoverflow.com/questions/35841117/missing-compliance-status-in-testflight It used to work. But now it is not. May I ask what should I do to solve the missing compliance problem?