Gym Distribution Certificate nightmare, two different apps try to use same Distribution Certificate...

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I have two apps I try to build them with a Macmini slave. Summary of the problem is gym can't detect the correct Distribution Certificate to archive the app.
We have only one admin account that creates certificates, one team_id.
Followed all the suggestions in the https://docs.fastlane.tools/actions/match/
Both apps are created with following commands.
fastlane match appstore

and
fastlane match adhoc

Both apps shares the same git repo but different branches.
Matchfile  for mobilev2 app
git_url "git@gitlab01a.mycompany.com:Incubator/Hugin-IOS-Certificates.git"
git_branch "MobileV2"

type "development" # The default type, can be: appstore, adhoc or development

app_identifier [
    "com.mycompany.nightly.v2",
    "com.mycompany.beta.v2",
    "com.mycompany.endeavor"
]

username<EMAIL_ADDRESS># Your Apple Developer Portal username

Matchfile  for hugin app
git_url "git@gitlab01a.mycompany.com:Incubator/Hugin-IOS-Certificates.git"
git_branch "Hugin"

type "development" # The default type, can be: appstore, adhoc or development

app_identifier [
    "com.mycompany.Hugin"
]

username<EMAIL_ADDRESS># Your Apple Developer Portal username

Then obviously match creates the Two Distribution Certificates, with the same name... I think that is the cause of the problem. Team_id is the same and Distribution Certificate name is the same

In the login.keychain, I can see both Distrubiton Certificates are installed, both of them have the exact same name just different expiration dates.
iPhone Distribution: mycompany, LLC. (B34U44J9D6)
iPhone Distribution: mycompany, LLC. (B34U44J9D6)

The error I get is
INFO [2018-02-12 11:21:28.12]: ▸ Code Signing Error: Provisioning profile "match AdHoc com.mycompany.endeavor" doesn't include signing certificate "iPhone Distribution: mycompany, LLC. (B34U44J9D6)".
INFO [2018-02-12 11:21:28.12]: ▸ Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.2'

but If I open Xcode manually I can see that match installed correct profiles.
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc' to '99151e4c-7b3d-402b-ad10-15df7fe0607e'
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc_team-id' to 'B34U44J9D6'
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc_profile-name' to 'match AdHoc com.mycompany.endeavor'

Solutions I have tried:

Manually delete one of the Distribution Certificates from the login.Keychain. THIS WORKS: however this defeats the purpose.... Whole point is to automate and using Jenkins and a macmini to push the builds out.....

Create two keychains:

  lane :beta do |options|
    cocoapods

    create_keychain(
      name: 'mobilev2.keychain',
      unlock: true,
      timeout: false,
      lock_when_sleeps: true,
      password: 'password'
    )

    unlock_keychain(path:"mobilev2.keychain", password: ENV["MATCH_PASSWORD"])
    sh "security set-keychain-settings -t 3600 -l ~/Library/Keychains/mobilev2.keychain"

    # https://stackoverflow.com/questions/39868578/security-codesign-in-sierra-keychain-ignores-access-control-settings-and-ui-p/40039594#40039594
    sh "security set-key-partition-list -S apple-tool:,apple: -s -k password mobilev2.keychain"

    register_devices(devices_file: "./fastlane/devices.txt")
    match(type: "adhoc", keychain_name:"mobilev2.keychain", force_for_new_devices: true)

Well this doesn't work for because again neither match or gym uses the newly created keychains...

my gym looks like
    gym(
      scheme: options[:scheme],
      workspace:options[:workspace]
    )

I have already wasted 3 days solving and going thru previous fastlane issues....
How do I use fastlane for multiple apps in the same team_id ?
Complete output when running fastlane, including the stack trace and command used

MHDs-Mac-mini:fastlane mhddeveloper$ fastlane beta --verbose
fastlane update available
Please run `brew update && brew cask reinstall fastlane`
[11:20:43]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
DEBUG [2018-02-12 11:20:43.57]: Checking if there are any plugins that should be loaded...
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:43.80]: ----------------------------------------
INFO [2018-02-12 11:20:43.80]: --- Step: Verifying fastlane version ---
INFO [2018-02-12 11:20:43.80]: ----------------------------------------
INFO [2018-02-12 11:20:43.80]: Your fastlane version 2.80.0 matches the minimum requirement of 2.19.1  ✅
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:43.87]: ------------------------------
INFO [2018-02-12 11:20:43.87]: --- Step: default_platform ---
INFO [2018-02-12 11:20:43.87]: ------------------------------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:43.87]: Driving the lane 'ios beta' 🚀
INFO [2018-02-12 11:20:43.88]: ---------------------------------
INFO [2018-02-12 11:20:43.88]: --- Step: echo $FASTLANE_USER ---
INFO [2018-02-12 11:20:43.88]: ---------------------------------
INFO [2018-02-12 11:20:43.88]: $ echo $FASTLANE_USER
INFO [2018-02-12 11:20:43.89]: -----------------------------------------------------
INFO [2018-02-12 11:20:43.89]: Step: if [ -d ../DerivedData ]; then rm -r ../DerivedData; fi
INFO [2018-02-12 11:20:43.89]: -----------------------------------------------------
INFO [2018-02-12 11:20:43.89]: $ if [ -d ../DerivedData ]; then rm -r ../DerivedData; fi
INFO [2018-02-12 11:20:43.90]: -----------------------------------------------------
INFO [2018-02-12 11:20:43.90]: Step: if [ -d test_output ]; then rm -r test_output; fi
INFO [2018-02-12 11:20:43.90]: -----------------------------------------------------
INFO [2018-02-12 11:20:43.90]: $ if [ -d test_output ]; then rm -r test_output; fi
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:43.94]: -----------------------
INFO [2018-02-12 11:20:43.94]: --- Step: cocoapods ---
INFO [2018-02-12 11:20:43.94]: -----------------------
INFO [2018-02-12 11:20:43.99]: gem 'cocoapods' is already installed
INFO [2018-02-12 11:20:43.99]: $ pod install
INFO [2018-02-12 11:20:46.15]: ▸ Analyzing dependencies
INFO [2018-02-12 11:20:46.15]: ▸ Downloading dependencies
INFO [2018-02-12 11:20:46.15]: ▸ Using Insert (<IP_ADDRESS>7)
INFO [2018-02-12 11:20:46.15]: ▸ Using Intercom (3.1.5)
INFO [2018-02-12 11:20:46.15]: ▸ Generating Pods project
INFO [2018-02-12 11:20:46.16]: ▸ Integrating client project
INFO [2018-02-12 11:20:47.32]: ▸ Sending stats
INFO [2018-02-12 11:20:47.33]: ▸ Pod installation complete! There are 2 dependencies from the Podfile and 2 total pods installed.
INFO [2018-02-12 11:20:47.33]: ▸ [!] The `mycompany [Debug]` target overrides the `LD_RUNPATH_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-mycompany/Pods-mycompany.debug.xcconfig'. This can lead to problems with the CocoaPods installation
INFO [2018-02-12 11:20:47.33]: ▸ [!] The `mycompany [Release]` target overrides the `LD_RUNPATH_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-mycompany/Pods-mycompany.release.xcconfig'. This can lead to problems with the CocoaPods installation
INFO [2018-02-12 11:20:47.37]: ▸ - Use the `$(inherited)` flag, or
INFO [2018-02-12 11:20:47.37]: ▸ - Remove the build settings from the target.
INFO [2018-02-12 11:20:47.37]: ▸ - Use the `$(inherited)` flag, or
INFO [2018-02-12 11:20:47.37]: ▸ - Remove the build settings from the target.
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:47.50]: -----------------------------
INFO [2018-02-12 11:20:47.50]: --- Step: unlock_keychain ---
INFO [2018-02-12 11:20:47.50]: -----------------------------
WARN [2018-02-12 11:20:47.54]: To not be asked about this value, you can specify it using 'password'
 [2018-02-12 11:20:47.54]: Keychain password: ********
INFO [2018-02-12 11:20:55.17]: Unlocking keychain at path: /Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:55.23]: -----------------------------------------------------
INFO [2018-02-12 11:20:55.23]: Step: security set-keychain-settings -t 3600 -l ~/Library/Keychains/mobilev2.keychain
INFO [2018-02-12 11:20:55.23]: -----------------------------------------------------
INFO [2018-02-12 11:20:55.23]: $ security set-keychain-settings -t 3600 -l ~/Library/Keychains/mobilev2.keychain
INFO [2018-02-12 11:20:55.28]: -----------------------------------------------------
INFO [2018-02-12 11:20:55.28]: Step: security set-key-partition-list -S apple-tool:,apple: -s -k mhdhappy mobilev2.keychain
INFO [2018-02-12 11:20:55.28]: -----------------------------------------------------
INFO [2018-02-12 11:20:55.28]: $ security set-key-partition-list -S apple-tool:,apple: -s -k mhdhappy mobilev2.keychain
INFO [2018-02-12 11:20:55.47]: ▸ keychain: "/Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db"
INFO [2018-02-12 11:20:55.61]: ▸ keychain: "/Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db"
INFO [2018-02-12 11:20:55.61]: ▸ version: 512
INFO [2018-02-12 11:20:55.61]: ▸ class: 0x00000010
INFO [2018-02-12 11:20:55.62]: ▸ attributes:

Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:20:55.74]: ------------------------------
INFO [2018-02-12 11:20:55.74]: --- Step: register_devices ---
INFO [2018-02-12 11:20:55.74]: ------------------------------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
WARN [2018-02-12 11:20:55.93]: To not be asked about this value, you can specify it using 'username'
 [2018-02-12 11:20:55.93]: Optional: Your Apple ID<EMAIL_ADDRESS>Loading session from<EMAIL_ADDRESS>INFO [2018-02-12 11:21:08.08]: Fetching list of currently registered devices...
INFO [2018-02-12 11:21:08.37]: Successfully registered new devices.
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:21:08.40]: -------------------
INFO [2018-02-12 11:21:08.40]: --- Step: match ---
INFO [2018-02-12 11:21:08.40]: -------------------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:21:08.45]: Successfully loaded '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Matchfile' 📄

