I am not able to login into the Appcelerator Studio or using appc cli.
Below is the error message I am getting even after entering the correct credentials.
ERROR | Error: Bad response from login (incorrect user data), please try again.
Unable to install new CLI as well. Below is the command and Error Message.
appc use
ERROR: Download server is not currently available. Please re-try your install again in a few moments. If you continue to have this problem, please contact Appcelerator Support at support#appcelerator.com. [com.appcelerator.install.download.server.unavailable]
I believe appc CLI login is discontinued as Appcelerator is officially discontinued as of March 2022.
The Titanium CLI will let you continue to work.
You can also take a look at this SO post, it might help
But overall, it might be a decent idea to look at other platforms as well. The switch to a different platform was painful and took me about 3 months, but looking back I'm happy I did
Related
I downloaded the app on my laptop and when I tried to open it an error message displays : "The code execution cannot proceed because VCOMP120.DLL was not found. Reinstalling the program may fix this problem." and I reinstalled it many times:(. What can I do to be able to use this application?
Something must be wrong in your Windows installation, according to this post in Microsoft's community.
I'm learning Google Cloud Vision API, but facing some issues. I have completely repeated all the steps from the 'Getting Started' Guide.
download/install google cloud SDK
activate login credentials using gcloud
Set the environment variable GOOGLE_APPLICATION_CREDENTIALS
Install the client library
After that I ran this code and got this error when compiling:
..\cloud.google.com\go\longrunning\autogen\operations_client.go:166:54: cannot use connPool (type "google.golang.org/api/internal".ConnPool) as type *"google.golang.org/grpc".ClientConn in argument to longrunning.NewOperationsClient
Compilation finished with exit code 2
I repeated all the steps over and over and still get this error. Windows 10 is installed on my pc with the latest software updates.
I have NOT changed the code from the tutorial.
Can anyone please tell me why I'm getting this error?
Issue has been fixed.
I just needed to remove conflicting custom imports and re-install Google Vision library.
Well that was a dumb mistake, sorry to bother you.
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
I couldn't be able to login to XCode accounts using my apple ID. It was working before. When I tried to login it shows an error There was an error connecting to Apple ID Server. But I have logged into the same account from another mac without any issue. Please help me with this. I am using XCode version 8.3.3
try these basic ways may be it will help full
Restart your system,sometimes the simplest turning off and on can
fix this error directly.
Sometimes it happens due to the poor Internet connection, check
whether connection is working properly.
Make sure that the date, time, and time zone are set correctly.
Apple discussion says you should check your firewall and antivirus settings - there may be
a similar rule or setting blocking the ID server
In my case, I upgraded my Xcode and Mac OS to the latest version and it started working smoothly
Charles proxy was the cause for me. Make sure you disable/uncheck HTTP( WebProxy) and HTTPS( Secure Web Proxy) and give it a try
My Xcode was working fine until an hour back. Now, it has started acting up. I automatically got logged out of my developer account, of which I am a member. Now, whenever I try to login I am thrown this error.
Your session has expired. Please log in.
Try signing in again or contact Apple Developer Support to resolve account access issues.
I have tried looking into the forums but to no avail.
Apple Forums.
I am unable to make builds because of this. Every time I try to login, it shows up this error.
Does anyone know how to tackle this issue?
Just faced same problem and solution was:
You need to enable Two-factor authentication for Apple ID
Read here how to do this
The same issue happened for me as well. Turning on two factor authentication resolved this issue.
If you have already enabled it, turn it off and then turn it on again and see.
None of the options worked for me, so I contacted Apple developer support. They confirmed that there was an issue at their end and now it's resolved. :)