I'm trying to config automatically build iOS apps using Expo through Gitlab-CI.
This are the commands that I am using:
expo login -u expo_user -p expo_pass
expo build:ios --non-interactive --apple-id my_id#domain.com --clear-dist-cert --clear-provisioning-profile --dist-p12-path "path_to_file.p12" --provisioning-profile-path "path_to_file.mobileprovision"
I am already passing the respective values of this env vars:
EXPO_APPLE_PASSWORD
EXPO_IOS_DIST_P12_PASSWORD
During the 2nd command execution it launch this logs:
[14:24:23] Trying to authenticate with Apple Developer Portal...
[14:24:25] Authentication with Apple Developer Portal failed!
[14:24:25] Error: Reason: Unknown reason, raw: "<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>Apple</center>\r\n</body>\r\n</html>\r\n\n"
at runAction (/expo-cli#3.13.1/src/appleApi/fastlane.ts:28:17)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at Object.authenticate (/expo-cli#3.13.1/src/appleApi/authenticate.ts:46:40)
at IOSBuilder.getAppleCtx (/expo-cli#3.13.1/src/commands/build/ios/IOSBuilder.js:47:23)
at IOSBuilder.produceMissingCredentials (/expo-cli#3.13.1/src/commands/build/ios/IOSBuilder.js:123:22)
at IOSBuilder.prepareCredentials (/expo-cli#3.13.1/src/commands/build/ios/IOSBuilder.js:65:7)
at IOSBuilder.run (/expo-cli#3.13.1/src/commands/build/ios/IOSBuilder.js:19:7)
at IOSBuilder.command (/expo-cli#3.13.1/src/commands/build/BaseBuilder.js:55:7)
at Command.<anonymous> (/expo-cli#3.13.1/src/exp.ts:81:7)
The Apple Developer account that I am using have configured the Two Factor Authentication (2FA).
Is this the reason why the expo build:ios command is failing the auth against Apple Portal?
What am I missing in this commands?
PS: These commands on my laptop works fine!
A similar issue was happening to me in interactive mode on my dev machine.
One thing that happened to work for me was logging into App Store Connect in an incognito window to trigger the 2FA. Not sure if it's a coincidence, but it worked!
For reference, I was getting a similar error on the latest expo-cli#4.9.1
✖ Logging in...
Authentication with Apple Developer Portal failed!
Error: Apple Service Error -1018. Could Not Complete Request. Your request could not be completed because of an error. Please try again later. Apple servers may be down right
now, please try again in about 10-20 minutes
In addition to the other answers, also ensure that a VPN or site-blocking software is not activated, which was the cause of my issue.
Not a very satisfying answer, but it worked for me: Delete your node_modules and then reinstall all your dependencies.
We had no problem last week, but today we kept hitting this error.
This possible fix has zero risk as long as you have a yarn.lock or NPM's equivalent so that you can be sure the versions you download match the originals.
You Need To Use expo build:ios --clear-credentials it worked fine for me.
As Specified bellow in link.
-c, --clear-credentials Clear all credentials stored on Expo servers.
https://forums.expo.io/t/solved-ios-standalone-build-failed/10007/3?u=alihussnain
Related
I am trying to deploy iOS application automatically with fastlane under CircleCI. Unfortunately it wants 2-factor authentication. I am trying to do on my development machine:
fastlane spaceauth -u my#email.com
and it sends me code by mobile phone, i.e. password is correct and valid. Unfortunately, after I enter the code, it says me
Requesting session...
Could not login to App Store Connect
Please check your credentials and try again.
This could be an issue with App Store Connect,
Please try unsetting the FASTLANE_SESSION environment variable
(if it is set) and re-run `fastlane spaceauth`
Exception type: Spaceship::AccessForbiddenError
How to fix that?
I am running Xcode 9.1 and recently rebooted my computer. Prior to rebooting I could run the simulator with no problems. After rebooting I get this message.
"Enter the name and password of a user in the developer tools group"
I am running this on my own personal machine (provided by my school) and should have administrator access with my login.
I have looked at other posts relating to this message and attempted the following solutions to no avail.
When I run "DevToolsSecurity ~enable" it tells me that developer mode is already enabled.
When I run "sudo dscl . append /Groups/_developer GroupMembership myUserName"
I got a message saying my user name was not in the subdoers file.
I am at a total loss on how to resolve this problem and admit that I am not a professional programmer. I am just a guy who is trying to figure out how to write some basic apps using Xcode. Any help would be GREATLY APPRECIATED!
Everything about what you’ve written indicates that you do not have administrative access to your machine. You can confirm this from System Preferences -> Users & Groups or checking the output of running ‘id’ from Terminal (you’ll probably not see the admin group listed).
I have on digitalocean my meteor application running but when I try and test on my iphone the app I am not able to see the login screen.
I don't think it's version dependent and I therefore do not list them. I am happy to provide all the config files if this helps but want to make sure that I am not missing anything conceptually.
My setup is that on my digitalocean (not real URL: https://ABC123.com) server I run the meteor app and the app works fine at the URL. The meteor application has been deployed a while back and is a different release from what I am testing now locally. Source code is quite similar though and it never worked on the iphone. nginx is used to forward the URL domain to
proxy_pass http://127.0.0.1:3100;
Here is the issue now:
I run from my local mac:
meteor run ios-device --mobile-server https://ABC123.com
and run from xcode on the simulator or my iphone and get the attached screenshot. You can see that there is no login prompt which I believe is caused that I do not connect to the server on digitalocean.
It's a also surprising that with the command meteor runs on localhost:3000 as well. But it's probably not the issue.
The way it should look is the below which is taken from the web page:
Thanks already in advance for any responses.
This is resolved. Using Safari as a debugger I noticed that the connection to the server failed due to a non AC SSL certificate. So, after I fixed the SSL certificates it does connect now.
I setup a copy of OSX server and correctly configured it with Xcode. I was able to create a bot and run a few integrations which failed because I didn't import the correct developer certificates. Running an integration now it seems to be stuck at "Getting sources.." while Xcode is showing it as being queued. Any ideas?
There are lot of reasons this might be happening and it depends on what version control system you are using. For both git and svn the issue might be the root ssl certificates. You need to add the root certificates from your keychain to your ssl configuration.
See this post for details.
If the problem isn't SSL certificate related then it will likely be a timeout issue fetching your source repository if it is very large. Check your integration logs for details.
This question might be considered duplicate of this: Unable to use heroku gem cli after password changes, but it is not.
In my case I have the latest Mac OS X 10.8.3 and I've installed brand new Heroku tool belt. First thing I've tried is to authenticate by issuing this:
heroku login
I was asked for my Heroku credentials, which I've entered (many-many times), but I got "Authentication Failed" message.
I've tried signing in with my credentials to Heroku website multiple times from different browsers - it all works, but I can't authenticate with Heroku CLI.
I don't have ~/.netrc file, I don't have any fancy firewall software on my Mac. What am I possibly doing wrong?
Thanks,
Alex.
Update 03/18/2013 9 PM Mountain:
This is the Heroku issue and they are looking into it:
Sounds like it might be an SSH key issue.
Here is a good guide to resolving it.
https://devcenter.heroku.com/articles/keys
Heroku engineers have fixed it and I was able to authenticate. Thank you, Heroku!