+----------------+--------------------------------------+
|      Detected Values from './fastlane/Matchfile'      |
+----------------+--------------------------------------+
| git_url        | git@gitlab01a.mycompany.com:Incubat  |
|                | or/Hugin-IOS-Certificates.git        |
| git_branch     | MobileV2                             |
| type           | development                          |
| app_identifier | ["com.mycompany.nightly.v2",         |
|                | "com.mycompany.beta.v2",             |
|                | "com.mycompany.endeavor"]            |
| username       |<EMAIL_ADDRESS>             |
+----------------+--------------------------------------+

+-----------------------+--------------------------------------+
|                   Summary for match 2.80.0                   |
+-----------------------+--------------------------------------+
| type                  | adhoc                                |
| keychain_name         | mobilev2.keychain                    |
| force_for_new_devices | true                                 |
| git_url               | git@gitlab01a.mycompany.com:Incubat  |
|                       | or/Hugin-IOS-Certificates.git        |
| git_branch            | MobileV2                             |
| app_identifier        | ["com.mycompany.nightly.v2",         |
|                       | "com.mycompany.beta.v2",             |
|                       | "com.mycompany.endeavor"]            |
| username              |<EMAIL_ADDRESS>             |
| readonly              | false                                |
| team_id               | B34U44J9D6                           |
| verbose               | false                                |
| force                 | false                                |
| skip_confirmation     | false                                |
| shallow_clone         | false                                |
| clone_branch_directly | false                                |
| skip_docs             | false                                |
| platform              | ios                                  |
+-----------------------+--------------------------------------+

INFO [2018-02-12 11:21:08.48]: Cloning remote git repo...
INFO [2018-02-12 11:21:08.48]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
INFO [2018-02-12 11:21:08.48]: $ GIT_TERMINAL_PROMPT=0 git clone 'git@gitlab01a.mycompany.com:Incubator/Hugin-IOS-Certificates.git' '/var/folders/7q/nbjwjbbs1sdbhfltcw1hs9t00000gn/T/d20180212-78351-5a9din'
INFO [2018-02-12 11:21:08.50]: ▸ Cloning into '/var/folders/7q/nbjwjbbs1sdbhfltcw1hs9t00000gn/T/d20180212-78351-5a9din'...
INFO [2018-02-12 11:21:08.96]: ▸ remote: Counting objects: 471, done.
INFO [2018-02-12 11:21:08.98]: ▸ remote: Compressing objects: 100% (383/383), done.
INFO [2018-02-12 11:21:09.18]: ▸ remote: Total 471 (delta 66), reused 457 (delta 57)
INFO [2018-02-12 11:21:09.18]: ▸ Receiving objects: 100% (471/471), 1.18 MiB | 0 bytes/s, done.
INFO [2018-02-12 11:21:09.19]: ▸ Resolving deltas: 100% (66/66), done.
INFO [2018-02-12 11:21:09.23]: ▸ Checking connectivity... done.
INFO [2018-02-12 11:21:09.24]: $ git --no-pager branch --list origin/MobileV2 --no-color -r
INFO [2018-02-12 11:21:09.26]: ▸ origin/MobileV2
INFO [2018-02-12 11:21:09.26]: Checking out branch MobileV2...
INFO [2018-02-12 11:21:09.26]: $ git checkout MobileV2
INFO [2018-02-12 11:21:09.29]: ▸ Branch MobileV2 set up to track remote branch MobileV2 from origin.
INFO [2018-02-12 11:21:09.29]: ▸ Switched to a new branch 'MobileV2'
INFO [2018-02-12 11:21:09.37]: 🔓  Decrypted '395GCB2ZL4.cer'
INFO [2018-02-12 11:21:09.45]: 🔓  Decrypted '8KQRUFN5J7.cer'
INFO [2018-02-12 11:21:09.52]: 🔓  Decrypted '395GCB2ZL4.p12'
INFO [2018-02-12 11:21:09.59]: 🔓  Decrypted '8KQRUFN5J7.p12'
INFO [2018-02-12 11:21:09.67]: 🔓  Decrypted 'AdHoc_com.mycompany.beta.v2.mobileprovision'
INFO [2018-02-12 11:21:09.75]: 🔓  Decrypted 'AdHoc_com.mycompany.endeavor.mobileprovision'
INFO [2018-02-12 11:21:09.83]: 🔓  Decrypted 'AdHoc_com.mycompany.nightly.v2.mobileprovision'
INFO [2018-02-12 11:21:09.90]: 🔓  Decrypted 'AppStore_com.mycompany.beta.v2.mobileprovision'
INFO [2018-02-12 11:21:09.98]: 🔓  Decrypted 'AppStore_com.mycompany.endeavor.mobileprovision'
INFO [2018-02-12 11:21:10.06]: 🔓  Decrypted 'AppStore_com.mycompany.nightly.v2.mobileprovision'
INFO [2018-02-12 11:21:10.15]: 🔓  Decrypted 'Development_com.mycompany.beta.v2.mobileprovision'
INFO [2018-02-12 11:21:10.21]: 🔓  Decrypted 'Development_com.mycompany.endeavor.mobileprovision'
INFO [2018-02-12 11:21:10.28]: 🔓  Decrypted 'Development_com.mycompany.nightly.v2.mobileprovision'
INFO [2018-02-12 11:21:10.28]: 🔓  Successfully decrypted certificates repo
INFO [2018-02-12 11:21:10.34]: Verifying that the certificate and profile are still valid on the Dev Portal...
Loading session from<EMAIL_ADDRESS>INFO [2018-02-12 11:21:11.74]: Installing certificate...
INFO [2018-02-12 11:21:11.74]: $ security list-keychains -d user
INFO [2018-02-12 11:21:11.75]: ▸     "/Users/mhddeveloper/Library/Keychains/login.keychain-db"
INFO [2018-02-12 11:21:11.75]: ▸     "/Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db"
INFO [2018-02-12 11:21:11.75]: ▸     "/Users/mhddeveloper/Library/Keychains/hugin.keychain-db"
INFO [2018-02-12 11:21:11.75]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /Users/mhddeveloper/Library/Keychains/login.keychain-db
INFO [2018-02-12 11:21:11.78]: ▸ keychain: "/Users/mhddeveloper/Library/Keychains/login.keychain-db"
INFO [2018-02-12 11:21:11.78]: ▸ version: 512
INFO [2018-02-12 11:21:11.78]: ▸ class: 0x80001000
INFO [2018-02-12 11:21:11.78]: ▸ attributes:
INFO [2018-02-12 11:21:11.78]: ▸     "alis"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2018-02-12 11:21:11.78]: ▸     "cenc"<uint32>=0x00000003
INFO [2018-02-12 11:21:11.78]: ▸     "ctyp"<uint32>=0x00000001
INFO [2018-02-12 11:21:11.78]: ▸     "hpky"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2018-02-12 11:21:11.78]: ▸     "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204341  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\024\006\003U\004\003\023\015APPLE ROOT CA"
INFO [2018-02-12 11:21:11.78]: ▸     "labl"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2018-02-12 11:21:11.78]: ▸     "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2018-02-12 11:21:11.78]: ▸     "snbr"<blob>=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2018-02-12 11:21:11.78]: ▸     "subj"<blob>=0x308196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697479  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\014;Apple Worldwide Developer Relations Certification Authority"
DEBUG [2018-02-12 11:21:12.09]: Certificate '8KQRUFN5J7.cer' is already installed on this machine
INFO [2018-02-12 11:21:12.09]: $ security import /var/folders/7q/nbjwjbbs1sdbhfltcw1hs9t00000gn/T/d20180212-78351-5a9din/certs/distribution/8KQRUFN5J7.p12 -k '/Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db' -P '' -T /usr/bin/codesign -T /usr/bin/security
security: SecKeychainItemImport: The specified item already exists in the keychain.
INFO [2018-02-12 11:21:12.17]: $ security set-key-partition-list -S apple-tool:,apple: -k '' /Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db
security: SecKeychainItemSetAccessWithPassword: The user name or passphrase you entered is not correct.
INFO [2018-02-12 11:21:12.22]: ▸ keychain: "/Users/mhddeveloper/Library/Keychains/mobilev2.keychain-db"
INFO [2018-02-12 11:21:12.22]: ▸ version: 512
INFO [2018-02-12 11:21:12.22]: ▸ class: 0x00000010
INFO [2018-02-12 11:21:12.22]: ▸ attributes:
INFO [2018-02-12 11:21:12.22]: ▸     0x00000000 <uint32>=0x00000010
INFO [2018-02-12 11:21:12.22]: ▸     0x00000001 <blob>="Imported Private Key"
INFO [2018-02-12 11:21:12.22]: ▸     0x00000002 <blob>=<NULL>
INFO [2018-02-12 11:21:12.22]: ▸     0x00000003 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000004 <uint32>=0x00000000
INFO [2018-02-12 11:21:12.22]: ▸     0x00000005 <uint32>=0x00000000
INFO [2018-02-12 11:21:12.22]: ▸     0x00000006 <blob>=0xD8A21CFA5436320D3B533A6CB4B7F1FDA1E53056  "\330\242\034\372T62\015;S:l\264\267\361\375\241\3450V"
INFO [2018-02-12 11:21:12.22]: ▸     0x00000007 <blob>=<NULL>
INFO [2018-02-12 11:21:12.22]: ▸     0x00000008 <blob>=0x7B38373139316361322D306663392D313164342D383439612D3030303530326235323132327D00  "{87191ca2-0fc9-11d4-849a-000502b52122}\000"
INFO [2018-02-12 11:21:12.22]: ▸     0x00000009 <uint32>=0x0000002A  "\000\000\000*"
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000A <uint32>=0x00000800
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000B <uint32>=0x00000800
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000C <blob>=0x0000000000000000
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000D <blob>=0x0000000000000000
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000E <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x0000000F <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000010 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000011 <uint32>=0x00000000
INFO [2018-02-12 11:21:12.22]: ▸     0x00000012 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000013 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000014 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000015 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000016 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000017 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000018 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x00000019 <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: ▸     0x0000001A <uint32>=0x00000001
INFO [2018-02-12 11:21:12.22]: $ openssl x509 -inform der -in /var/folders/7q/nbjwjbbs1sdbhfltcw1hs9t00000gn/T/d20180212-78351-5a9din/certs/distribution/8KQRUFN5J7.cer -subject -dates -noout &
INFO [2018-02-12 11:21:12.26]: ▸ subject= /UID=B34U44J9D6/CN=iPhone Distribution: mycompany, LLC. (B34U44J9D6)/OU=B34U44J9D6/O=mycompany, LLC./C=US
INFO [2018-02-12 11:21:12.26]: ▸ notBefore=Feb  9 16:31:11 2018 GMT
INFO [2018-02-12 11:21:12.26]: ▸ notAfter=Feb  9 16:31:11 2019 GMT

