fastlane-old / fastlane_core Goto Github PK
View Code? Open in Web Editor NEWAll shared code of the fastlane toolchain
Home Page: https://fastlane.tools
All shared code of the fastlane toolchain
Home Page: https://fastlane.tools
When passing boolean options, particularly to the Carthage task, neither true nor false are recognized. Other values (1, yes), capitalizations or quoting don't work, either.
So, if I have something like:
export FL_CARTHAGE_VERBOSE=true
or
export FL_CARTHAGE_USE_SSH=true
the result is
[12:49:17]: ----------------------
[12:49:17]: --- Step: carthage ---
[12:49:17]: ----------------------
[12:49:17]: Error setting value 'true' for option 'use_ssh'
[12:49:17]: Please pass a valid value for use_ssh. Use one of the following: true, false
[12:49:17]: Variable Dump:
[12:49:17]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios routine"}
[12:49:17]: Please pass a valid value for use_ssh. Use one of the following: true, false
See crash report a035c466c2219a7c9c53b1ecca81bfa0
doing a "sudo gem update fastlane" fails due to incompatible version of fastlane_core
As a developer,
I would like to be able to easily detect if fastlane is running in a Jenkins environment vs. locally
So that I can wrap CI environment specific settings.
Usage example:
if Helper.jenkins?
ENV["DEVELOPER_DIR"] = "/Applications/Xcode6.1.app/Contents/Developer"
endif
I noticed one issue when updating Fastlane. One of the machines had an older version installed and gem update fastlane
did not update dependencies properly (it was failing on AppFile
team_id
). I think this happened because fastlane_core.gemspec doesn't specify the exact version of CredentialsManager. And with the 0.1.3
you've added the team_id
parameter which is a new feature.
I think I've had that before as well with some previous update. Maybe it's worth looking through all the versioning schemes in Fastlane tools and make sure they use semantic versioning. At the same time looking through all gemspecs to weed out the exact dependencies.
Hello,
I'm experiencing an issue with fastlane
when its being trigerred by my CI (Gitlab CI). Note that it doesn't happen if I manually launch fastlane
on my CI machine through SSH.
The following stack track appears after the lane finishes successfully:
/path/excon-0.45.4/lib/excon/socket.rb:138:in `select': Interrupt
from /path/excon-0.45.4/lib/excon/socket.rb:138:in `rescue in block in connect'
from /path/excon-0.45.4/lib/excon/socket.rb:119:in `block in connect'
from /path/excon-0.45.4/lib/excon/socket.rb:110:in `each'
from /path/excon-0.45.4/lib/excon/socket.rb:110:in `connect'
from /path/excon-0.45.4/lib/excon/ssl_socket.rb:148:in `connect'
from /path/excon-0.45.4/lib/excon/socket.rb:28:in `initialize'
from /path/excon-0.45.4/lib/excon/ssl_socket.rb:8:in `initialize'
from /path/excon-0.45.4/lib/excon/connection.rb:387:in `new'
from /path/excon-0.45.4/lib/excon/connection.rb:387:in `socket'
from /path/excon-0.45.4/lib/excon/connection.rb:106:in `request_call'
from /path/excon-0.45.4/lib/excon/middlewares/mock.rb:47:in `request_call'
from /path/excon-0.45.4/lib/excon/middlewares/instrumentor.rb:22:in `request_call'
from /path/excon-0.45.4/lib/excon/middlewares/base.rb:15:in `request_call'
from /path/excon-0.45.4/lib/excon/middlewares/base.rb:15:in `request_call'
from /path/excon-0.45.4/lib/excon/middlewares/base.rb:15:in `request_call'
from /path/excon-0.45.4/lib/excon/connection.rb:233:in `request'
from /path/excon-0.45.4/lib/excon.rb:229:in `post'
from /path/fastlane_core-0.16.1/lib/fastlane_core/update_checker.rb:69:in `finished_running'
from /path/fastlane_core-0.16.1/lib/fastlane_core/update_checker.rb:35:in `block in show_update_status'
from /path/fastlane_core-0.16.1/lib/fastlane_core/update_checker.rb:33:in `fork'
from /path/fastlane_core-0.16.1/lib/fastlane_core/update_checker.rb:33:in `show_update_status'
from /path/fastlane-1.26.0/bin/fastlane:135:in `<top (required)>'
from /Users/user/.rbenv/versions/2.2.2/bin/fastlane:23:in `load'
from /Users/user/.rbenv/versions/2.2.2/bin/fastlane:23:in `<main>'
I've had a bit of a look around in the code and it appears to me that this is happening because fastlane
doesn't wait for the forked process that runs the update_checked.finished_running
method to return.
The CI then kills the test shell as soon as fastlane
returns which in turns kills all its child processes (including the one currently making a request) - hence the error.
My current workaround has been to add a sleep statement after fastlane
is executed, but it's obviously not ideal.
I'm no ruby ninja but happy to give a PR a go to fix this. The idea would be to add a waitpid
in update_checked.show_update_status
in order for the parent process to wait on its child.
1.26.0
0.16.2
👏 👏 for Fastlane, what a time saver!
Looking to get fastlane wrapped around AFNetworking, and I am having trouble getting scan
working with tvOS support.
Looking through fastlane core, I think this may be the problem. Is that preventing tvOS simulators from being picked up?
After downloading the existing metadata with ‘deliver’, I had a folder named ‘zh-Hans’ for Simplified Chinese. When I renamed that to ‘cmm-Hans’ as per fastlane-old/snapshot#45, I was unable to upload the metadata.
I guess this Radar has been implemented? https://github.com/fastlane/fastlane_core/blob/d22a109e554312956e8cd0615ee3cc58e3a02bc4/lib/fastlane_core/languages.rb#L9
Origin: fastlane-old/deliver#147
Add a flag to skip storing of user credentials
Getting hanged after checking dependancy.
Sometimes it goes upto three more additional steps: Compiling, Linking and Running Tests> Touching but stops just before the app loads in the simulator (it gives a blank black screen in the simulator in the screen and jumps back to the home screen.
When I press Control+C I get this:
/Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:26:in `each': Interrupt
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:26:in `block in execute'
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:25:in `spawn'
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:25:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:120:in `launch'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:35:in `block (3 levels) in work'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:31:in `each'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:31:in `block (2 levels) in work'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:30:in `each'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:30:in `block in work'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:29:in `each'
from /Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:29:in `work'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/actions/snapshot.rb:17:in `run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:142:in `block (2 levels) in execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/actions/actions_helper.rb:37:in `execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:128:in `block in execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:127:in `chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:127:in `execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/fast_file.rb:149:in `method_missing'
from Fastfile:382:in `block (4 levels) in parsing_binding'
from Fastfile:360:in `each'
from Fastfile:360:in `block (3 levels) in parsing_binding'
from Fastfile:354:in `open'
from Fastfile:354:in `block (2 levels) in parsing_binding'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane.rb:36:in `call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane.rb:36:in `call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:51:in `block in execute'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:46:in `chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:46:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/command_line_handler.rb:30:in `handle'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:37:in `block (2 levels) in run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:155:in `run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:161:in `<top (required)>'
from /usr/local/bin/fastlane:23:in `load'
from /usr/local/bin/fastlane:23:in `<main>'
I noticed that when I delete the builds from the simulator and re-runs them, then they continue a bit more, and exits with error status:
Testing failed:
Test target <AppName>UITests encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **
[15:45:27]: Exit status: 65
I runned without anything in UITests to make sure it is not an error because of some wrong programming code.
Full code:
Testing failed:
Test target <AppName>UITests encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **
[15:45:27]: Exit status: 65
[15:45:28]: Tests failed - check out the log above
[15:45:28]: Backtrace:
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/error_handler.rb:14:in `handle_test_error'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:126:in `block in launch'
/Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:61:in `call'
/Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.32.0/lib/fastlane_core/command_executor.rb:61:in `execute'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:120:in `launch'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:35:in `block (3 levels) in work'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:31:in `each'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:31:in `block (2 levels) in work'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:30:in `each'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:30:in `block in work'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:29:in `each'
/Library/Ruby/Gems/2.0.0/gems/snapshot-1.4.2/lib/snapshot/runner.rb:29:in `work'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/actions/snapshot.rb:17:in `run'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:142:in `block (2 levels) in execute_action'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/actions/actions_helper.rb:37:in `execute_action'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:128:in `block in execute_action'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:127:in `chdir'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:127:in `execute_action'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/fast_file.rb:149:in `method_missing'
Fastfile:382:in `block (4 levels) in parsing_binding'
Fastfile:360:in `each'
Fastfile:360:in `block (3 levels) in parsing_binding'
Fastfile:354:in `open'
Fastfile:354:in `block (2 levels) in parsing_binding'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane.rb:36:in `call'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane.rb:36:in `call'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:51:in `block in execute'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:46:in `chdir'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/runner.rb:46:in `execute'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/lib/fastlane/command_line_handler.rb:30:in `handle'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:37:in `block (2 levels) in run'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
/Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:155:in `run'
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.48.0/bin/fastlane:161:in `<top (required)>'
/usr/local/bin/fastlane:23:in `load'
/usr/local/bin/fastlane:23:in `<main>'
But it doesn't exit here. Instead it does the run for the next language, runs upto "checking dependency", and then stands there stuck, and then I have to exit using Control+C. When it exits, it shows the previous error of "Exit status 65".
I recently used deliver trying to upload an ipa file. deliver failed with the following output
/Library/Ruby/Gems/2.0.0/gems/deliver-1.7.0/lib/deliver/detect_values.rb:28:
in `find_app': Could not find app with app identifier 'some.weird.identifier.dev' in your iTunes Connect account
Since the identifier was totally wrong and normally used for another build i checked the Info.plist
file in my Ipa file and there wasn't the identifier listed as stated above.
Diggin more into it i found out that this ipa bundle contained more Plist files in the App directory:
/MyApp.ipa/Payload/MyApp.app ls | grep '.*\.plist'
DMailApp-Info.plist
DMailAppEnterprise-Info.plist
DMailAppProdEnterprise-Info.plist
DMailAppVTU-Info.plist
Info.plist
ResourceRules.plist
mimetypes.plist
The IPA File Analyser seems to grab the wrong plist (not the Info.plist) and if its structured like an "Info.plist" it reads out its properties and uses them instead.
i know these other plist files shouldn't exist in the best case and they are not neccessary for the project, but they COULD exist (like in my case, i'm not the maintainer of that app but i'm uploading it). Removing the unused plist files except the "Info.plist" fixes the issue.
I have seen this issue with using the resign action of Fastlane. I build the ipa and then move it. I then pass the new location to the resign action, which then fails in verify_default_value_matches_verify_block
with a message Invalid default value for ipa, doesn't match verify_block
. This doesn't seem right that the default value needs to be verified if I have supplied an override value that passes the verfiy block
I just realized this is currently an issue with his PR - fastlane/fastlane#206. I call values
because we just merge the things together but it won't load any defaults, ENV values, or action values. I am suggesting that we change values
to fetch all the values or maybe specify an array of values to call fetch on.
https://github.com/KrauseFx/fastlane_core/blob/master/lib/fastlane_core/configuration.rb#L13
@KrauseFx Let me know if that doesn't make sense 😇
I'm getting the following exception when trying to run the produce
tool as part of my dashlane
setup: Looks like your login data was correct, but you do not have access to the apps.
. Just to be clear, the account definitely has access to creating apps.
Here is my Dashfile, here is my trace and here is the error image.
After digging into the source code, I think it might have something to do with the 'wait' conditions being incorrect.
Perhaps wait_for_elements('.ng-scope')
is being called prematurely? Perhaps the page is loading in fragments, so on a slower connection an ng-scope
item might be rendered onto the page before the whole page (and "My Apps" label) has loaded.
Could we replace that generic test with something else? Is this something you've already explored? I'll investigate whether there are any other defining characteristics we could work from.
@milch was already working on this. This would improve all commands, especially deliver --help
and similar.
When the iTunes Connect user's password contains an >
character, uploading builds using ItunesTransporter fails with [Transporter Error Output]: Your Apple ID or password was entered incorrectly. (-20101)
The password works fine in the iTunes Connect login happing right before the upload is initiated.
I suspect the Shellwords.escape
in shell_escaped_password
is doing some shenanigans here?
See https://github.com/KrauseFx/fastlane_core/blob/master/lib/fastlane_core/configuration.rb#L67
I'd send a pull request for this, but I'm not sure if thats intended or how far reaching the change would be.
The issue fastlane-old/snapshot#341 is believed to be caused by fastlane_core option processing (in commander_generator) not able to process list / array command line options.
fastlane_code should specify "Array" to commander-rb/commander (and ruby OptionParser) for correct interpretation.
The issue gym hangs on xcrun #143 had a pull request add a 10s timeout to avoid xcode 6 possible hangs as detection for when shared schemes don't exist and the command hangs.
However, on slower build machines this 10s is too short and ends up failing the build with the message about shared schemes.
Hi all,
I would like to iterate over a list of accounts and renew APNS certificates like the script attached but it seems that once logged in on DevPortal with account1, event if I call CredentialsManager::PasswordManager.logout, I keep logged as account1 so APNS renewal fails. It could be nice if we could be logged out from DevCenter when calling CredentialsManager::PasswordManager.logout or if we had a logout func to force it to log out.
Thank you !
Updating APNS for : com.foo.bar
[15:21:19]: Refreshing push notification profiles for app 'com.foo.bar'
[15:21:22]: Login into iOS Developer Center
Uncaught exception: Could not find app with identifier 'com.foo.bar' on apps page. The identifier is case sensitive.
/Library/Ruby/Gems/2.0.0/gems/pem-0.6.4/lib/pem/developer_center.rb:70:in `open_app_page'
/Library/Ruby/Gems/2.0.0/gems/pem-0.6.4/lib/pem/developer_center.rb:14:in `fetch_cer_file'
/Library/Ruby/Gems/2.0.0/gems/pem-0.6.4/lib/pem/cert_manager.rb:15:in `run'
/Library/Ruby/Gems/2.0.0/gems/pem-0.6.4/lib/pem/manager.rb:5:in `start'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:40:in `block (2 levels) in <class:ProfileList>'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:31:in `each'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:31:in `block in <class:ProfileList>'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:20:in `each'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:20:in `<class:ProfileList>'
/Users/romainbiard/RubymineProjects/untitled/profile_list.rb:14:in `<top (required)>'
When using fastlane 1.33.0 and fastlane_core 0.22.2, gym fails during code signing on my build server without much error output:
▸ Touching ios
▸ Signing /Users/me/Library/Developer/Xcode/DerivedData/app-eyotgxjqqvlmyggemmozymvbmkgu/Build/Intermediates/ArchiveIntermediates/app/InstallationBuildProductsLocation/Applications/app.app
▸ Touching ios
�[37m[17:22:34]: �[0mExit status: 1
When downgrading to fastlane 1.32.4 and fastlane_core 0.22.1 it all works as expected. I don't know exactly what's wrong, but my guess is it has something to do with this commit: eb0fb63
Locally it does work with the latest versions of fastlane, so I don't know exactly what's wrong, but it may be relevant that I'm using the use_legacy_build_api: true
build option of gym
I've noticed that users have issues when they use an old fastlane_core. In particular if Apple broke the login process. It would be beneficial for the core to detect it is out of date and notify the users. So maybe this: https://fastlane-refresher.herokuapp.com/ should support fastlane_core ?
I was given this exception when response from apple is nil
/Users/ericraio/.rvm/gems/ruby-2.1.5/gems/json-1.8.2/lib/json/common.rb:155:in `initialize': no implicit conversion of nil into String (TypeError)
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/json-1.8.2/lib/json/common.rb:155:in `new'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/json-1.8.2/lib/json/common.rb:155:in `parse'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane_core-0.7.5/lib/fastlane_core/developer_center/developer_center_helper.rb:25:in `post_ajax'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/developer_center.rb:66:in `maintain_app_certificate'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/developer_center.rb:93:in `block in maintain_app_certificate'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/developer_center.rb:75:in `each'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/developer_center.rb:75:in `maintain_app_certificate'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/developer_center.rb:18:in `run'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/sigh-0.5.2/lib/sigh/manager.rb:6:in `start'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/actions/sigh.rb:20:in `run'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/fast_file.rb:112:in `block (2 levels) in method_missing'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/actions/actions_helper.rb:51:in `execute_action'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/fast_file.rb:94:in `block in method_missing'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/fast_file.rb:93:in `chdir'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/fast_file.rb:93:in `method_missing'
from (eval):70:in `block (3 levels) in parse'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/runner.rb:35:in `call'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/runner.rb:35:in `block in execute'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/runner.rb:25:in `chdir'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/runner.rb:25:in `execute'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/lib/fastlane/lane_manager.rb:33:in `cruise_lane'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/bin/fastlane:39:in `block (2 levels) in run'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/command.rb:178:in `call'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/command.rb:178:in `call'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/command.rb:153:in `run'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/runner.rb:428:in `run_active_command'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/runner.rb:68:in `run!'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/commander-4.3.4/lib/commander/delegates.rb:15:in `run!'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/bin/fastlane:118:in `run'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/gems/fastlane-1.3.0/bin/fastlane:124:in `<top (required)>'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/bin/fastlane:23:in `load'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/bin/fastlane:23:in `<main>'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'
from /Users/ericraio/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `<main>'
In this method here, we need something like a nil check before parsing json and set up a retry?
def post_ajax(url, data = nil)
JSON.parse(page.evaluate_script("$.ajax({type: 'POST', url: '#{url}', async: false#{data.nil? ? '' : ", data: #{data}"} })")['responseText'])
end
As of 9/22/15 - when uploading ipa's to itunes connect the prerelease page has an initial status of "Uploaded" and then a status of "Processing".
Making the following change to wait_for_preprocessing in itunes_connect_helper.rb does the right thing...
old - while page.has_content? "Uploaded"
new - while page.has_content? "Uploaded" or page.has_content? "Processing"
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.