App Submission

RSS for tag

Submit your apps to the App Store using App Store Connect.

App Submission Documentation

Posts under App Submission tag

191 Posts
Sort by:
Post not yet marked as solved
1 Replies
229 Views
I'm not sure what to do at this point. I submitted an app for testflight review. It has failed multiple times with this: 2.1.0 Performance: App Completeness. The app makes REST calls of HTTPS and then XMPP communication; however, it is failing on the REST calls and never making it to the XMPP communication. Originally, I was on a non-standard port for HTTPS (as this was a test app) and thought maybe that was the problem...so I moved to port 443 and now have a standard URL in the form of https://<hostname.domain>/ without a port listed. If it is helpful, as a test app, the hostname DNS is via DuckDNS and using Letsencrypt for certificates. I have tested the URL via a VPN from various parts of the world and it works perfectly. However, when the App Reviewer tests, the screenshot provided back to me shows the app cannot connect and the server has no indication of a connection. It is as though a firewall is blocking the reviewer from connecting to the address of my server. I'm not sure what to do at this point. Any ideas or suggestions?
Posted
by random9.
Last updated
.
Post not yet marked as solved
2 Replies
726 Views
About 24 hours ago, I got an email from Apple says my submission was accepted for release on the App Store. It can take up to 24 hours after release for items to become publicly available. However, the state is still "In review" when I log in to the App Store Connect page. Despite that in the app review section, it does say my app has been approved.
Posted
by pojudesu.
Last updated
.
Post not yet marked as solved
1 Replies
428 Views
Hi everyone, My iOS application uses a third-party SDK. Its integration went very well, until I used Transporter to submit the app to the Apple servers. I got an error (Asset validation failed (90060)) regarding the CFBundleShortVersionString value. Indeed, this SDK uses 4 dot-separated digits in its plist file as its Bundle identifier. Knowing that their usage is not appropriate, I tried to edit the plist file, but the behaviour of the SDK totally changes and becomes unusable. Their contact team do not answer my requests, which made me think that maybe someone already got this kind of problem. Would anyone have an idea to resolve this issue? Best regards
Posted Last updated
.
Post not yet marked as solved
2 Replies
287 Views
Hi everyone, We can't submit a new build of our titles since Friday. The game is live in [some territories in] the appstore already, so this is just a new release. The button goes to a spinner for a short while, and then just goes back to being the blue "Add for Review" button. Any advice or guidance would be very much appreciated. Ref: Thanks in advance!
Posted Last updated
.
Post not yet marked as solved
0 Replies
337 Views
I am developing a time control app, that allows the employees of a company to register their work hours (entry, exit and interval times). After careful studies on wich distribution method to choose, we decided that an Unlisted App would be the best approach. We thought of distributing the app via Ad Hoc, but the security clearences needed to run it conlficts with some laws of my country, and any sort of MDM is out of the question, since the app is intended to be run o both users private or company owned devices alike. This way, having it on the App Store as unlisted would solve both theese problems, since it would facilitate distribution to the users, and still have some sort of privacy. Problem is, when I sent my app for revision, i received the following message: "We found in our review that your app is intended to be used by a specific business or organization, including partners, clients, or employees, but you've selected public distribution on the App Store in App Store Connect. Since the App Store is intended for apps with a public audience, we recommend reviewing the other distribution options available to you through your Apple Developer Program Account. " I would like to ask for some support on this, did my intentions have been misinterpreted, or should I look for another solution to distribute the app? For clarification, I have created a Unlisted App request, and then sent my app for revision.
Posted Last updated
.
Post not yet marked as solved
0 Replies
218 Views
I am trying to upload screenshots for our first build validation in the "Prepare for Submission" page, but the image disappears after I drag it in the uploader. When I refresh the page there is a gray placeholder with a cloud icon. When checking the console after dragging an image to the uploader, I can see a "Upload operations error" error and a "[UPLOAD FAIL]" error, but there's no additional info.
Posted Last updated
.
Post not yet marked as solved
0 Replies
354 Views
Many months ago Apple stated: "From Fall 2023 you’ll receive an email from Apple if you upload an app to App Store Connect that uses required reason API without describing the reason in its privacy manifest file" Yet it seems nobody has received them? So whats the latest situation with this, if there's a mandatory requirement to add the privacy manifest by Spring how can people meet that now looming deadline if they haven't received the email that was due in the Fall?
Posted
by Piepants.
Last updated
.
Post not yet marked as solved
1 Replies
313 Views
I'm trying since yesterday to submit an urgent update but when I tap on "submit for review" it does nothing after a short loader. Safari Console shows a 409 error. Please help me or fix it
Posted
by neobeppe.
Last updated
.
Post not yet marked as solved
1 Replies
247 Views
This started last night, I submitted a new build and Apple reported at the time it was successfully uploaded. No emails back from apple but it never shows up in the appstore connect build section. Is something down at Apple?
Posted
by dpalme.
Last updated
.
Post not yet marked as solved
0 Replies
317 Views
My app was rejected with the following message Guideline 3.1.1 - Business - Payments - In-App Purchase Your app accesses digital content purchased outside the app, such as Workout and Diet Plans, but that content isn't available to purchase using in-app purchase. On your website we noticed paid plans https://www.theaverage.app/pricing.html. After user purchase these plans they will be available in this app. This is considered digital content and needs to be available to purchase in the app using in app purchases. But in fact I have just implemented a landing page for pricing and there is no payment options available outside the app. Having said that, Is it enough that I just remove the reference to the website https://www.theaverage.app from the app store ?
Posted
by coachgpt.
Last updated
.
Post not yet marked as solved
1 Replies
311 Views
Hello everyone, I was added to an organization account, and I was given app owner access. I can see the created app on my dashboard, but I can access it on my XCode. I can only see my Personal team Here's the screenshot below: I can't see the team I was added to because that was where the app was created. Here's the app on my dashboard Can anyone help please? Thanks in advance
Posted
by kxSplash.
Last updated
.
Post not yet marked as solved
0 Replies
305 Views
Hi there, I've successfully uploaded my app to App Store Connect using the Transporter app. However, it seems to be stuck in the processing state within App Store Connect. Despite uploading multiple builds, I haven't encountered any errors in my email notifications. Any insights on resolving this issue would be greatly appreciated. I am attaching a screenshot.
Posted Last updated
.
Post not yet marked as solved
0 Replies
338 Views
I'm encountering an issue while attempting to upload my IPA to the App Store. The error message indicates a problem with the datatype of the cfBundleVersion attribute, stating that it's incorrect. Strangely, this was working fine until yesterday. It's the error log: 2024-02-09 22:16:35.852 INFO: Show Progress: Contacting Apple Services… 2024-02-09 22:16:36.729 *** Error: Error [REDACTED]ing '/Users/vagrant/deploy/[REDACTED] - Development.ipa'. 2024-02-09 22:16:36.730 *** Error: An attribute in the provided entity has the wrong type Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER (ID: xxxxx) (409) { NSLocalizedDescription = "An attribute in the provided entity has the wrong type"; NSLocalizedFailureReason = "Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER (ID: xxxxx)"; "original_server_error" = { code = "ENTITY_ERROR.ATTRIBUTE.TYPE"; detail = "Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER"; id = "xxxxx", source = { pointer = "/data/attributes/cfBundleVersion"; }; status = 409; title = "An attribute in the provided entity has the wrong type"; }; } Uploading IPA failed: exit status 1 Here's the relevant snippet from my Info.plist: <string>74</string> I've built the iOS app using React Native and deployed it via Bitrise. Any insights into why this error might be occurring and how to resolve it would be greatly appreciated. Thank you!
Posted
by Ken2026.
Last updated
.
Post not yet marked as solved
1 Replies
316 Views
Hello I am planning to release a new version of app. Also there is plan for EOL by end of this year. So according to this requirement, I want the new version of app should be available only for existing devices where the app is already installed. New devices should not able to download the app. I know we can "Remove from sale" in Pricing and Availability" from app store, but that removes the app completely. So I have couple of questions: Can we post an app release only for devices where the app is already installed? Is it possible keep the app in app store but prevent new users from downloading?
Posted Last updated
.
Post not yet marked as solved
0 Replies
722 Views
We are trying to upload an app which has the existing version set to 1.2 , so we incremented the version to 1.3, yesterday, all of our apps started to disappear, and during this time, somehow for a fraction of a second our app appeared and we created a new version 1.3 to begin the upload. From then onwards we are getting the below error First error says 1.9, nowhere have we given anything remotely close to 1.9 in our source code. Please help!!!!!!! need to upload the app on an urgent basis. TSI takes time, support center asked to check on this forum. Tried via xcode and transporter both!! Asset validation failed (90478) Invalid Version. The build with the version “1.9” can’t be imported because a later version has been closed for new build submissions. Choose a different version number. (ID: b36cfa2b-d5ee-4558-8fb3-aa42d6224db4) 2024-02-08 18:15:33.332 ERROR: Asset validation failed (90186) Invalid Pre-Release Train. The train version '1.3' is closed for new build submissions (ID: 083e54b9-67c3-418b-a36d-8acadc739ddf) 2024-02-08 18:15:33.332 ERROR: Asset validation failed (90062) This bundle is invalid. The value for key CFBundleShortVersionString [1.3] in the Info.plist file must contain a higher version than that of the previously approved version [1.20]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring (ID: a96c0334-984b-4b5b-92f8-640b52a6acfe) 2024-02-08 18:15:34.195 INFO: Show Progress: Upload failed. Asset validation failed Invalid Version. The build with the version “1.9” can’t be imported because a later version has been closed for new build submissions. Choose a different version number. (ID: b36cfa2b-d5ee-4558-8fb3-aa42d6224db4) 2024-02-08 18:15:34.196 INFO: UPLOAD FAILED with 3 errors.
Posted
by LCTech.
Last updated
.
Post not yet marked as solved
1 Replies
488 Views
Hello, we have a pretty big macOS pkg (12 GB) that we upload on AppStoreConnect. When uploading manually via Transporter, everything works perfectly, but when we are automating this upload in script (via "xcrun altool --upload-app --apiKey"), the upload starts correctly, but we end up having an error after around 25 minutes. Setting request length to: 511 Web service call (lookupSoftwareForBundleId) result: { ErrorCode = 401; ErrorMessage = "Failure to authenticate."; Errors = ( "Failure to authenticate." ); NSUnderlyingError = "Error Domain=MZJSONServiceClientErrorDomain Code=401 \"Failure to authenticate.\" \U2026"; } When reducing the package size (to around 6GB), the same script runs perfectly. Anyone else has that problem, or even better, a solution?
Posted Last updated
.
Post not yet marked as solved
2 Replies
391 Views
We have tested this at our end on the latest mac version 'Sonoma 14.3 version' and application is launching successfully. But when i submit the app on App Store it will reject by given this reason(We were unable to review your app as it crashed on launch on Mac running macOS 14.3.) Thanks !!.
Posted
by amit2018.
Last updated
.