+-------------------+---------------------------------------------------+
|                         Installed Certificate                         |
+-------------------+---------------------------------------------------+
| User ID           | B34U44J9D6                                        |
| Common Name       | iPhone Distribution: mycompany, LLC. (B34U44J9D6) |
| Organisation Unit | B34U44J9D6                                        |
| Organisation      | mycompany, LLC.                                   |
| Country           | US                                                |
| Start Datetime    | Feb  9 16:31:11 2018 GMT                          |
| End Datetime      | Feb  9 16:31:11 2019 GMT                          |
+-------------------+---------------------------------------------------+

INFO [2018-02-12 11:21:12.94]: Installing provisioning profile...
WARN [2018-02-12 11:21:13.25]: Setting environment variable 'sigh_com.mycompany.nightly.v2_adhoc' to '01ab994a-d9ed-4e79-be7b-3c86a82af798'
WARN [2018-02-12 11:21:13.25]: Setting environment variable 'sigh_com.mycompany.nightly.v2_adhoc_team-id' to 'B34U44J9D6'
WARN [2018-02-12 11:21:13.25]: Setting environment variable 'sigh_com.mycompany.nightly.v2_adhoc_profile-name' to 'match AdHoc com.mycompany.nightly.v2'
WARN [2018-02-12 11:21:13.25]: Setting environment variable 'sigh_com.mycompany.nightly.v2_adhoc_profile-path' to '/Users/mhddeveloper/Library/MobileDevice/Provisioning Profiles/01ab994a-d9ed-4e79-be7b-3c86a82af798.mobileprovision'
INFO [2018-02-12 11:21:13.70]: Installing provisioning profile...
WARN [2018-02-12 11:21:14.01]: Setting environment variable 'sigh_com.mycompany.beta.v2_adhoc' to '1dd5b4f2-d6c2-4ae9-bf90-4bdc871d8a54'
WARN [2018-02-12 11:21:14.01]: Setting environment variable 'sigh_com.mycompany.beta.v2_adhoc_team-id' to 'B34U44J9D6'
WARN [2018-02-12 11:21:14.01]: Setting environment variable 'sigh_com.mycompany.beta.v2_adhoc_profile-name' to 'match AdHoc com.mycompany.beta.v2'
WARN [2018-02-12 11:21:14.01]: Setting environment variable 'sigh_com.mycompany.beta.v2_adhoc_profile-path' to '/Users/mhddeveloper/Library/MobileDevice/Provisioning Profiles/1dd5b4f2-d6c2-4ae9-bf90-4bdc871d8a54.mobileprovision'
INFO [2018-02-12 11:21:14.45]: Installing provisioning profile...
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc' to '99151e4c-7b3d-402b-ad10-15df7fe0607e'
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc_team-id' to 'B34U44J9D6'
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc_profile-name' to 'match AdHoc com.mycompany.endeavor'
WARN [2018-02-12 11:21:14.77]: Setting environment variable 'sigh_com.mycompany.endeavor_adhoc_profile-path' to '/Users/mhddeveloper/Library/MobileDevice/Provisioning Profiles/99151e4c-7b3d-402b-ad10-15df7fe0607e.mobileprovision'

+---------------------+------------------------+------------------------+
|                    Installed Provisioning Profile                     |
+---------------------+------------------------+------------------------+
| Parameter           | Environment Variable   | Value                  |
+---------------------+------------------------+------------------------+
| App Identifier      |                        | com.mycompany.nightly  |
|                     |                        | .v2                    |
| Type                |                        | adhoc                  |
| Platform            |                        | ios                    |
| Profile UUID        | sigh_com.mycompany.ni  | 01ab994a-d9ed-4e79-be  |
|                     | ghtly.v2_adhoc         | 7b-3c86a82af798        |
| Profile Name        | sigh_com.mycompany.ni  | match AdHoc            |
|                     | ghtly.v2_adhoc_profil  | com.mycompany.nightly  |
|                     | e-name                 | .v2                    |
| Profile Path        | sigh_com.mycompany.ni  | /Users/mhddeveloper/L  |
|                     | ghtly.v2_adhoc_profil  | ibrary/MobileDevice/P  |
|                     | e-path                 | rovisioning            |
|                     |                        | Profiles/01ab994a-d9e  |
|                     |                        | d-4e79-be7b-3c86a82af  |
|                     |                        | 798.mobileprovision    |
| Development Team ID | sigh_com.mycompany.ni  | B34U44J9D6             |
|                     | ghtly.v2_adhoc_team-i  |                        |
|                     | d                      |                        |
+---------------------+------------------------+------------------------+

+---------------------+------------------------+------------------------+
|                    Installed Provisioning Profile                     |
+---------------------+------------------------+------------------------+
| Parameter           | Environment Variable   | Value                  |
+---------------------+------------------------+------------------------+
| App Identifier      |                        | com.mycompany.beta.v2  |
| Type                |                        | adhoc                  |
| Platform            |                        | ios                    |
| Profile UUID        | sigh_com.mycompany.be  | 1dd5b4f2-d6c2-4ae9-bf  |
|                     | ta.v2_adhoc            | 90-4bdc871d8a54        |
| Profile Name        | sigh_com.mycompany.be  | match AdHoc            |
|                     | ta.v2_adhoc_profile-n  | com.mycompany.beta.v2  |
|                     | ame                    |                        |
| Profile Path        | sigh_com.mycompany.be  | /Users/mhddeveloper/L  |
|                     | ta.v2_adhoc_profile-p  | ibrary/MobileDevice/P  |
|                     | ath                    | rovisioning            |
|                     |                        | Profiles/1dd5b4f2-d6c  |
|                     |                        | 2-4ae9-bf90-4bdc871d8  |
|                     |                        | a54.mobileprovision    |
| Development Team ID | sigh_com.mycompany.be  | B34U44J9D6             |
|                     | ta.v2_adhoc_team-id    |                        |
+---------------------+------------------------+------------------------+

+---------------------+------------------------+------------------------+
|                    Installed Provisioning Profile                     |
+---------------------+------------------------+------------------------+
| Parameter           | Environment Variable   | Value                  |
+---------------------+------------------------+------------------------+
| App Identifier      |                        | com.mycompany.endeavo  |
|                     |                        | r                      |
| Type                |                        | adhoc                  |
| Platform            |                        | ios                    |
| Profile UUID        | sigh_com.mycompany.en  | 99151e4c-7b3d-402b-ad  |
|                     | deavor_adhoc           | 10-15df7fe0607e        |
| Profile Name        | sigh_com.mycompany.en  | match AdHoc            |
|                     | deavor_adhoc_profile-  | com.mycompany.endeavo  |
|                     | name                   | r                      |
| Profile Path        | sigh_com.mycompany.en  | /Users/mhddeveloper/L  |
|                     | deavor_adhoc_profile-  | ibrary/MobileDevice/P  |
|                     | path                   | rovisioning            |
|                     |                        | Profiles/99151e4c-7b3  |
|                     |                        | d-402b-ad10-15df7fe06  |
|                     |                        | 07e.mobileprovision    |
| Development Team ID | sigh_com.mycompany.en  | B34U44J9D6             |
|                     | deavor_adhoc_team-id   |                        |
+---------------------+------------------------+------------------------+

