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!
Related
I have a Safari extension in the macOS App Store. The Xcode project was created using the safari-web-extension-converter. It creates 4 targets, 2 each for iOS and macOS. I've done a number of releases of the macOS version successfully.
When I build and archive the iOS version, this completes successfully. When I attempt to upload the archive, I get this error after at the last Upload step:
App Store Connect Operation Error
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'michaelanthonyflores.Passport-Extension' under the iOS application 'Passport Extension.app'. With error code STATE_ERROR.VALIDATION_ERROR.90685 for id d8a52342-9686-4d7a-acec-93ce5dfb5d56
This is confusing since I don't have an existing iOS application in App Store Connect. Previously I attempted changing the name and ended up down a rabbit hole of signing and identity errors. What is the actual issue that this usually points to? How do I get more helpful debug information on this?
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
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...
I'm trying to submit an iOS app to AppStore and I'm having the following error:
ERROR ITMS-9000: "Missing or invalid signature. The bundle
'com.google.GPPSignIn3PResources' at bundle path
'Payload/My_app_name.app/GooglePlus.bundle' is not signed using an
Apple submission certificate."
I've submitted this app before I've never had this problem. Does anybody know if there is any recent change?
Update:
I could submit the app about 6 hours before having this error. Then, my app was rejected with this message:
This bundle is invalid - New apps and app updates submitted to the App
Store must be built with public (GM) versions of Xcode 5.1.1 or higher
and iOS 7 SDK. Do not submit apps built with beta software.
After this, couldn't submit anymore.
Update2:
Google has made an announcement about this:
http://googledevelopers.blogspot.com.br/2014/09/an-important-announcement-for-ios.html
A new version was released, solving the problem.
Just remove files below and build your app as usual!
GooglePlus.bundle/GPPSignIn3PResources
GooglePlus.bundle/GPPCommonSharedResources.bundle/GPPCommonSharedResources
GooglePlus.bundle/GPPShareboxSharedResources.bundle/GPPShareboxSharedResources
Google released the version 1.7.1 of the google plus sdk.
I created a new podspec for the 1.7.1 version as the previous owner is not reachable.
Just add into your Podfile:
pod 'googleplus-ios-sdk', '~> 1.7.1'
Adding the --deep flag to Other Code Signing Flags (OTHER_CODE_SIGN_FLAGS) in the Project (not target) settings seems to fix this.
The correct fix is to upgrade to the 1.7.1 version of the Google Plus iOS SDK.
It seems to have been specifically released to fix this problem.
If you diff the 1.7.0 and 1.7.1 bundles you will see that no files were added, but three files were deleted : GPPSignIn3PResources, GPPShareboxSharedResources and GPPCommonSharedResources - the three files that the App Store was complaining about.
Adding --deep flag didn't help me, so I solved the issue in a simple and elegant way (sarcasm detected). I removed Google+ SDK from Podfile, then downloaded SDK from here and installed it in a old-fashioned way.
my solution for Google Plus looked this way
deleted the 3 bundles from frameworks from my project
downloaded new Version 1.7.0 (had to upgrade anyway)
i opened the GooglePlus.bundle and removed 3 files (GPPSignIn3PResources,GPPShareboxSharedResources.bundle,GPPCommonSharedResources.bundle) as all 3 files will give you a warning in itunes
I added the 3 bundles back to frameworks
i tested my Google + login in app ... works
submitted ...
and run into a new issue (arm64 requirement), unrelated to this one :)
I think this should work if you don't need the resource files like login button.
If --deep doesn't work, then chances are that the bundle is simply resources and does not actually have any executable file. Delete its Info.plist and you'll be good. If there's some reason you actually need Info.plist, at least delete the CFBundleExecutable key.
I had the same error when I tried to submit the app with xcode 6.1. Nothing worked and I really tried everything.
Then I found a solution on apple developer forums. It worked for me:
Go into Keychain Access
Go into Login keychain
Delete Apple World Wide Developer Relations Certificate Authority
Go into System keychain
Delete Apple World Wide Developer Relations Certificate Authority
Download new WWDR certificate
Install it in Login keychain (just clicking it did that)
link: https://devforums.apple.com/message/1072465#1072465
This issue appears to have been fixed today by Apple, after being broken for ~24 hours.
Submitting the same app today, with no changes to the .bundle, no longer throws the error.
--deep code signing of the bundle is not required.
(Note that I did not test this with the specific Google bundle that the question references. The Resources Bundle that our app uses, though, now works correctly and no longer throws the error.)
Google just released an updated version 1.7.1, which can be downloaded from their website https://developers.google.com/+/mobile/ios/getting-started. Currently it's still not mentioned in their Release Notes though.
If you're using cocoapods you can copy the current 1.7.0 podspec, create a local one and change all the version references in their to 1.7.1 until the new one is merged into the official cocoapods repo.
You should also remove info.plist files
GooglePlus.bundle/info.plist
GooglePlus.bundle/GPPCommonSharedResources.bundle/info.plist
GooglePlus.bundle/GPPShareboxSharedResources.bundle/info.plist
By removing all Info.plist file form goolepplus.bundle file work for me.
I know you already have several posts with this subject but I still could not find the answer to my problem in time to upload my binary. I get the error:
The bundle is invalid. New apps and updates app submitted to the App Store must be built with public.
...but I'm already using xcode 5.1.1 so do not know why I get this error. How should I proceed?