I am trying to submit my app.ipa to application loader but when i press there is a error
We’re having trouble connecting to the App Store. Please try again later.
You are not authorized to use this service.
You might have changed the password for your developer account. Just sign in again with correct password, then this error should go away. (I saw exactly the same error today and after I signed in with the updated password, it is fine now.)
Related
I'm signing my macOS application with a Developer ID Application Certificate and sending it to Apple's notary service. When I'm uploading the build from XCode I'm getting the following error:
Failed retrieving request UUID for upload. You may have outstanding
agreements to sign on App Store Connect.
I've checked the following URLs and I don't have any new prompts for new agreements:
https://developer.apple.com/account/
https://appstoreconnect.apple.com/
https://appstoreconnect.apple.com/agreements/#/
Is this a bug from Xcode/App Store Connect or does the message refer to other agreements that must be signed?
After failing to solve this with an Apple Support person, I removed an admin who did not have a current individual Apple Development account from the Team. Solved the issue instantly.
Had the same issue and also no outstanding agreements to sign.
In the end, the problem was, that the user who wanted to upload the build for notarization didn't have "Access to Cloud Managed Developer ID Certificate" in the Users and Access section on App Store Connect. It worked before for that user, so something in the backend must have changed in the meanwhile.
I had the same problem, no agreements to sign, I had Access to Cloud Managed Developer ID Certificate and still got the error.
To fix it I went to Xcode->Preferences-> removed my developer account from Xcode the re-added my developer account to Xcode and it worked.
Update from November 2022: I no longer receive the error from the question, it was probably fixed by Apple on their side.
I am just starting out trying to connect Xcode to Github. I keep getting this peculiar error, saying "Failed to load owners" whenever I try to create a remote repository from within Xcode under the Source Control Manager. See the error here
If I ignore the warning, the upload then fails with this error.
I cannot seem to find anything online regarding this, and I cannot for the world notice anything being wrong with my GitHub account. The account itself is also accepted by Xcode (successfully added under the Accounts pane in Preferences).
Any help will be greatly appreciated.
In your GitHub account, when you are creating a personal access token to connect your Xcode to GitHub, you have to check off repo, write:packages, and read:packages.
Shown by the image here: https://i.stack.imgur.com/NUiiC.png
Then, you should be able to create the repo without any problems! Hope this helped.
I deleted my GitHub-Profile in the XCode Preferences and setted up again. After that it worked smoothly.
After having had a chat with a kind representative from GitHub Developer Support, it seems like it in my case had to do with my old username and password credentials that was saved on my machine. I quote:
Sometimes applications can use these old credentials, even if you
replace it with the personal access token.
Credentials for git authentication are stored in the Keychain App, and
git passes these onto GitHub when pushing changes to a Repository.
I'd suggest checking in the Keychain App for any records with the name
GitHub.
If they exist, delete those and try the push again.
Git should ask you to enter your username and password and once you
re-enter them, the correct credentials should be stored in your
Keychain app for future use.
So there you have it. This in fact solved my problem. It could also have had something to do with the personal access token that might not be set up with the proper permissions. If you have the same problem as I had you could also check out the scopes on your personal access token to verify it has access to everything you need. Step 7 on the help guide below has a screenshot of what that looks like:
https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
For anyone who's looking for another way. What happened to me is that my personal access token expired, and I needed to generate a new one in Github / setting/ developer/ access token. After I generated a new one, I logged out of Github via Xcode, Logged back in and put in my new access code and cleared the issue!
When we hit the button to do the final publish to Apple Store we get a "Spawn failed" error and cannot find out why. Apple quite rightly say "it's not our problem as you're using someone else's tools" but that's not really helpful. Anyone have any pointers on where to look.
Spawn failed.
, Error: Spawn failed.
at CloudPublishService.getiOSError (C:\Users\XXX\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:79:21)
at CloudPublishService. (C:\Users\XXX\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:96:29)
at Generator.next ()
at fulfilled (C:\Users\XXX\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:4:58)
I was having the same problem and just figured out what's going on. Because the error message is just a generic explosion while trying to get a real error message my fix may not fix your issue but here's what was going wrong for me:
I had two factor authentication on and I was trying to use the app-specific password that I generated for the nativescript appleId login. If you use the appleId main password then it will get past this error and then two factor authentication kicks in and asks for a number sent to your device, then it asks for the app-specific password
If you're sure you're entering the right credentials and the app-specific password, you may need to check if the Application Version (if you're using NativeScript Sidekick, it's in the Properties tab) is not equal to a version you've already published to the App Store. This fixed the 'Spawn failed' error for me.
I am a developer and to use the marketing API I must have an app. I have this app and it is currently in development mode. Is it necessary to make this app public?
My initial thinking was 'no' and I have been successfully using the API via this app for a while now and have not experienced any limitations until recently. When trying to change the status of an Ad to active I got an error message that suggests the problem could be due to the app being in development mode.
FWIW I am able to successfully change Ad status to paused most of the time, however, more often when I try to activate an Ad, it fails, although it does succeed sometimes. As such, I believe I am using the API correctly. It seems to be more of an Ad state issue, or, perhaps an app state issue. Most of the time the error messages I receive from the API are not helpful. I did get one today that suggests the possibility that my app needs to be public.
Here is the error just in case it helps:
[{"code":400,"body":"{\"error\":{\"message\":\"Invalid parameter\",\"type\":\"OAuthException\",\"code\":100,\"error_data\":{\"blame_field\":\"targeting invalid fbid 141898914497\"},\"error_subcode\":1487133,\"is_transient\":false,\"error_user_title\":\"Can't Set Exclusion Targeting\",\"error_user_msg\":\"You may not be able to select a connection to exclude in your targeting because you're not an admin of this Page or app, or because the app is in developer mode, or the event is in the past. If you want to run your ad with exclusion targeting, please request admin access from the owner of the Page or app or move your app out of developer mode to link it to the ad. If you want to select an event for exclusion targeting, please make sure the event end time is in the future.\",\"fbtrace_id\":\"Dqzily7dOQa\"}}"}]
Thank you for any help or insight into this issue.
Just to resolve this, the answer is no, the app does not have to be public in order to use the API. The problem turned out to be an access permission issue on the account in question.
I have a Unity project that I'm trying to build out to Web Player for Facebook. The project previously existed as an Android app and works well with Parse as a backend for high scores.
However, in the web player, I get an authentication pop-up titled "Authentication Required" and the message "A user name and password are being requested by https://api.parse.com. The site says: "Parse"" with Username and Password fields. Entering my Parse credentials didn't seem to work here either. I don't have a Parse User to try either - I just rely on Parse to generate them automatically without passwords. The scores never actually get loaded because this stops the process.
It works in the Editor. Has anyone had a problem similar to this? A search came up empty.
I've encountered the same message after upgrading to Unity 5 with the latest build for parse on the asset store (v. 1.3.5). While it's not a preferable solution downgrading to a previous version build (4.6) the problem does no longer occur.