INFO [2018-02-12 11:21:14.82]: All required keys, certificates and provisioning profiles are installed 🙌
INFO [2018-02-12 11:21:14.83]: Setting Provisioning Profile type to 'ad-hoc'
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
Successfully loaded Appfile at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/Appfile'
- team_id: 'B34U44J9D6'
-------
INFO [2018-02-12 11:21:14.89]: -----------------
INFO [2018-02-12 11:21:14.89]: --- Step: gym ---
INFO [2018-02-12 11:21:14.89]: -----------------
DEBUG [2018-02-12 11:21:14.93]: Merging provisioning profile mappings
DEBUG [2018-02-12 11:21:14.94]: -------------------------------------
DEBUG [2018-02-12 11:21:14.94]: Primary provisioning profile mapping:
DEBUG [2018-02-12 11:21:14.94]: {}
DEBUG [2018-02-12 11:21:14.94]: Secondary provisioning profile mapping:
DEBUG [2018-02-12 11:21:14.94]: {:"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", :"com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", :"com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}
DEBUG [2018-02-12 11:21:14.94]: Resulting in the following mapping:
DEBUG [2018-02-12 11:21:14.94]: {:"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", :"com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", :"com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}
INFO [2018-02-12 11:21:14.94]: $ xcodebuild -list -workspace ./mycompany.xcworkspace
Select Scheme:
1. mycompany
2. Pods-mycompany
?  1
INFO [2018-02-12 11:21:19.74]: $ xcodebuild -showBuildSettings -workspace ./mycompany.xcworkspace -scheme mycompany
DEBUG [2018-02-12 11:21:21.32]: Parsing project file '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/mycompany.xcodeproj' to find selected provisioning profiles
DEBUG [2018-02-12 11:21:21.32]: Finding provision profiles for 'Release'
DEBUG [2018-02-12 11:21:21.55]: Merging provisioning profile mappings
DEBUG [2018-02-12 11:21:21.55]: -------------------------------------
DEBUG [2018-02-12 11:21:21.55]: Primary provisioning profile mapping:
DEBUG [2018-02-12 11:21:21.55]: {:"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", :"com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", :"com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}
DEBUG [2018-02-12 11:21:21.55]: Secondary provisioning profile mapping:
DEBUG [2018-02-12 11:21:21.55]: {}
DEBUG [2018-02-12 11:21:21.55]: Resulting in the following mapping:
DEBUG [2018-02-12 11:21:21.55]: {:"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", :"com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", :"com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}
INFO [2018-02-12 11:21:21.55]: Detected provisioning profile mapping: {:"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", :"com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", :"com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}

+--------------------------------------+--------------------------------------+
|                           Summary for gym 2.80.0                            |
+--------------------------------------+--------------------------------------+
| scheme                               | mycompany                            |
| workspace                            | ./mycompany.xcworkspace              |
| export_method                        | ad-hoc                               |
| export_options.provisioningProfiles  | match AdHoc                          |
| .com.mycompany.nightly.v2            | com.mycompany.nightly.v2             |
| export_options.provisioningProfiles  | match AdHoc com.mycompany.beta.v2    |
| .com.mycompany.beta.v2               |                                      |
| export_options.provisioningProfiles  | match AdHoc com.mycompany.endeavor   |
| .com.mycompany.endeavor              |                                      |
| destination                          | generic/platform=iOS                 |
| output_name                          | mycompany                            |
| build_path                           | /Users/mhddeveloper/Library/Develop  |
|                                      | er/Xcode/Archives/2018-02-12         |
| clean                                | false                                |
| output_directory                     | .                                    |
| silent                               | false                                |
| skip_package_ipa                     | false                                |
| buildlog_path                        | ~/Library/Logs/gym                   |
| skip_profile_detection               | false                                |
| xcode_path                           | /Applications/Xcode.app              |
+--------------------------------------+--------------------------------------+

+--------------------------------------+----------------------+
|                   Generated Build Command                   |
+--------------------------------------+----------------------+
| Option                               | Value                |
+--------------------------------------+----------------------+
| set -o pipefail &&                   |                      |
| xcodebuild                           |                      |
| -workspace ./mycompany.xcworkspace   |                      |
| -scheme mycompany                    |                      |
| -destination                         | generic/platform=iOS |
| -archivePath                         |                      |
| /Users/mhddeveloper/Library/Develop  |                      |
| er/Xcode/Archives/2018-02-12/mHelpD  |                      |
| esk\ 2018-02-12\ 11.21.21.xcarchive  |                      |
| archive                              |                      |
| | tee                                |                      |
| /Users/mhddeveloper/Library/Logs/gy  |                      |
| m/mycompany-mycompany.log            |                      |
| | xcpretty                           |                      |
+--------------------------------------+----------------------+
INFO [2018-02-12 11:21:21.93]: $ set -o pipefail && xcodebuild -workspace ./mycompany.xcworkspace -scheme mycompany -destination 'generic/platform=iOS' -archivePath /Users/mhddeveloper/Library/Developer/Xcode/Archives/2018-02-12/mycompany\ 2018-02-12\ 11.21.21.xcarchive archive | tee /Users/mhddeveloper/Library/Logs/gym/mycompany-mycompany.log | xcpretty
INFO [2018-02-12 11:21:23.29]: ▸ Building Pods/Pods-mycompany [Release]
INFO [2018-02-12 11:21:23.29]: ▸ Check Dependencies
INFO [2018-02-12 11:21:23.37]: ▸ Compiling Pods-mycompany-dummy.m
INFO [2018-02-12 11:21:23.49]: ▸ Compiling Pods-mycompany-dummy.m
INFO [2018-02-12 11:21:23.49]: ▸ Building library libPods-mycompany.a
INFO [2018-02-12 11:21:23.51]: ▸ Building library libPods-mycompany.a
INFO [2018-02-12 11:21:23.54]: ▸ Building CordovaLib/CordovaLib [Release]
INFO [2018-02-12 11:21:23.54]: ▸ Check Dependencies
INFO [2018-02-12 11:21:23.58]: ▸ Copying CDVWebViewEngineProtocol.h
INFO [2018-02-12 11:21:23.59]: ▸ Copying CDVScreenOrientationDelegate.h
INFO [2018-02-12 11:21:23.59]: ▸ Copying CDV.h
INFO [2018-02-12 11:21:23.60]: ▸ Copying CDVCommandQueue.h
INFO [2018-02-12 11:21:23.60]: ▸ Copying CDVAppDelegate.h
INFO [2018-02-12 11:21:23.61]: ▸ Copying CDVWhitelist.h
INFO [2018-02-12 11:21:23.62]: ▸ Copying CDVCommandDelegateImpl.h
INFO [2018-02-12 11:21:23.62]: ▸ Copying CDVPlugin+Resources.h
INFO [2018-02-12 11:21:23.62]: ▸ Copying CDVAvailability.h
INFO [2018-02-12 11:21:23.62]: ▸ Copying CDVUIWebViewDelegate.h
INFO [2018-02-12 11:21:23.63]: ▸ Copying CDVPluginResult.h
INFO [2018-02-12 11:21:23.63]: ▸ Copying NSMutableArray+QueueAdditions.h
INFO [2018-02-12 11:21:23.63]: ▸ Copying CDVInvokedUrlCommand.h
INFO [2018-02-12 11:21:23.63]: ▸ Copying CDVPlugin.h
INFO [2018-02-12 11:21:23.63]: ▸ Copying NSDictionary+CordovaPreferences.h
INFO [2018-02-12 11:21:23.64]: ▸ Copying CDVURLProtocol.h
INFO [2018-02-12 11:21:23.65]: ▸ Copying CDVCommandDelegate.h
INFO [2018-02-12 11:21:23.65]: ▸ Copying CDVAvailabilityDeprecated.h
INFO [2018-02-12 11:21:23.66]: ▸ Copying CDVUserAgentUtil.h
INFO [2018-02-12 11:21:23.67]: ▸ Copying CDVTimer.h
INFO [2018-02-12 11:21:23.67]: ▸ Copying CDVConfigParser.h
INFO [2018-02-12 11:21:23.67]: ▸ Copying CDVViewController.h
INFO [2018-02-12 11:21:23.68]: ▸ Precompiling CordovaLib_Prefix.pch
INFO [2018-02-12 11:21:23.74]: ▸ Precompiling CordovaLib_Prefix.pch
INFO [2018-02-12 11:21:23.82]: ▸ Compiling CDVViewController.m
INFO [2018-02-12 11:21:24.82]: ▸ Compiling NSDictionary+CordovaPreferences.m
INFO [2018-02-12 11:21:24.83]: ▸ Compiling CDVAppDelegate.m
INFO [2018-02-12 11:21:24.83]: ▸ Compiling CDVUIWebViewDelegate.m
INFO [2018-02-12 11:21:24.83]: ▸ Compiling CDVCommandDelegateImpl.m
INFO [2018-02-12 11:21:24.83]: ▸ Compiling CDVJSON_private.m
INFO [2018-02-12 11:21:24.83]: ▸ Compiling CDVWhitelist.m
INFO [2018-02-12 11:21:24.84]: ▸ Compiling CDVInvokedUrlCommand.m
INFO [2018-02-12 11:21:24.84]: ▸ Compiling CDVTimer.m
INFO [2018-02-12 11:21:24.84]: ▸ Compiling CDVUserAgentUtil.m
INFO [2018-02-12 11:21:24.84]: ▸ Compiling CDVConfigParser.m
INFO [2018-02-12 11:21:24.90]: ▸ Compiling CDVGestureHandler.m
INFO [2018-02-12 11:21:24.90]: ▸ Compiling CDVHandleOpenURL.m
INFO [2018-02-12 11:21:24.91]: ▸ Compiling CDVUIWebViewNavigationDelegate.m
INFO [2018-02-12 11:21:25.11]: ▸ Compiling NSMutableArray+QueueAdditions.m
INFO [2018-02-12 11:21:25.11]: ▸ Compiling CDVCommandQueue.m
INFO [2018-02-12 11:21:25.25]: ▸ Compiling CDVPluginResult.m
INFO [2018-02-12 11:21:25.25]: ▸ Compiling CDVPlugin+Resources.m
INFO [2018-02-12 11:21:25.25]: ▸ Compiling CDVURLProtocol.m
INFO [2018-02-12 11:21:25.39]: ▸ Compiling CDVUIWebViewEngine.m
INFO [2018-02-12 11:21:25.51]: ▸ Compiling CDVPlugin.m
INFO [2018-02-12 11:21:25.51]: ▸ Compiling CDVLocalStorage.m
INFO [2018-02-12 11:21:25.88]: ▸ Compiling CDVIntentAndNavigationFilter.m
INFO [2018-02-12 11:21:25.88]: ▸ Compiling CDVViewController.m
INFO [2018-02-12 11:21:26.24]: ▸ Compiling NSDictionary+CordovaPreferences.m
INFO [2018-02-12 11:21:26.24]: ▸ Compiling CDVAppDelegate.m
INFO [2018-02-12 11:21:26.24]: ▸ Compiling CDVUIWebViewDelegate.m
INFO [2018-02-12 11:21:26.25]: ▸ Compiling CDVCommandDelegateImpl.m
INFO [2018-02-12 11:21:26.25]: ▸ Compiling CDVJSON_private.m
INFO [2018-02-12 11:21:26.25]: ▸ Compiling CDVWhitelist.m
INFO [2018-02-12 11:21:26.30]: ▸ Compiling CDVInvokedUrlCommand.m
INFO [2018-02-12 11:21:26.30]: ▸ Compiling CDVTimer.m
INFO [2018-02-12 11:21:26.39]: ▸ Compiling CDVUserAgentUtil.m
INFO [2018-02-12 11:21:26.54]: ▸ Compiling CDVConfigParser.m
INFO [2018-02-12 11:21:26.54]: ▸ Compiling CDVGestureHandler.m
INFO [2018-02-12 11:21:26.56]: ▸ Compiling CDVHandleOpenURL.m
INFO [2018-02-12 11:21:26.65]: ▸ Compiling CDVUIWebViewNavigationDelegate.m
INFO [2018-02-12 11:21:26.91]: ▸ Compiling NSMutableArray+QueueAdditions.m
INFO [2018-02-12 11:21:26.91]: ▸ Compiling CDVCommandQueue.m
INFO [2018-02-12 11:21:26.91]: ▸ Compiling CDVPluginResult.m
INFO [2018-02-12 11:21:26.92]: ▸ Compiling CDVPlugin+Resources.m
INFO [2018-02-12 11:21:26.92]: ▸ Compiling CDVURLProtocol.m
INFO [2018-02-12 11:21:27.15]: ▸ Compiling CDVUIWebViewEngine.m
INFO [2018-02-12 11:21:27.20]: ▸ Compiling CDVPlugin.m
INFO [2018-02-12 11:21:27.21]: ▸ Compiling CDVLocalStorage.m
INFO [2018-02-12 11:21:27.36]: ▸ Compiling CDVIntentAndNavigationFilter.m
INFO [2018-02-12 11:21:27.38]: ▸ Building library libCordova.a
INFO [2018-02-12 11:21:27.41]: ▸ Building library libCordova.a
INFO [2018-02-12 11:21:28.04]: ▸ Building mycompany/mycompany [Release]
INFO [2018-02-12 11:21:28.04]: ▸ Check Dependencies
INFO [2018-02-12 11:21:28.05]: ▸ ** ARCHIVE FAILED **
INFO [2018-02-12 11:21:28.06]: ▸ The following build commands failed:
INFO [2018-02-12 11:21:28.06]: ▸ Check dependencies
INFO [2018-02-12 11:21:28.06]: ▸ (1 failure)
▸ Building Pods/Pods-mycompany [Release]
▸ Check Dependencies
▸ Compiling Pods-mycompany-dummy.m
▸ Compiling Pods-mycompany-dummy.m
▸ Building library libPods-mycompany.a
▸ Building library libPods-mycompany.a
▸ Building CordovaLib/CordovaLib [Release]
▸ Check Dependencies
▸ Copying CDVWebViewEngineProtocol.h
▸ Copying CDVScreenOrientationDelegate.h
▸ Copying CDV.h
▸ Copying CDVCommandQueue.h
▸ Copying CDVAppDelegate.h
▸ Copying CDVWhitelist.h
▸ Copying CDVCommandDelegateImpl.h
▸ Copying CDVPlugin+Resources.h
▸ Copying CDVAvailability.h
▸ Copying CDVUIWebViewDelegate.h
▸ Copying CDVPluginResult.h
▸ Copying NSMutableArray+QueueAdditions.h
▸ Copying CDVInvokedUrlCommand.h
▸ Copying CDVPlugin.h
▸ Copying NSDictionary+CordovaPreferences.h
▸ Copying CDVURLProtocol.h
▸ Copying CDVCommandDelegate.h
▸ Copying CDVAvailabilityDeprecated.h
▸ Copying CDVUserAgentUtil.h
▸ Copying CDVTimer.h
▸ Copying CDVConfigParser.h
▸ Copying CDVViewController.h
▸ Precompiling CordovaLib_Prefix.pch
▸ Precompiling CordovaLib_Prefix.pch
▸ Compiling CDVViewController.m
▸ Compiling NSDictionary+CordovaPreferences.m
▸ Compiling CDVAppDelegate.m
▸ Compiling CDVUIWebViewDelegate.m
▸ Compiling CDVCommandDelegateImpl.m
▸ Compiling CDVJSON_private.m
▸ Compiling CDVWhitelist.m
▸ Compiling CDVInvokedUrlCommand.m
▸ Compiling CDVTimer.m
▸ Compiling CDVUserAgentUtil.m
▸ Compiling CDVConfigParser.m
▸ Compiling CDVGestureHandler.m
▸ Compiling CDVHandleOpenURL.m
▸ Compiling CDVUIWebViewNavigationDelegate.m
▸ Compiling NSMutableArray+QueueAdditions.m
▸ Compiling CDVCommandQueue.m
▸ Compiling CDVPluginResult.m
▸ Compiling CDVPlugin+Resources.m
▸ Compiling CDVURLProtocol.m
▸ Compiling CDVUIWebViewEngine.m
▸ Compiling CDVPlugin.m
▸ Compiling CDVLocalStorage.m
▸ Compiling CDVIntentAndNavigationFilter.m
▸ Compiling CDVViewController.m
▸ Compiling NSDictionary+CordovaPreferences.m
▸ Compiling CDVAppDelegate.m
▸ Compiling CDVUIWebViewDelegate.m
▸ Compiling CDVCommandDelegateImpl.m
▸ Compiling CDVJSON_private.m
▸ Compiling CDVWhitelist.m
▸ Compiling CDVInvokedUrlCommand.m
▸ Compiling CDVTimer.m
▸ Compiling CDVUserAgentUtil.m
▸ Compiling CDVConfigParser.m
▸ Compiling CDVGestureHandler.m
▸ Compiling CDVHandleOpenURL.m
▸ Compiling CDVUIWebViewNavigationDelegate.m
▸ Compiling NSMutableArray+QueueAdditions.m
▸ Compiling CDVCommandQueue.m
▸ Compiling CDVPluginResult.m
▸ Compiling CDVPlugin+Resources.m
▸ Compiling CDVURLProtocol.m
▸ Compiling CDVUIWebViewEngine.m
▸ Compiling CDVPlugin.m
▸ Compiling CDVLocalStorage.m
▸ Compiling CDVIntentAndNavigationFilter.m
▸ Building library libCordova.a
▸ Building library libCordova.a
▸ Building mycompany/mycompany [Release]
▸ Check Dependencies
** ARCHIVE FAILED **

The following build commands failed:
Check dependencies
(1 failure)
ERROR [2018-02-12 11:21:28.08]: Exit status: 65

+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.80.0                  |
| export_method | ad-hoc                  |
| sdk           | iPhoneOS11.2.sdk        |
+---------------+-------------------------+

INFO [2018-02-12 11:21:28.12]: ▸ === BUILD TARGET mycompany OF PROJECT mycompany WITH CONFIGURATION Release ===
INFO [2018-02-12 11:21:28.12]: ▸ Check dependencies
INFO [2018-02-12 11:21:28.12]: ▸ Code Signing Error: Provisioning profile "match AdHoc com.mycompany.endeavor" doesn't include signing certificate "iPhone Distribution: mycompany, LLC. (B34U44J9D6)".
INFO [2018-02-12 11:21:28.12]: ▸ Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.2'
INFO [2018-02-12 11:21:28.12]:
ERROR [2018-02-12 11:21:28.12]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
WARN [2018-02-12 11:21:28.12]: 📋  For the complete and more detailed error log, check the full log at:
WARN [2018-02-12 11:21:28.12]: 📋  /Users/mhddeveloper/Library/Logs/gym/mycompany-mycompany.log
INFO [2018-02-12 11:21:28.12]:
ERROR [2018-02-12 11:21:28.12]: Looks like fastlane ran into a build/archive error with your project
ERROR [2018-02-12 11:21:28.12]: It's hard to tell what's causing the error, so we wrote some guides on how
ERROR [2018-02-12 11:21:28.12]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
ERROR [2018-02-12 11:21:28.12]: Before submitting an issue on GitHub, please follow the guide above and make
ERROR [2018-02-12 11:21:28.12]: sure your project is set up correctly.
ERROR [2018-02-12 11:21:28.12]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
ERROR [2018-02-12 11:21:28.12]: the full commands printed out in yellow in the above log.
ERROR [2018-02-12 11:21:28.12]: Make sure to inspect the output above, as usually you'll find more error information there
INFO [2018-02-12 11:21:28.12]:
WARN [2018-02-12 11:21:28.13]: Lane Context:
INFO [2018-02-12 11:21:28.13]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :SIGH_PROFILE_TYPE=>"ad-hoc", :MATCH_PROVISIONING_PROFILE_MAPPING=>{"com.mycompany.nightly.v2"=>"match AdHoc com.mycompany.nightly.v2", "com.mycompany.beta.v2"=>"match AdHoc com.mycompany.beta.v2", "com.mycompany.endeavor"=>"match AdHoc com.mycompany.endeavor"}}
ERROR [2018-02-12 11:21:28.13]: Error building the application - see the log above
INFO [2018-02-12 11:21:28.13]: Successfully generated documentation at path '/Users/mhddeveloper/Workspace/workspace/MobileV2 - iOS/MobileV2/cordova/platforms/ios/fastlane/README.md'

+------+------------------------+-------------+
|              fastlane summary               |
+------+------------------------+-------------+
| Step | Action                 | Time (in s) |
+------+------------------------+-------------+
| 1    | Verifying fastlane     | 0           |
|      | version                |             |
| 2    | default_platform       | 0           |
| 3    | echo $FASTLANE_USER    | 0           |
| 4    | if [ -d                | 0           |
|      | ../DerivedData ];      |             |
|      | then rm -r             |             |
|      | ../DerivedData; fi     |             |
| 5    | if [ -d test_output    | 0           |
|      | ]; then rm -r          |             |
|      | test_output; fi        |             |
| 6    | cocoapods              | 3           |
| 7    | unlock_keychain        | 7           |
| 8    | security               | 0           |
|      | set-keychain-settings  |             |
|      | -t 3600 -l             |             |
|      | ~/Library/Keychains    |             |
| 9    | security               | 0           |
|      | set-key-partition-lis  |             |
|      | t -S                   |             |
|      | apple-tool:,apple: -s  |             |
|      | -k m                   |             |
| 10   | register_devices       | 12          |
| 11   | match                  | 6           |
| 💥   | gym                    | 13          |
+------+------------------------+-------------+

ERROR [2018-02-12 11:21:28.15]: fastlane finished with errors
/Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane_core/lib/fastlane_core/ui/interface.rb:155:in `build_failure!': [!] Error building the application - see the log above (FastlaneCore::Interface::FastlaneBuildFailure)
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane_core/lib/fastlane_core/ui/ui.rb:16:in `method_missing'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/gym/lib/gym/error_handler.rb:73:in `handle_build_error'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/gym/lib/gym/runner.rb:97:in `block in build_app'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane_core/lib/fastlane_core/command_executor.rb:93:in `call'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane_core/lib/fastlane_core/command_executor.rb:93:in `execute'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/gym/lib/gym/runner.rb:93:in `build_app'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/gym/lib/gym/runner.rb:18:in `run'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/gym/lib/gym/manager.rb:19:in `work'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/actions/build_ios_app.rb:64:in `run'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:231:in `block in execute_action'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:148:in `trigger_action_by_name'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/fast_file.rb:148:in `method_missing'
	from Fastfile:41:in `block (2 levels) in parsing_binding'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in `run!'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/commands_generator.rb:337:in `run'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/fastlane/lib/fastlane/cli_tools_distributor.rb:98:in `take_off'
	from /Users/mhddeveloper/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.80.0/bin/fastlane:20:in `<top (required)>'
	from /Users/mhddeveloper/.fastlane/bin/bundle/bin/fastlane:22:in `load'
	from /Users/mhddeveloper/.fastlane/bin/bundle/bin/fastlane:22:in `<main>'
MHDs-Mac-mini:fastlane mhddeveloper$

I ended up creating and deleting keychains.
I don't like this solution at all. But it worked.
My main question remains, I have seen people saying they manage 18 apps in the fastlane issue comments, I don't understand howcome they manage that thru match when it is only possible to have 3 distribution profiles and it is not possible to use the same Dist profile for multiple apps....
Here is my solution:
lane :beta do |options|
    preparePods

    unlock_keychain(path:"login.keychain", password:ENV["MATCH_PASSWORD"])
    sh "security set-keychain-settings -t 3600 -l ~/Library/Keychains/login.keychain"

    #create a new keychain for the dist profile
    create_keychain(
        name: ENV["KEYCHAIN_NAME"],
        unlock: true,
        timeout: false,
        lock_when_sleeps: false,
        password: ENV["MATCH_PASSWORD"]
    )

    set_build_number(options[:build_number])
    set_version_number(options[:version_number])
    register_devices(devices_file: "./devices.txt")
    match(type: "adhoc", keychain_name: ENV["KEYCHAIN_NAME"], force_for_new_devices: true)
    unit_tests
    screenShots

# very very important
    sh "security set-key-partition-list -S apple-tool:,apple: -s -k #{ENV["MATCH_PASSWORD"]} #{ENV["KEYCHAIN_NAME"]}"

    gym(export_method:"ad-hoc",
        scheme: "Hugin",
        workspace:"Hugin.xcworkspace",
        export_xcargs: "-allowProvisioningUpdates",
        include_bitcode: false,
        export_options: {
            uploadBitcode: false,
            uploadSymbols: true,
            compileBitcode: false
        }
      )

    # between commit has to be changed before every merge request
    changes = changelog_from_git_commits(
          between: ["b7d62280", "HEAD"],  # Optional, lets you specify a revision/tag range between which to collect commit info
          pretty: "- %s",# Optional, lets you provide a custom format to apply to each commit when generating the changelog text
          date_format: "short",# Optional, lets you provide an additional date format to dates within the pretty-formatted string
          match_lightweight_tag: false,  # Optional, lets you ignore lightweight (non-annotated) tags when searching for the last tag
          merge_commit_filtering: "exclude_merges" # Optional, lets you filter out merge commits
          )

    # upload to Beta by Crashlytics
    crashlytics(
      api_token: "token",
      build_secret: "token",
      notes: changes,
      groups:["qa","product"],
      notifications: true
    )

    # delete the keychain
    delete_keychain(name: ENV["KEYCHAIN_NAME"])

  end


Recommend neovim as one of the editors

Neovim does have a perl6 syntax file, but it is outdated: https://github.com/neovim/neovim/blob/master/runtime/syntax/perl6.vim
In any case, maybe it is actually usable? Perhaps somebody can try it and if it works even a little bit, we can list it too.

afaik this is available in normal vim too, but there exists https://github.com/vim-perl/vim-perl6.git which should work on both.

I'll try compiling neovim and give it a whirl, and see if the vim-perl/vim-perl6.git bundle works nicely with it as well. If the results are positive, I'll add it as a recommendation.


fixes packages with only nohoist

prevents garn from assuming package has a package declaration when it only has a nohoist declaration in workspaces
allows for package.json with only nohoist in workspaces in accordance with https://classic.yarnpkg.com/blog/2018/02/15/nohoist/
...
"workspaces": {
  "nohoist": [...]
},
...

Looks good! Merge it :tada:


library-referance patch

In library-referance.rst, it uses the variable i in an example, and i is never defined. I replaced i with
Microphone.list_microphone_names().index(microphone_name) so the example code is actually use able.

Nice catch! I used your example to fix it in<PHONE_NUMBER>1f851c28a83d515ef1e1794d46c511.


Scissor rect validation failed assertion on Metal

I am getting 'Scissor rect validation failed assertion' errors with what seem to be uninitialised integer values for some of the rect components on Metal, since https://github.com/google/filament/pull/5644 landed.  E.g.
-[MTLDebugRenderCommandEncoder setScissorRect:]:3635: failed assertion `Set Scissor Rect Validation
(rect.x(18446744073709551615) + rect.width(0))(18446744073709551615) must be <= render pass width(2732)

(added: that's of course a '-1', not a random value, but still looks like something did not get initialised beyond that).
This is without actually ever calling setScissor anywhere. Am I supposed to call this with the same values as the Viewport when I don't want to make use of scissoring?

This seems to be related to https://github.com/google/filament/issues/5892: the scissor rect validation assertion passes as long as the viewport does not extend beyond the screen/framebuffer size.

Lacking time to do more advanced debugging, I stuck in some logging in MetalDriver.mm in the bit that starts with the comment 'Set scissor-rectangle.'. The first few frames it shows
sleft = 0.000000, sright =<PHONE_NUMBER>.000000, stop = 0.000000, sbottom =<PHONE_NUMBER>.000000
vleft = 0.000000, vright = 1512.000000, vtop = 0.000000, vbottom = 1008.000000
left = 0.000000, right = 1512.000000, top = 0.000000, bottom = 1008.000000

which looks ok (assuming the large values for sright and sbottom are intentional). This does not trigger the problem yet. Then at some point the assertion triggers, and the values for that frame are
sleft = 0.000000, sright =<PHONE_NUMBER>.000000, stop = 0.000000, sbottom =<PHONE_NUMBER>.000000
vleft =<PHONE_NUMBER>3709551616.000000, vright =<PHONE_NUMBER>3709551616.000000, vtop = 0.000000, vbottom = 2008.000000
left =<PHONE_NUMBER>3709551616.000000, right = 2732.000000, top = 0.000000, bottom = 2008.000000

I don't think I am changing the viewport to have vleft=vright=-1, but I'll triple check.

@kpeeters Thanks for your patience, I was out last week. I'll give this a closer look.

@bejado No problem at all. I can confirm that I only call setViewport once, with sensible values.

@kpeeters Thank you for that detailed debugging info. After further investigation, I suspect that your app (or Filament) is passing in a negative Viewport origin, which is valid, but not currently handled correctly.
I've updated https://github.com/google/filament/pull/5896 to fix this, which should now fix this issue and https://github.com/google/filament/issues/5892.

@bejado All good now (for both issues). Yes, I was indeed using a negative Viewport origin. Thanks a lot, I can run HEAD again.

@kpeeters Good to hear, apologies for the trouble!

I am still seeing an assert failing when the left boundary of the scissor is beyond half of the viewport width. The assert shows a number for the viewport width which is half its actual size. Does not happen with the top being beyond half the viewport height, strangely. May have something to do with the fact that this device has UIScreen.main.nativeScale == 2, but I don't have any others available to test that. If there's something obvious that comes to mind, let me know, otherwise I'll do some more digging.

I don't see any assert when adjusting the left boundary of the scissor beyond half the viewport width.
We have some test cases for scissor / viewport which you can play around with and run via:
./build.sh -p desktop debug backend_test_mac
out/cmake-debug/filament/backend/backend_test_mac --api metal '--gtest_filter=BackendTest.ScissorViewport*'

If you're able to reproduce the assertion please feel free to file another issue.


var.create && var.create_iam_role evaluated before the creation of the map not after

Description
This PR fixes the issue with the for_each expression in the code, where var.create_iam_role was unable to overwrite a broken for_each expression. It changes the code to evaluate user variables first, and then if they are true, evaluates the list comprehension.
Motivation and Context
The issue with the for_each expression in the code has been reported in multiple issues (#2337, #1753, and #2411), and this PR aims to fix it for users creating their own iam role. This change evaluates user variables first, and then if they are true, evaluates the list comprehension, which solves an issue if some locals are only known after apply. See full comment https://github.com/terraform-aws-modules/terraform-aws-eks/issues/2458#issuecomment-1459407299
Breaking Changes
There are no breaking changes with this PR.
How Has This Been Tested?

I tested on a local terraform deployment
I ran pre-commit as requested

I apologize as I have no reproducible minimum for you to evaluate on, hopefully someone else can provide it.

I apologize as I have no reproducible minimum for you to evaluate on, hopefully someone else can provide it.

We will not accept changes unless someone can provide a reproduction first that demonstrates the issue

I understand the desire to have a reproduction, but I, unfortunately, have too much on my plate.
You are seeing a lot of issues on this one line and my change disables that line in a way the user can then fix it themselves.


MPT inference after conversion

I ran conversion of MPT to ONNX following the docs here: https://huggingface.co/docs/optimum/main/en/exporters/onnx/usage_guides/export_a_model#customize-the-export-of-transformers-models-with-custom-modeling
At conversion I got a bunch of logs like this:
	- Validating ONNX Model output "present.0.key":
		-[✓] (2, 32, 128, 16) matches (2, 32, 128, 16)
		-[x] values not close enough, max diff: 0.00390625 (atol: 1e-05)

And then when I go to test inference I cannot get the model to product more than 1 new token.
I believe there is something missing with sequence length but I'm not sure what. This ticket describes a similar issue: https://github.com/mosaicml/llm-foundry/issues/345
Thank for your help!
cc @fxmarty

Thanks @fxmarty makes sense.
What about the "values not close enough" during conversion. Seems like there is still an issue during conversion.

@zacharyblank I can not tell whether it is an issue in the export or just the ATOL_FOR_VALIDATION that is too low, we would need to run real generations to see if it has an influence or not.

@fxmarty are you suggesting I override ORTModelForCausalLM.forward and swap the last 2 dimensions?
class IsomericLM(ORTModelForCausalLM):
  def forward(self, input_ids: torch.LongTensor = None, attention_mask: torch.FloatTensor or None = None, past_key_values: Tuple[Tuple[torch.Tensor]] or None = None, labels: torch.LongTensor or None = None, **kwargs) -> CausalLMOutputWithCrossAttentions:

    # Swap last 2 dimensions

    return super().forward(input_ids, attention_mask, past_key_values, labels, **kwargs)

MPT is currently not supported in transformers natively and thus we won't support it for now in the ONNX Runtime extension, and I don't expect it to work.

@fxmarty Now that MPT is supported in transformers, maybe it might be worth revisiting now? 🤗 This feature was also requested for transformers.js here.


Messages with "payload" property broken in spring-cloud-function-adapter-aws

Describe the bug
We are using SpringCloudFunctions on AWS for Lambdas.
The messages send to the Lambdas contain a property "payload".
This worked fine up until<EMAIL_ADDRESS>With the current version 4.1.2  the message does not reach the lambda implementation correctly.
Only the "payload" property gets passed to the function-code
Sample
Deploy a SCF-Lambda to AWS or Localstack and log the input:
@SpringBootApplication
@Slf4j
public class SampleLambda {

  @Bean
  public Function<Message<String>, String> transformMessage() {
    return input -> {
        log.info("Debug: {}", input.getPayload());
      return input.getPayload();
    };
  }
}

Sample-Input:
{
  "a": "b",
  "payload": {
    "c": "d"
  }
}

Output:
"Debug: {\"c\":\"d\"},.."

The lambda is triggered by a step function that builds a json object as input for the lambda.
Why would we pass this as a header to the lambda?
Here an extended examplee:
{
  "someProperty": "someValue",
  "payload": {
    "otherProperty": "otherValue"
  }
}

Would log:
"Debug: {\"otherProperty\":\"otherValue\"},.."
Everything outside of the "payload" property of the message we build for the lambda does not reach our code.

We are getting a similar error after upgrading to Spring Cloud Function 4.1.1. (Or actually same as #1135, but after upgrading to 4.1.2 I expect the same as above). Same scenario as @M0rious: our lambda input request has a json field called "payload" that is not expected any special handling on an AWS Lambda adapter level.
The special handling of the "payload" field seems to have been introduced by the following commit, although I don't understand how the change is related to #1086 as mentioned in the commit message:
https://github.com/spring-cloud/spring-cloud-function/commit/8a93e10a0e95dd26d3f111b38a1e9be5fd42a5c2#diff-c3541839d4b70d7bf7b3c116f62949cdab0fd8923e1ccf57a6788e6411d67d87
@olegz What was the original reason for adding special handling of requests having a "payload" field? Ideally there would be some way to opt in or opt out from this behavior to avoid breaking changes to existing Lambda functions.

Don't get me wrong, we can fix it, just trying to understand  your expectation and what I read is that given that Spring Message has a distinct payload field, you would expect/like your payload to go there and the rest as headers, correct?

Don't get me wrong, we can fix it, just trying to understand your expectation and what I read is that given that Spring Message has a distinct payload field, you would expect/like your payload to go there and the rest as headers, correct?

Yes - if we send a JSON-Message to the Lambda we expect the whole message to be in the payload field - regardless of the fields contained in the message we send.
We use Message as Input for the Lambda so we can call getHeaders to use e.g. the 'aws-context' header for logging.


finishSC is not running

Hi, I am trying to use finishSC but it doesn't work. I was trying the Ecoli example and I had the same error:
usage: finisherSC.py [-h] [-p PICKUP] [-o MAPCONTIGS] [-f FAST]
[-par PARALLEL] [-l LARGE]
folderName mummerLink
finisherSC.py: error: too few arguments
It seems that finishSC.py doesn't recognize my paths. I have changed but I still had the same error.
Kind regards
Ruth

Maybe you can try to use absolute path. BTW: What is your command ?

I have tried with the absolute path too. I use a LSF system with the bsub instruction, but I tried the program in my computer without the cluster too and it is still not working.

You may consider following the commands in the following link.
https://github.com/kakitone/finishingTool/blob/master/.travis.yml
I am not sure whether it was a typo, but you mentioned "finishSC.py". The command should use "finisherSC.py" instead of "finishSC.py"
BTW: the OS need to be Mac/Linux and Python need to be version 2.7.


 I only tested <IP_ADDRESS>, so it might not be an issue on newer versions.

Does prototype per chance overwrite some of the array prototype methods?
 I only tested <IP_ADDRESS>, so it might not be an issue on
newer versions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/calvinmetcalf/shapefile-js/issues/82, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABE4n2EtI80Nufsq3X0OYvzRg5h4P5qYks5sYhCggaJpZM4O4Jvp
.

Yea, I'm sure it does. It overrides a lot of core js. It's pretty annoying to deal with.

I think you may have answered your own question  ¯_(ツ)_/¯

Yup, I was just posting in case anyone else encountered it.


[Rule34xxx] Add extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Add extractor for rule34.xxx.
Videos on this site do not have titles, I took the liberty of setting the title to rule34xxx.

There are quite a few additional metadata fields that could be populated with information from the page. Many can be found in the README - but tags also comes to mind as one that would be particularly useful for this extractor.
Having said that, I think this would be the first extractor added specifically for an imageboard/booru-style site within yt-dlp. Since they tend to be designed for and dominated by images rather than videos, I'm inclined to say that gallery-dl is a better home for an extractor like this. It can even delegate video downloads to yt-dlp as needed.

Understandable, I didn't consider the whole site but only videos.


Policy conditions not enforced in resource policy?

I'm testing IAMSpy and it looks like policy conditions in resource policy are / may not be enforced.  What behavior is expected?
I've created a failing test case here:
https://github.com/skuenzli/IAMSpy/commit/3614947751b8507d1c5eed56956b06cbb600e0b7
But basically the test case uses:

allow-testing-s3.json GAAD which grants no permissions to role testing via Identity policies
a bucket policy that Allows s3:GetObject to principal * and narrows that with an aws:PrincipalArn condition

Statement:
{
          "Sid": "AllowNonExistentPrincipal",
          "Effect": "Allow",
          "Principal": "*",
          "Action": "s3:GetObject",
          "Resource": [
            "arn:aws:s3:::bucket",
            "arn:aws:s3:::bucket/*"
          ],
          "Condition": {
            "ArnEquals": {
              "aws:PrincipalArn": [
                "arn:aws:iam::111111111111:user/some-other-user"
              ]
            }
          }
        }

IAMSpy can_i reports the testing principal has the s3:GetObject permission to the bucket.
FWIW, I have tried both strict_conditions=True and False
Is this behavior expected?
AFAICT (from debug output in my private library integration), the condition is parsed from the statement in the resource policy.

Yup this is currently a known issue. So condition support has started, but the ties between the various condition keys haven't been fully setup yet. At the moment, it will enforce that the PrincipalArn as a string matches should multiple policies require them to be different, but it is yet to compare this against the source ARN. Once the SCP branch has been merged in, that is next on my todo list :)

@Skybound1 - quick update:
I spent a couple days getting acquainted with IAMSpy and trying to figure out where to add/copy the condition key constraints.
It seems like parse.py's generate_evaluation_logic_checks needs something like:
    if source:
        if identity_identifier not in model_vars:
            constraints.append(identity_check == False)  # noqa: E712
        source_account = source.split(":")[4]
        constraints.append(z3.String("s_account") == z3.StringVal(source_account))
        # WIP add context keys to identity side of model so conditions in resource policy are respected
        # (using specific condition names below just for exploration/poc)
        constraints.extend([
            z3.Bool("condition_aws:PrincipalArn_exists") == True,  # noqa: E712
            z3.String("condition_aws:PrincipalArn") == z3.StringVal(source),
        ])

But I'm stuck and don't feel like I really understand what I'm doing.
If you can provide some guidance on how to implement this, or even some recommended reading about using z3 String expressions, I'm happy to work on this some more.

:thinking:  TBH, considering the scale of work that needs to go into conditions, I don't think putting it into that function would be the cleanest, imho we should have a separate function that is called to generate all the condition constraints.
Also, so I would make a few tweaks to that:

It shouldn't be added as part of the if source, this constraint should always be in place, as it should also apply for say the who_can operation where the source isn't defined but computed by the model, but this constraint should still apply. I think this is just a constraint that is always added in. This constraint should just be linking the source ARN to the condition key. Policy conditions just compare the condition_key variable against whatever is defined in the policy, but as that isn't constrained anywhere, IAMSpy can just set that to whatever it wants. This is just to tell IAMSpy that this variable should always be linked to the source. There will be a tad bit we will need to change when it comes to assumed role ARNs vs role ARNs, but that's a problem for later I think.
I wouldn't enforce the exists == True, the condition_key_exists labels are used for the strict condition checking part of the tool, not for making sure the values are legit.
So there is a difference between z3.String and z3.StringVal. z3.String is for declaring and using a variable. So this will be something that we let the model play with, and the string we use as the argument is the name / label of that variable. z3.StringVal defines a constant, and the argument is the value the constant is set to. In this case, I don't think we need to define any constants, we just need to define a constraint saying whatever is in condition_aws:PrincipalArn is the same as whats in s  (well named I know xD)... so that would be something like z3.String("condition_aws:PrincipalArn") == z3.String("s")

Annoyingly, I haven't found that many great docs on using Python Z3, so it's been a lot of experimenting myself, reading through general Z3 docs and trying to figure out how to conver that to Python, etc

Thanks for the detailed guidance.
I had similar thoughts that:

the constraint should always apply, regardless of source; I was mostly just experimenting in the path that was executing.
some well-named functions like apply_constraints_for_conditions might help modularize and clarify intent
z3py docs have big gaps; I've taken to skimming questions tagged with z3py on StackOverflow since I'm not even sure how to ask/phrase questions for search

I'll try to give this another shot next week.


Login workflow

- Summary
This PR improves the login/logout flow by displaying a currently logged in userpic in the AppHeader + allowing to log out.
Closes #100
- Test plan

Log in with GitHub
Click on the user pic in the right top corner
Click Logout
You'll see the login screen again

Unfortunately re-login introduceses some React errors. See #136
- Description for the changelog
[feat](login) Added userpic with a logout action in the dropdown.

LGTM


FVM Launch: represented Bacalhau and Waterlily at the FVM Launch livestream

For "Celebrating Things Done" session

This is done, well done @wesfloyd!


Chapter 2 bug - drops one message

If I do this with 10,000 items:
 for line in f:
     print(line)
     time.sleep(.02)
     message = rabbitpy.Message(channel,
                                ujson.dumps(line.rstrip()),
                                {'content_type': 'text/plain'},
                                opinionated=True)
     message.publish(exchange, sys.argv[1])

And then do this to retrieve the data:
while len(queue) > 0:
    message = queue.get()
    print('Message:')
    print(' ID: %s' % message.properties['message_id'])
    print(' Time: %s' % message.properties['timestamp'].isoformat())
    print(' Body: %s' % message.body)
    o.write(str(message.body))
    o.write("\n")
    message.ack()

I consistently get back 9,999 items. I understand that this is not the right way and that it is desirable to "consume" rather than "get", but the RabbitMQ In Depth Book is a treasure, and this library should function correctly. I'm digging in with PyCharm, will post my findings, and a patch if I figure out how to fix it.

I'm afraid there's probably more to this issue than what's in your code, how are you declaring the connection and channel? My guess is your app is exiting before the TCP buffer is fully flushed.
If you're not using a context manager for the connection, you might want to give that a try.


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5829480876
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Aug 11 06:09:41 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5839776011
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Aug 12 06:08:26 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5845708182
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Aug 13 06:08:20 UTC 2023

This is failing because it's trying to create a tag that already exists for some reason.
Creating new commit and pushing, attempt 1
Cloning into 'repo_checkout'...
[main efeecb21] .github/workflows/e2e.nodejs.release.main.default.slsa3.yml
 2 files changed, 3 insertions(+), 3 deletions(-)
fatal: tag 'v40.0.62' already exists
To https://github.com/slsa-framework/example-package.git
 ! [rejected]          main -> main (fetch first)
error: failed to push some refs to 'https://github.com/slsa-framework/example-package.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Everything up-to-date
HTTP 4[22](https://github.com/slsa-framework/example-package/actions/runs/5829480876/job/15809071377#step:3:23): Validation Failed (https://api.github.com/repos/slsa-framework/example-package/releases)
Release.tag_name already exists
Error: Process completed with exit code 1.

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.63
Run: https://github.com/slsa-framework/example-package/actions/runs/5852450511
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.63
Date: Mon Aug 14 06:17:04 UTC 2023
Tests are passing now. Closing this issue.


Updated pixi.js to v3

I used compound-concave like dev branch, it's ok?
1. ParticleContainer (former SpriteBatch) can render just one texture, that's why I use just Container.
2. In Render.world we render just bodies, right? What if we have another thing in main container, like a gui or something?
3. Pixi operates with sprites very fast but with graphics — slowly. Why not could we create sprite in canvas?
Sorry, my English is very bad, that's why my message looks... so aggressive, maybe?
Matter is the best JavaScript physics engine that I saw.

Cool, I'll try this out soon.
re. 2: the built in renderer is only a minimal example, for anything more you should create a custom renderer
re 3: do you mean cache vector graphics? I thought about it, but it's kind of out of the scope of the demo renderer, I prefer to keep it simple for now

@liabru yes, cache. I'll make the demo of it on weekends.

I've tried this out, looks good but could you please make the following amends?

fix bug when resizing browser: canvas only scales on x-axis (remove autoResize: true?)
add pixi.js.map (see console error)
change render.bodies to render.spriteContainer (only use bodies to refer to Matter.Body instances)
remove both of your inline comments

Thanks

@liabru done.

This has been merged into master. Thanks for the contribution!


Maintaining an Effective Salesforce Backup

https://help.salesforce.com/s/articleView?id=sfdo.NPSP_Data_Mgmt_BP.htm&type=5
FIRST STEP (Small group at sprint?):

Plan the videos needed (1 for each section? what kind of intro video, if any, etc)
Make cards for each video (see #13 for template, can use this one for the first video.)
Assign them for writing or leave in Looking for Vols column

I am renaming this ticket: The original article has been changed and we had a dupe newer ticket #161 for the new version of the larger article. Looks like they dropped the backup portion altogether and I don't find it in docs on its own. It's a pretty standard SF feature. We can do a video from SF docs
Since the team has already been assigned here, we can work from this ticket. Will delete 161. The team here can create sub-story tickets as they work through it. Thanks @LouiseLockie @GOSHCCAvni @Salesforce-Em! Glad to have such great brains on the case!

Hi @barbarachristensen, I hope you are well. Myself and @LouiseLockie have been through the best practice link and have found that most of the links already have videos linked to them. We don't think that we need to create any additional videos for this. Thanks


fallback to rest of the world for payments if its not excluded

[x] fix tests
[x] test it end to end
[x] drink some tea

With rest of world selected:

Without rest of world selected:

What's the easiest way to add data to test this out?

The interface in Compatibility & Payments looks to work as advertised with the right currencies added.
Deffo worth adding a qa+ on the bug so all the use-cases can get thoroughly tested.
r+wc


crash on unc share access

Description
crash on unc share access
Steps To Reproduce
crash on unc share access
Requirements

e.g. Fix crash that occurs when...
crash on unc share access

Files Version
<IP_ADDRESS>
Windows Version
Win 11 22H2 22621.1848
Log File
debug.log

Thanks for the report.

Can you fill out the steps to reproduce.


Report incorrect link

How does a company or person report an incorrect link being flagged as malicious?

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8112b7a9-8f21-18b3-03da-f8c02b05f239
Version Independent ID: a441f1d1-5844-ecb9-ba44-95b94714e4e8
Content: Complete Safe Links overview for Microsoft Defender for Office 365 - Office 365
Content Source: microsoft-365/security/office-365-security/safe-links.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@rturner2, see:
https://docs.microsoft.com/microsoft-365/security/office-365-security/report-junk-email-messages-to-microsoft

@rturner2 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


What is the implication of breaking changes to stable semantic conventions

As semantic conventions for HTTP are declared stable (and hopefully messaging and databases will follow soon), certain changes outlined in the version and stability document are prohibited.
For metrics, those prohibited changes also include the addition of additional attributes to an existing (stable) metric (see #722 for further discussions). As this drastically limits the extensibility of existing stable metrics, in discussions around messaging and database metrics the question came up whether there should be a defined process for such breaking changes (for example adding additional attributes to an existing stable metric).
The following options might be possible (this is not an exhaustive list):

Forbid any breaking changes.
a. Instead of adding attributes to an existing metric, a new metric with the additional attributes would need to be added.
For applying breaking changes, require a new major version for semantic conventions and consequently for instrumentation libraries implementing them.
For applying breaking changes, require only a new major version for instrumentation libraries instrumenting them.

Especially in regards to databases and messaging system-specific metrics this question is important. There is a goal of providing stable semantic conventions and instrumentation libraries for such systems, however, with those systems and their instrumentation evolving it is doubtful whether relying on a never-changing set of metric attributes is feasible.

Especially in regards to databases and messaging system-specific metrics this question is important. There is a goal of providing stable semantic conventions and instrumentation libraries for such systems, however, with those systems and their instrumentation evolving it is doubtful whether relying on a never-changing set of metric attributes is feasible.

Regarding this question about extending database and messaging system-specific metrics (see also #760), the following two use cases were discussed in the semconv SIG on Feb 26th to illustrate the impact of the different options to telemetry consumers.

For alerts defined on default time series, both options (2) and (3) would be possibly breaking. While such breaking changes could certainly be indicated by a new major version of the agent or instrumentation library used, this in fact might frustrate users as the impact of instrumentation library updates likely will not be clear to them, and in the worst case the breakage will not be obvious, but existing alerts will just stop to fire as they used to.
One possible solution would be to discourage users from defining alerts on default time series, and strongly recommend to define alerts on aggregations of a fixed subsets of attributes.

Option (1) will make it much harder to build generic out-of-the-box APM experiences and dashboards based on generic messaging or database metrics and attributes. This could for example involve RED dashboards for messaging consumer scenarios (with throughput, error rate, and latency), or the error rate and latency of downstream database calls. Both those cases are standard features of existing APM solutions.
As a possible workaround, one could take into account multiple versions of sufficiently similar metrics and aggregate those to achieve the same goal. However, this is quite tedious and in certain ways diminishes the value of semantic conventions as a unified standard.

Every outlined option breaks or impedes one of those two use cases, so we would need to decide which impediments we want to impose on telemetry consumers.

One flavor that could be added to the options (2) and (3) above:

Consider requiring instrumentation libraries to be configurable to double-emit both versions (pre and post breaking change) to provide a transition phase for consumers (like we did with OTEL_SEMCONV_STABILITY_OPT_IN=http/dup).

I believe we've also entertained an option 1.5 when it comes to adding an attribute to a metric which is quite similar to @arminru suggestion above:

we can add an attribute to an existing stable metric as opt-in. Since it requires explicit user action, it is not breaking. The opt-in mechanism can enable/disable a set of features and does not have to be on per-attribute basis.
we can consider accumulating and batching multiple issues like that before doing a major version update/adding metric_v2/etc

Related discussion https://github.com/open-telemetry/semantic-conventions/pull/675#discussion_r1538357461:
The SemVer 2.0 is specific to public API and semconv do not strictly fit into this category.  It's a common practice to do some behavior-breaking changes without major version update. E.g. certain bug fixes or improvements can fit into this category.
Some changes bring significant improvement to user experience, e.g. adding a route/operation name to HTTP client metric and changing the span name accordingly.
By making it opt-in we're effectively keeping the absolute majority of users from leveraging it (because it's hard to discover a flag). Current and future users would have a subpar experience only because of our back-compat concerns.
While decision in each case can vary, we should have a process to allow some lower risk breaking changes without a major version updates. This process should involve weighting pros and cons.


Fix inconsistency in footer links

Closes #5449

@davidfischer
I would like to update this. There are many places where the link is pointed to latest version.
Will update this PR to point them at stable version.

@dojutsu-user please open a new PR, so it's easy to review, I'm merging this one.


Update auto-comment.yml

I updated the issue that is raisen on my code  #854

Please Create new PRs for this because this contain conflict issue.