App Submission

RSS for tag

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

App Submission Documentation

Posts under App Submission tag

207 Posts
Sort by:
Post marked as solved
3 Replies
532 Views
I have a crypto app which by a miracle got released today, I discovered a bug and pushed an update and the app keeps getting rejected, the update has nothing to do with apple ecosystem, it's on the server, however the QAs have NO idea what they are doing... look at this: The guy was trying to put the login info that you use to sign in to use a functionality of the app, like he has no idea what the app does and didn't read the notes I left, this is the 4th time it gets rejected for different dumb reasons and I'm very frustrated with these dumb people... In the latest review I left a note under "App Review Information" that said: README: The username and password is for login into the app, DO NOT use it for anything else inside the app because obviously is not going to work... If you need a wallet to test the functionality inside the app you can use this one: 0xC7E4cbB12728Aa5a01606317Bcb0Be736e7f5cBB A couple of important things about the app: This is NOT a Wallet This app does NOT facilitates any transmission of any currency at all (including crypto) This app does NOT asks user for any private information that may grant access to his/her account to move funds It is: A wallet tracker, imagine you go to google and you track when the page changes background which is public. Nothing else. It doesn't move funds, or facilitates anything, it's a Read-Only app Thank you, Arturo Do you know what the guy wrote after denying the app? We have started your app's review, but we were unable to successfully access all or part of your app. Please provide us with a wallet address to fully review your app. Next Steps To help us proceed with the review of your app, please provide a user name and password in the App Review Information section of App Store Connect. Please be sure that the demo account includes content that demonstrates the features and functionality available in your app. So I write in the comments the wallet, the login info, the label on the app is very explicit and this guys keep rejecting... I'm I going crazy or these people need some training? How can I make sure that they read the notes or this go through the right process I don't know what to do at this point?
Posted
by
Post not yet marked as solved
1 Replies
266 Views
Your app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1 of the App Store Review Guidelines. Specifically, we found that your app uses a decoy functionality to hide a user’s photos, which is not an appropriate use of the Photos API. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, Apple does not permit unapproved uses of public APIs in App Store apps. Next Steps Please revise your app to ensure that documented APIs are used in the manner prescribed by Apple. It would be appropriate to remove any features in your app that use a decoy functionality to hide a user's photos from your app. If there are no alternatives for providing the functionality your app requires, you can use Feedback Assistant to submit an enhancement request. Can someone please how to resolve this issue? Thanks, Hai
Posted
by
Post not yet marked as solved
0 Replies
672 Views
Yesterday, I updated to Xcode 13 via the App Store. I'm trying to send an archive of my app to App Store Connect through the usual way in the "Organizer" window, and once the archive is submitted, I get the warning message: App Store Connect Operation Warning Your version of iTMSTransporter will be updated in approximately 10 days. I've never seen this before and have no idea what it means. The archive still shows in Testflight later and is useable, but I am not sure if it's safe to update the App Store version of my app with this archive build when it was uploaded with warnings. What is this warning, and how can I fix this? I also get this email about alternative icon errors after App Store Connect upload. I have alternative app icons enabled in the app and know for sure that I have 120x120 on iPhone, so I'm not sure why this is happening:
Posted
by
Post marked as solved
1 Replies
330 Views
Hi. I need your help. I tried to submit my app to the App Store Connect. I almost submitted there however it was an error. I tried many times. My attachment is here. Please take a look. I did using 'Any iOS Device (arm64)' there. However, why an error again? I am confused. Can you please help me?
Posted
by
Post not yet marked as solved
0 Replies
258 Views
I recently launched my app on the App Store and realized people in Ethiopia could not find it on the App Store. According to Apple, Ethiopia is not in the list of regions where App Store is available. Well understood. Now my wonder is, how is it possible that apps still show up on the Ethiopian App Store? How did those developers get theirs to show there and mine doesn’t? People who search for my app get results shown for other apps with simile names. How does that work?
Posted
by
Post not yet marked as solved
3 Replies
437 Views
Hi, When packaging an application using JDK 17 and the latest version of jpackage I get the below error when uploading to the App Store. All test prior to uploading complete just fine. I think it might be realated to the structure of the .app folder but not sure, any ideas would be helpful ITMS-90238: Invalid Signature - The main app bundle Test at path Test.app has following signing error(s): a sealed resource is missing or invalid. Refer to the Code Signing ... and ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Test.app/Contents/MacOS/Test]] The app verifies in Transporter just fine and codesign as well. codesign --verify --verbose=4 'Test.app' Test.app: valid on disk Test.app: satisfies its Designated Requirement Also entitlements seems to be fine. codesign -d --entitlements :- ./Test.app/Contents/MacOS/Test Executable=/Users/ryan/flat/Test.app/Contents/MacOS/Test <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.cs.allow-jit</key> <true/> <key>com.apple.security.cs.allow-unsigned-executable-memory</key> <true/> <key>com.apple.security.cs.disable-library-validation</key> <true/> <key>com.apple.security.cs.allow-dyld-environment-variables</key> <true/> <key>com.apple.security.cs.debugger</key> <true/> </dict> </plist> The app structure looks like the below, noting runtime contains the java runtime and app contains the application jar file. ls -al ./Test.app/Contents total 16 drwxr-xr-x 9 ryan staff 288 27 Sep 08:36 . drwxr-xr-x 3 ryan staff 96 27 Sep 08:35 .. -rw-r--r-- 1 ryan staff 1229 27 Sep 08:36 Info.plist drwxr-xr-x 3 ryan staff 96 27 Sep 08:36 MacOS -rw-r--r-- 1 ryan staff 8 27 Sep 08:36 PkgInfo drwxr-xr-x 3 ryan staff 96 27 Sep 08:36 Resources drwxr-xr-x 3 ryan staff 96 27 Sep 08:36 _CodeSignature drwxr-xr-x 6 ryan staff 192 27 Sep 08:36 app drwxr-xr-x 3 ryan staff 96 27 Sep 08:35 runtime The jpackage commands looks like the below: Noting that in the first, jpackage finds the correct certificate and entitlements because of the option --mac-app-store Further details can be found here https://docs.oracle.com/en/java/javase/17/jpackage/support-application-features.html#GUID-8D9F0607-91F4-4070-8823-02FCAB12238D rm -rf Test.app iconutil --convert icns flat.iconset /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home/bin/jpackage \ -i input \ -n Test \ --app-version 1.0.9 \ --main-class com.formdev.flatlaf.demo.FlatLafDemo \ --main-jar flatlaf-demo-1.6.jar \ --icon flat.icns \ --mac-package-name Test \ --mac-package-identifier "com.formdev.flatlaf.demo.FlatLafDemo" \ --java-options -Xmx2048m \ --mac-sign \ --mac-app-store \ --mac-signing-key-user-name "Ryan Henderson (A8KKM73GSU)" \ --type app-image --verbose codesign --verify --verbose=4 'Test.app' rm -rf *.pkg /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home/bin/jpackage \ -n Test \ --app-version "1.0.9" \ --description "Test Pkg" \ --vendor "Ryan" \ --copyright "Ryan" \ --app-image Test.app \ --mac-app-store \ --mac-sign \ --mac-signing-key-user-name "3rd Party Mac Developer Installer: Ryan Henderson (A8KKM73GSU)" \ --type pkg If you want I can also supply the verbose output from the .app generation and the .pkg generation using jpackage. From what I can see it's doing all the right things when signing etc. Thanks Ryan
Posted
by
Post not yet marked as solved
0 Replies
245 Views
Hypothetical: We release V1 as a phased rollout and on the second day pause it. We then create V2 ten days later and release it as a phased rollout while V1 is still paused. Questions: At this point does V1 go away(removed from the app store) or just stay in a paused state. I assume V2 starts at day 1 of the phased rollout. If an app is in a paused state for 30 days what happens? Does it go away(removed from the app store) or automatically get activated again? What is the V1 app is activated again from the paused state and before it reaches 100% on the seventh day a new V2 is released? (Not sure why this would happen just trying to think of all scenarios)
Posted
by
Post not yet marked as solved
1 Replies
496 Views
Hi Team, We are trying to register our App in the App Store for the first time. After filling the General Details, when continue is clicked, it is giving us error "The App Name you entered has already used". But when we checked in AppStore, there is no such app by that name. We want to register the app in the same name and dont want to change the name since it's already being used in android. Kindly help asap. Regards,
Posted
by
Post marked as solved
6 Replies
3.3k Views
Running the following command: xcrun altool --upload-app --type tvos --file "{IPA_PATH}" --username "{APPLE_ID}" --password "{PASSWORD}" Results in this error message: *** Error: Exception caught. Exception caught: *** -[__NSDictionaryM setObject:forKey:]: object cannot be nil (key: cfBundleVersion) (-1010) I am running the latest XCode 13. altool's version is 4.059.1219. Same build can be uploaded as normal through XCode's UI. Same command was working as expected on the latest Xcode 12.
Posted
by
Post not yet marked as solved
1 Replies
155 Views
Hi Buddies, I hope you are doing well, basically, I'm here to ask something regarding my site app. I'm making my site Mobile app that just works the same as my site. The work of the app is just that the app will display my app on smartphones, using the mobile application. My question is that this type of app will approve by apply store or not? This is my site: (https://printersinsider.com/)
Posted
by
Post not yet marked as solved
2 Replies
228 Views
Hello, like in the title, I would like to know if is possible: publish an app named "TestApp" with appid aaa.bbb.ccc afterwards, publish the same app named "OfficialApp" with appid aaa.bbb.ddd In our use case, the first app published will be only a test app (not published but only for testflight), while the second app will be the official one in production/store. It is possible or there are some checks about "same source code"? Thanks in advance
Posted
by
Post not yet marked as solved
0 Replies
520 Views
My app is getting rejected multiple times and I seem to not understand where to place the legal stuff. This is the message: We noticed that your app did not meet all the terms and conditions for auto-renewing subscriptions, as specified in Schedule 2, section 3.8(b) of the Paid Applications agreement.  We were unable to find the following required item(s) in your app's metadata: – A functional link to the Terms of Use (EULA) Next Steps To resolve this issue, please add this missing information. If the above information is present, please reply to this message in Resolution Center to provide details on where to locate it.  If you are using the standard Apple Terms of Use (EULA), you will need to include a link to the Terms of Use in your App Description. If you are using a custom EULA, add it in App Store Connect. I am using Apple's standard Terms of Use. When I asked for more information, the person also replied: We were unable to find a functional link to the Terms of Use (EULA) in your app's metadata. Please add this missing information in the app's metadata. Where do I put it? Right now I have in the sign up screen and in the settings with the name "Terms of Service", what's wrong, where it's supposed to go? Is that the same and I just need to rename it to "Terms of Use (EULA)"? Please advice
Posted
by
Post not yet marked as solved
1 Replies
280 Views
Hi, I am a Senior Product Manager for a learning platform company. We have created our own app which provides mobile access and offline content library for our learning system. This has a generic login flow for users from many of our client organisations and uses our product branding. We also have a major international client who is launching a mental health wellbeing program that they would like to surface through a similar app, but have this branded for their organisation. The login flow is different, and the content that you can access would be completely different to the generic app. The client would publish their app themselves through their existing App Store account. My understanding is that apps that are too similar may be rejected by Apple. What is the likelihood of this and does anyone know of a way I can find out more or get some kind of sanity check done by Apple before we go to the effort and expense of creating the new client-specific app that runs the risk of being rejected? Many thanks in advance for any assistance.
Posted
by
Post not yet marked as solved
4 Replies
1.1k Views
Yesterday, appstore submission system changed. You can add different type submissions such as App Store Version, In-App Events and Custom Product Pages. My app was previously in Metadata Rejected state. With new build and metadata, I click "Add for Review" button Then, it redirects me "App Review" tab. I click "Submit to App Review" button and I get this error: "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." But, there are no errors showing. I just see metadata rejected message. I've been adding and removing submission again and again hoping it would work but no avail. Anyone managed to resolve this issue? Thanks!
Posted
by
Post not yet marked as solved
0 Replies
249 Views
Hi, My app has been rejected because the reviewer was expecting the wrong behaviour. I responded to him/her as a reply in the "Resolution Center" with the good expected behaviour and how to properly test the app. There has been no response for multiple days. Will my replies be ignored since the app has already been rejected, or will the reviewer do a second pass review with my new comments? If my replies will be ignored, what's expected of me? To do an appeal or submit a new version of the same exact build (since the build was OK - the reviewer simply wasn't expecting the right behaviour)? Thanks :)
Posted
by
Post not yet marked as solved
1 Replies
307 Views
i am trying to update my build in appstore connect, and every time i try to add for review (or submit for review, in the older way) i get the message: Unable to Add for Review / The items below are required to start the review process: / This field is required listed below are things i've tried and done filled everything in "Agreements, Tax, and Banking" agreed the Paid Apps contract filled in every fields other than optional areas - including copyright actually i am assuming that the copyright part is causing the problem because the "save" button doesn't get activated even though i changed the copyright. to make it short i just cannot save my copyright information. can anyone help me with the problem? i'm currently getting crazy because of this.
Posted
by
Post not yet marked as solved
1 Replies
413 Views
Everything seems to work fine when I upload my app using Xcode 13.0, but very soon after the upload successfully completes I get this email from Apple: Dear Developer, We identified one or more issues with a recent delivery for your app, "MyApp" 1.0.0 (2021.10.24.1). Please correct the following issues, then upload again. Best regards, The App Store Team The email names no issues, and the builds page for my app at appstoreconnect.apple.com doesn't show my upload at all, not even as failed. The last time I uploaded a build was about a month ago, and it worked fine. I suspect Xcode was auto-updated to 13.0 since my last upload and that's the source of the problem, but I have no clues to go on. How can I figure out what's going wrong?
Posted
by