You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently encountering an issue where fastlane match does not seem to be able to update/override existing profiles and certificates when running
We are not sure if this is a regression or a bug we just did not notice so far. We have worked with the GitLab Secure Files API in the past as well and know that before you re-upload a file you will first need to delete it. I did a quick peek into the implementation but could not find a place where a delete would be issued to update the new certs/profiles which might be the root cause.
The issue shows as follows:
[09:56:25]: GitLab storage error: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile, API: https://gitlab.com/api/v4)
[09:56:26]: GitLab storage error: match_version.txt already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: match_version.txt, API: https://gitlab.com/api/v4)
Command executed
bundle exec fastlane match development --readonly false
Complete output when running fastlane, including the stack trace and command used
[09:55:49]: Initializing match for GitLab project xxxx/apple-certificates on https://gitlab.com
[09:56:09]: Verifying that the certificate and profile are still valid on the Dev Portal...
Available session is not valid anymore. Continuing with normal login.
[09:56:14]: Verifying that the certificate and profile are still valid on the Dev Portal...
Available session is not valid anymore. Continuing with normal login.
[09:56:17]: Installing certificate...
+---------------------------------------------------------------------------+
| Installed Certificate |
+-------------------+-------------------------------------------------------+
| User ID | XXXXXXXXXX |
| Common Name | Apple Distribution: YYYYYYYYYYYYYY, Inc. (XXXXXXXXXX) |
| Organisation Unit | XXXXXXXXXX |
| Organisation | YYYYYYYYYYYYYY, Inc. |
| Country | US |
| Start Datetime | 2024-05-09 14:45:22 UTC |
| End Datetime | 2025-05-09 14:45:21 UTC |
+-------------------+-------------------------------------------------------+
[09:56:17]: Installing certificate...
+------------------------------------------------------------------------------------------+
| Installed Certificate |
+-------------------+----------------------------------------------------------------------+
| User ID | XXXXXXXXXX |
| Common Name | 3rd Party Mac Developer Installer: YYYYYYYYYYYYYY, Inc. (XXXXXXXXXX) |
| Organisation Unit | XXXXXXXXXX |
| Organisation | YYYYYYYYYYYYYY, Inc. |
| Country | US |
| Start Datetime | 2024-04-17 07:26:57 UTC |
| End Datetime | 2025-04-17 07:26:56 UTC |
+-------------------+----------------------------------------------------------------------+
[09:56:18]: Provisioning profile '61b9a06c-4776-47a8-9a0b-977a892b270d' is not available on the Developer Portal for the user xxx@yyyyyyyyyyyy.com, fixing this now for you 🔨
[09:56:20]: Starting login with user 'xxx@yyyyyyyyyyyy.com'
Available session is not valid anymore. Continuing with normal login.
[09:56:23]: Successfully logged in
[09:56:23]: Fetching profiles...
[09:56:23]: Verifying certificates...
[09:56:23]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[09:56:24]: Creating new provisioning profile for 'com.xxx.yyyy' with name 'match AppStore com.xxx.yyyy macos' for 'macos' platform
[09:56:25]: Downloading provisioning profile...
[09:56:25]: Successfully downloaded provisioning profile...
[09:56:25]: Installing provisioning profile...
/var/folders/89/nf2tq6c92nz_mlzhl1xsqpk40000gn/T/d20240512-23686-eky4c7/XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile
[09:56:25]: Installing provisioning profile...
[09:56:25]: GitLab storage error: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile, API: https://gitlab.com/api/v4)
[09:56:26]: GitLab storage error: match_version.txt already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: match_version.txt, API: https://gitlab.com/api/v4)
[09:56:26]: Finished uploading files to GitLab Secure Files Storage [xxxx/apple-certificates]
+---------------------------------------------------------------------------------------------------------------------------------------------+
| Installed Provisioning Profile |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+
| Parameter | Environment Variable | Value |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+
| App Identifier | | com.xxx.yyyy |
| Type | | appstore |
| Platform | | macos |
| Profile UUID | sigh_com.xxx.yyyy_appstore_macos | 12312312-xxxx-4418-ae24-498fb9c95e5a |
| Profile Name | sigh_com.xxx.yyyy_appstore_macos_profile-n | match AppStore com.xxx.yyyy macos |
| | ame | |
| Profile Path | sigh_com.xxx.yyyy_appstore_macos_profile-p | /Users/mschmieder/Library/MobileDevice/Provisioning |
| | ath | Profiles/12312312-xxxx-4418-ae24-498fb9c95e5a.provisionp |
| | | rofile |
| Development Team ID | sigh_com.xxx.yyyy_appstore_macos_team-id | XXXXXXXXXX |
| Certificate Name | sigh_com.xxx.yyyy_appstore_macos_certifica | Apple Distribution: XXX, Inc. (TNRXXXXX) |
| | te-name | |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+
Environment
[09:57:43]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Same issue here with the latest stable version of fastlane at the time of writing: 2.220.0
Temporary solution, if you know what files will be updated, is to manually delete them from the repo's Secure Files, but it's definitely not an optimal long term fix.
Fortunately we don't have to update provisioning profiles often, but nevertheless I think this is a serious problem.
New Issue Checklist
Issue Description
We are currently encountering an issue where fastlane
match
does not seem to be able to update/override existing profiles and certificates when runningWe are not sure if this is a regression or a bug we just did not notice so far. We have worked with the GitLab Secure Files API in the past as well and know that before you re-upload a file you will first need to delete it. I did a quick peek into the implementation but could not find a place where a delete would be issued to update the new certs/profiles which might be the root cause.
The issue shows as follows:
Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: