I've been trying to submit my app for the past 24 hours to no avail. The problem has been caused mainly due to third-party frameworks I think. Especially the GooglePlus API. When I upgraded the GooglePlus API to its latest, the validation process gave me warnings about references made to non-public APIs, which I found impossible to fix, so I reverted to the previous version which hadn't given me any problems so far during submission.
Now when I did try to submit it again, it gives me the following error:
This bundle is invalid. The app is not signed.
I have no idea why. I signed it with the same provisioning profile I've been using for the previous versions. Any idea why this may be happening?
Related
I'm getting the following error after my app has processed in AppStore Connect.
"ITMS-90562: Invalid Bundle - The app submission can not be successfully recompiled from bitcode due to missing symbols during linking. You can try to reproduce and diagnose such issues locally by following the instructions from:
enter code herehttps://developer.apple.com/library/archive/technotes/tn2432/_index.html"
I did an AdHoc export as the above link recommends and was not able to reproduce the issue. This is with Xcode 10.2 with an app that includes a watch extension and several other extensions. Many previous builds of the app have been submitted successfully. As recently as last week. I even went back to the commit of the last known good submission, increased the build number and uploaded that with the same results. I started seeing this problem on Friday September 13. My instincts are telling me this is most likely a bug with AppStore Connect. Is anyone else experiencing this same problem or have advice about how to work around it?
I have been trying to submit a Swift 3 app to Apple from Xcode 8.2 , App passes through all phases but gets stuck at authentication forever and then ends with an error. But then I export app for Appstore submission and then upload the same using Application Loader, tried with two different accounts but no avail. Have referred to this thread as well This action could not be completed. Try Again (-22421)
Most upvoted answer says apple servers may be misbehaving but I wonder how many days ? Is this something specific to Swift app ? I havent tried submitting any ObjC app recently so not sure, can anyone provide a solution ?
I stopped using Xcode uploader after 2 hours of failed uploading attempts. Then I took Application Loader instead and it told me the exact reason of fails. In my case it was too fat watch extension.
Hope this will help.
It's ongoing issue with Apple App uploader server, since couple of days, so you don't have a way, rather than waiting.
You can try following solutions:
Use Application Loader to upload your app, as Xcode organizer can't upload file (rejects IPA) sometimes, without genuine reason and it's frequently occurring issue, with Xcode Organizer, that apple could not resolve permanently.
Solution for error code: 22421
Apple app upload server is not working properly (not in
connection or lost connection during file upload). Just wait and try
again later (may be after a day).
Fluctuation in your network
connection, during file upload.
You may not have added privacy
statements in your info.plist file.
Cocoa Keys: Here, is list of keys that you should consider to add in your info.plist file, if you have used that service in your application.
Nowadays, you may also face, this error code: 90186 (with app loader)
Outdated application loader can be reason of this error. Use latest Xcode tool and use application loader from Xcode Tool.
Incorrect/invalid provisioning profile, associated with your build. Ensure, your have used correct provisioning profile (A provisioning
profile with Distribution/Production mode is require. A Development mode provisioning profile won't allow your to upload app on store.)
You can find latest Application Loader Tool from latest Xcode Tool: Xcode ▶ Open Developer Tool ▶ Application Loader
I am having issues uploading my app to iTunes Connect for Testflight testing. I don't receive any errors when uploading the build through Xcode 7.0, but after my build attempts to processes on iTunes Connect I get the following automated email from Apple:
Dear developer,
We have discovered one or more issues with your recent delivery for "MY_APP". To process your delivery, the following issues must be corrected:
Address Sanitizer Detected - The executable ${executablePath} links in the Address Sanitizer. Please remove Address Sanitizer usage before submitting to the App Store.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
I've ensured that "Enable Address Sanitizer" is unchecked for all of my build schemes. I cleaned the build folder and attempted to upload a clean build, but am still having the same issue. I don't see anything in the build settings related to Address Sanitizer.
Is there something else I need to do to remove Address Sanitizer?
we hit this same problem and our team spent the last 48 hours trying to isolate it. Turns out that it was a naming conflict in one of the bundles that we were including. Since the bundle is part of our standard SDK stack that we include in every game submission and we never had any issues with it before, I am assuming that something was upgraded on Apple's back-end to include checks for a lots of the new xCode features which caused the naming conflict during the post submission auto-code checks.
it took us over 20 submissions to isolate the offending bundles and renaming them fixed the problem. If you're hitting this issue, I suggest going through your plist to see if any of the bundle names have used keywords that are reserved for Address Sanitizer usage. It was one of our engineers that identified the problem and he's away on vacation for the next week but apparently, he replaced the hyphens in the bundle name with underscores and the problem disappeared.
Wanted to share this one quickly and hope it helps folks that are stuck on this issue as it was an absolute nightmare for us to pin down.
Thanks to some help from #Erik-Kerber, I managed to get a build through.
I was running the GM of Xcode 7 (7A218). After updating to the release build (7A220) from the App Store my app successfully passed iTunes Connect processing.
My build also get rejected.
I am using Fabric / Crashlytic library in my project.
I was also having the same issue and the same mail i got from Apple when my build rejected by Apple.
But after replacing my Fabric/Crashlytics library with updated library it get solved and accepted by Apple Succefully.
Since itunes connect UI have changed I'm expressing problems submitting app updates.
I am using libgdx v 1.3.2-SNAPSHOT' and roboVM v '0.0.14'
The error I am getting from Application Loader:
ERROR ITMS-9000: "Missing or invalid signature. The bundle
'com.google.GooglePlayGames' at bundle path
'Payload/IOSLauncher.app/GooglePlayGames.bundle' is not signed using
an Apple submission certificate."
Any idea on why is this happening?
I found the solution! :
The latest update google has done to their iOS SDK 1.7.1 has fixed up everything except for the final GooglePlayGames.bundle which is available in the outdated GooglePlayGames iOS SDK v3.0
As soon as that SDK gets updated, we should be able to use this plugin and validate properly.
As for now you can do it manually by deleting the "GooglePlayGames.bundle/GooglePlayGames" binary.
It won't affect anything since it's just derived data.
Works Perfectly!
Once I tried to validate my iOS application on the appstore, I got the following error on XCODE:
Your app contains non-public API usage. Please review the errors, correct them and resubmit your application.
The error doesn't provide an explanation on which are the non-public classes that we used. How can I get it?
The app references non-public symbols in Payload/...app/libsqlite3.0.dylib: _dispatch_sources_type_vm, guarded_close_np, guarded_open_np
I have tried to solve the problem by removing libsqlite3.dylib from xcode and by adding linker flag '-lsqlite3' or '-libsqlite3' (with the last flag the app did not compiled).
How can I solve it?
You could also just download the sqlite amalgamation and include the sqlite source code into your app. That would not link to the system libsqlite3.0.dylib and the problem would be avoided. Your app binary would get a little bit bigger, but the build/validation problems would go away.