Related
i am unable to publish any apps on my Google Play Developer account is says
An unexpected error occurred. Please try again later. (8869003)
can anyone please help me to get out of this?
Had same issue today.
In my case I had to logout and login.
Then everything worked.
In used incognito window and worked. Clearing cookies, cache might also work
It happens due to conflict between chrome signed in account and google console signed in account, signing out from console and resigning in will solve the conflict. Solaza suggested the same solution
I ran into a similar Android Developer Console Issue today.
I was trying to promote a Closed Testing Track (Beta) to Production.
I always got the following error (with random error codes):
An unexpected error has occurred. Please try again. (Random-Error-Code)
The solution was to create the new release by hand in the Production Track, rather than promoting up the existing Closed Testing Track.
This happened to me as well. It could have been because I changed my account email on the same day. I got it working the next day.
Things to try:
Use a different computer.
You have to select at least one country from the list of countries to test.
Give it 24 hours for Google to refresh your email change, and try again.
If nothing works, contact Google Play Console Customer Support, they have a chat window.
I faced this issue when update my developer profile on google play developer account. There is a featured app selection at the end of the page. I selected an app that is not published yet, caused the problem.
I didn't select that app as featured and it worked.
in my case it's due to the network issues that my laptop by default will use our company's system proxy, I guess it'll go through some internal firewalls before reach the outside world, the latency caused the error, i switched to no proxy mode, then everything working fine
My email address has changed and now I can't log into Visual Studio 2017.
The error is "We could not refresh the credentials for the account. Failed to refresh the access token".
How can I fix this?
This bug will be fixed in a future version.
For now:
Close down VS2017
Go to "C:\Users\{username}\AppData\Local\.IdentityService"
Rename "IdentityServiceAdalCache.cache" as shown below. (for example just add an underscore to it)
Restart VS2017 and log in.
NOTE: There are similar issues that this won't resolve, but this worked for me.
Open Visual Studio. Click Help, Send Feedback, Report a Problem...
This brings you to a login screen. If you log in from there, it will log you into Visual Studio.
What worked for me was to rename .identityservice and then restart VS and log in to your VSTS account. It then recreates a new .identityservice that it can access.
I tried by deleting only the IdentityServiceAdalCache.cache as in the accepted answer but it did not fix the problem.
For the record, I managed to fix it by deleting every files within the .IdentityService folder (located in C:\Users{username}\AppData\Local.IdentityService).
I have read dozens of posts on this topic discussing clearing out .IdentityService. I tried every variation of this solution that one might think of. None worked.
I ended up poking around and trying to manually login to my Microsoft account using Internet Explorer, but I could not connect to https://login.microsoftonline.com. I added the https://login.microsoftonline.com address to my Trusted Sites in Internet Options. Once I had done this, Visual Studio was able to connect to Microsoft and validate my account.
When an error occurs, Visual studio will log it's error messages in the following folder. Please check the logs located at
%Temp%\servicehub\logs
This can also be caused by network restrictions. Please disable your virus guard or firewall and check.
This issue can also be caused by running VS "As Administrator" and the administrator is a different user. Just some FYI.
None of these answers will resolve that issue unfortunately.
Very old thread but if someone is still having this issue, then try following in my footsteps:
I just deleted the entire .IdentityService folder, and launched visual studio again... It asks you to log in and works normally. (for me)
Make sure you can access https://login.microsoftonline.com
If your network is blocking that (perhaps to block Microsoft webmail), then the above solutions will not pertain to you. Either unrestrict access, or you will need some off-line version.
In case someone is still looking for an answer. What worked for me was checking that the AppData folder and Local folder were not on 'read only mode' in the path "C:\Users{username}\AppData\Local.IdentityService" and it just worked!
Check to make sure that your PC no limit(IP-Firewall) to Internet connection access.
Disable or turn off VPN
It happened to me when using an account that uses my organization's email-domain, and I guess it tried to verify it and it couldn't find it in their database, and as soon as I used an account with a onmicrosoft.com domain, it worked.
The interesting part is that it allowed me to create the Microsoft account with this organization email and I still use it for DevOps, and it just stopped me when signing in with Visual Studio, I don't understand why this difference is.
I hope this can help someone..
I have VS 2017 and had this exact issue. Simply deleting
C:\Users\{username}\AppData\Local.IdentityService did not work for me.
Follow the steps 1-2 below to see if you might have and identical cause of the problem, and the rest how to solved it if so.
Go to C:\Users\{user}\AppData\Local\Temp\servicehub\logs and open the latest error logs from VS.
IF you see "Retrieved tenant memberships, found '2' owned tenants", then follow the rest of the steps.
Go to azure portal then login under the username you are
trying to use.
The following steps may change by the time you read this, but you
want to get to step 6. Go to Manage Azure Directory.
Click "Switch Tenants"
I was linked to 2 tenants, one of which I did not need. This is what had been causing my issues. Select the useless tenants, and click "leave tenant".
Once this is completed, close all instances of VS.
Delete C:\Users\{username}\AppData\Local.IdentityService.
Open VS and login to your account.
I found the same behavior when using Administrator user.
Any other user can login and activate the license only for himself.
I don't think there is a way to activate for Administrator, which makes using this licensing awkward for usage in a shared resource (i.e. build server).
The one solution which worked for me was resetting the domain password and restarting the system.
I just wanted to share this because i was struggling with the same problem since 8 days tried everything on net and this worked.
Hope it helps someone :)
I updated Visual Studio with latest package and after rebooting my PC issue was solved. I was able to log-in
Opening VS as admin worked for me, none of the above did
I was getting this error from our proxy having restrictive rules in place, I was able to add the sites to a whitelist that were being blocked while trying to login.
Some of the sites I whitelisted in Webmarshal were:
*.windows.net
*.msocsp.com
*.ws.symantec.com
*.digicert.com
*.clicktale.net
app.vssps.visualstudio.com
demdex.net
For me it was due wrong system time, after setting correct time it got fixed automatically
I had the problem of not being able to sign in to VS after not using unity for a long time and then updating everything. The way I solved it was to open VS and then click help. This opened the sign in box with 'Personalization Account'. I clicked 'Account options' under the afore mentioned heading, and changed the 'Embedded web browser' to 'System web browser' in the right window. This enabled me to log in via my Edge browser and everything worked fine.
I just fixed it by changing folder to be public.
folder files: "C:\Users{username}\AppData\Local.IdentityService"
right click and choose property and uncheck the hidden and apply it.
If you are under a domain network there is a workaround (quick fix),
Adding or changing the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
ProtectionPolicy = 1 (DWORD)
Check the most recent modified files at %temp%\servicehub\logs.
Check StorageUtilitiesSingleton-10788-lqnuymos-1.log
For an error like this: The computer must be trusted for delegation and the current user account must be configured to allow delegation.
If that is the case this might help you.
I has this issue recently.
Tried all the options above, none worked.
Get it sorted, after repairing Visual Studio, doing all the updates, restart and updated again, restart, another repair and bang! Worked like a charm.
Instead of doing all this, change embedded broswer to system browser so it will works normally in default browser and gets updated in VS.
In VS 2019 enabling System Web Browser instead of Embedded web browser fixed it for me,
Hope this helps someone
https://learn.microsoft.com/en-us/visualstudio/ide/work-with-multi-factor-authentication?view=vs-2019
I tried multiple things above such as
Renaming c:\users[user]\appdata\local.IdentityService
Logging directly in https://login.microsoftonline.com (noticed certificate issues)
Adding https://login.microsoftonline.com to the Trust Sites list in Internet Options
Opening VS as non-admin as well as admin
Reviewed the logs here: %Temp%\servicehub\logs
I also installed Chrome, setting it to the default browser, because many features were saying IE is no longer supported
Reviewing the logs gave me the clue I needed to solve my particular issue. The log stated there was an issue with SSL trust.
Consequently, I ran our local version of rootsupd.exe and installed any related Microsoft root certificates such as the DigiCert Global Root G2 to the Trusted Root Authorities. After rebooting my machine, I noticed VS began recognizing my account and was actually already signed in.
When I tried to validate an App Store build using Xcode 8 I'm getting the following error:
ITunesSoftwareServiceAuthenticationErrorDomain 434.
What does this mean?
I received the same error on multiple attempts. I made some changes (to provisioning profiles etc.) and then validation worked fine a couple of times. But then the error message came back for no apparent reason. Seems like a bug on Apple's side.
Since then I switched to use Application Loader, and with that workflow I have not encountered any problems. Here's how.
In the Xcode Organizer, I do not use "Validate...", but instead "Export..." to save the my_product.ipa file.
Then open Apple's Application Loader (Xcode menu > Open Developer Tool > Application Loader), and with that I upload the my_product.ipa to iTunes Connect.
This process has seemed reliable to me.
Firstly, I received the same error on multiple times. Change some codes, finally release that :
Solution:
unchecked "include bitcode" , then validate (in my case it was successful)
After
Validate with checked "include bitcode"
P.S : Next time, I used XCODE Application Loader. It will be ok for deploy your application.
For what it's worth, this appears to be intermittent. I just received the error and literally did a retry without doing anything else and it worked.
I have seen more reports of this, and some seemingly unrelated but very similar messages from other services. I finally submitted a Code-Level Support Technical Support Incident (TSI). After two days I was told this is not a "code" issue and was credited the TSI i burned when submitting the questions. They got everything they needed to see the problem, but since they called me "John" in their answer, and they clearly saw my name was "Harry", hmm...
the reply, exactly:
Blockquote
Please include the line below in follow-up emails for this request.
Follow-up: 651327438
Hello John,
Thank you for contacting Apple Developer Technical Support (DTS). We provide support for code-level questions on hardware & software development, and are unable to help you with your question. For questions regarding iTunes Connect, we recommend that you first check the iTunes Connect Developer guide.
http://developer.apple.com/library/ios/iTunesConnectGuide
If you are not able to find the information you need in the iTunes Connect Developer Guide and you are still not able to resolve your issue, please direct your inquiry through the iTunes Connect Contact Us system When contacting the iTunes Connect Team, be sure to mention that you were referred by DTS.
Note that some issues with iTunes Connect are transient, and may resolved by waiting a few hours and trying again later.
Bottom Line: I gave up and uploaded the archive. It was accepted. I will update when the app is live.
Quit Xcode and re-login as suggested by members does not work for me. I solved it by using Application Loader.
Steps:
Change the version and build in your app.
Archive again for new file submission and export file to desktop.
Goto top menu: Open Developer Tool > Application Loader (if you don't have this, search, download and install this plug init)
Upload the new version archived file. Done
You will find them in iTunes Connect. From here process to My Apps > Choose the rejected app > Change the version and click on the new uploaded archive file, file will be processing.
Time to resubmit.
Hello Ive sent a version of my app one week ago through Xcode 6 and it didn't have any problem. Today Ive tried to upload a new version of my App via Xcode and when uploading, the progress bar stays in "Sending API usage to Itunes Connect". It doesn't give me any errors, nor warnings, it just stays like that forever.
Ive been looking in google and also in here, and found a lot of solutions (ones more logical than others). Well, Ive tried ALL those solutions, I've created new provision profiles, restarted my computer, restart Xcode, changed "netinfo", connect to new wifi, among others.
Its really driving me crazy since I didn't do anything, it just stopped working.
There are a lot of question with this same topic on the internet (including StackOverflow) and I think there is no one ultimate answer that really explain why this happen. Ive seen very detailed answers but none of them worked for me.
Some of this questions are:
1) Can't Submit App to App Store: “Sending API Usage to iTunes Connect” either times out or loses connection.
2) Application Loader (Apple) stuck on “Sending API usage to iTunes Connect”.
3) Stuck on “Sending API usage to iTunes Connect”.
If I export the archive into an .ipa I can upload it with application loader. I don't know why I can't do it with Xcode. Ive always used Xcode for this.
The reason I want to know how to do it with Xcode is that I don't know if uploading only the .ipa and configuring in app purchases only directly via itunes connect's webpage without doing it in application loader(the button that says "New In-app Purchases" template) , will also work.
I hope someone could help me.
Thank you.
minimise the organiser window
reopen it from mac floating menubar
This seems to be refreshing the connection while online. Works for me.
I had this same problem a few minutes ago, let me explain what I did:
Restart your router/modem
Restart your Mac
Set the active scheme in Xcode for iOS Device
Make a new archive
Validate before submit
These steps work perfectly for me, hope that helps.
I also faced similar problem. I can't upload from my office, but can upload from my home. I assumed that my office's internet connection has problem with Apple server. If you get problem with Xcode to upload, you can download Application Loader separately from iTunes connect and try with that and wait for passing sending api usage state.
Try doing this:
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Seems to be working for a lot of others - https://forums.developer.apple.com/thread/76803
I couldn't make this work on XCode 7.1.
I had to upgrade to 7.1.1, which allowed me to export the binary for App Store Deployment, and then use the Application Loader to upload the app for review.
Absolutely crazy, Apple.
I've found that instead of restarting your router and machine etc, simply clicking 'Renew DHCP Lease' in the TCP/IP settings of your internet device (under Network in System Preferences) solves the issue much quicker and easier, for me anyway.
Just another error that makes working in Apples eco-system all the more fun and exciting...
There was no one particular procedure that seemed to do it in my case: restarted router, restarted Mac, restarted Xcode, recreated profiles on developer website, viewed them in Xcode, recreated archives, attempted just validating for App Store. All of these things over and over again.
My experience has been that you should just kept trying until suddenly it works. Which is sadly not the magic button to click that I was looking for.
Possibly the fact that I managed only twice in the last dozen or so upload attempts in the morning from here in the UK (making it approx 02:30 over there in the US), indicates it's perhaps an iTunes overloaded problem.
I had the same problem, though none of the suggested steps solved my problem, other than using the Application Loader.
However, one thing that bothered me was a warning message saying that:
The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.
It came to me that it might be the reason why Xcode's uploading might be messed up, since it locks at the Sending API usage to iTunes Connect.
Some people mention it in some posts here in stackoverflow.
For me Network is not allowing to upload the build as office wireless is having firewall so I had to move to other wi-fi to upload the build.
Just adding another possible answer here that fixed it for me.
I was on a VPN at work. Disabling this and trying again worked.
I am trying up upload my first app to the store. I had a real issue (wrong syntax on version string) first time so I know I can get as far as validation. When I fixed that issue I now get "Network connect was lost" coming up in the Issues dialog, after quite a pause.
It is not clear if that is a problem with the validation process, between me and apple, or with my app (that does use network connections). My network is pretty solid.
Any ideas what might be happening.
I faced the same issue, then i restart my xcode once. The error gone.
Sometimes Xcode may cause for issues. So use the "Application Loader" to upload app in Appstore.
It is probably caused by unavailability of Apple's servers.
In Apple's developer's forum you can see many people live the same problem at certain times.
The most recent one:
https://discussions.apple.com/message/25437485
So... wait :)
For me, it succeeds after I change the WIFI my MBP joins.
On Mac, all I did was Renew DHCP Lease on my Wifi Information, and it worked.
You might have an Agreement e.g. Paid Apps amendment that you need to agree to.
I started to get this issue this morning, after successfully submitting builds for the same app just last night.
Remembered there was something I had to agree to when I was uploading last night (one of the two made it successfully last night despite this agreement issue).
Restarting XCode didn't help me.
On Mac, I deactivated MalwareBytes and NordVPN. It worked.