[match] cannot create new provisioning profiles for Mac/Catalyst since 2.218.0 about fastlane HOT 9 OPEN

@greatcat19 What command are you running?

@nekrich an idea?

from fastlane.

something like

$ bundle e fastlane match development --platform catalyst

My lane:

def perform_match(type)
  platform = lane_context[:PLATFORM_NAME]
  # https://docs.fastlane.tools/actions/match/#match
  match_platform = platform == :ios ? 'ios' : 'catalyst'
  match(
    type: type,
    team_id: TEAM_ID,
    api_key_path: ASC_KEY_PATH, # comment me out when readonly is false
    app_identifier: MAIN_IDENTIFIERS,
    platform: match_platform,
    additional_cert_types: type == 'developer_id' ? 'developer_id_installer' : nil,
  )
end

desc 'This lane downloads and configures the code signing certificates and profiles.'
lane :configure_code_signing do |options|
  perform_match('appstore') if options[:appstore] == true
  perform_match('development') if options[:development] == true
end

from fastlane.

Could you run VERBOSE=true bundle e fastlane match development --platform catalystand also put more of your output so we see where it fails? Thanks.

from fastlane.

Running into the same problem right now.

[19:37:59]: Creating new provisioning profile for 'redacted' with name 'match Development redacted catalyst' for 'catalyst' platform
INFO  [19:38:00]: >> POST profiles: {"data":{"attributes":{"name":"match Development redacted catalyst","profileType":"MAC_CATALYST_APP_DEVELOPMENT","templateName":null,"teamId":"redacted"},"type":"profiles","relationships":{"bundleId":{"data":{"type":"bundleIds","id":"redacted"}},"certificates":{"data":[{"type":"certificates","id":"redacted"}]},"devices":{"data":[]}}}} 
DEBUG [19:38:00]: << POST profiles: 409 {
  "errors" : [ {
    "id" : "redacted",
    "status" : "409",
    "code" : "ENTITY_ERROR",
    "title" : "There is a problem with the request entity",
    "resultCode" : 35,
    "detail" : "There are no current MAC_OS devices on this team matching the provided device IDs."
  } ]
}

This seems to be the relevant part.

from fastlane.

@Schlabbi can you confirm that the devices array is indeed empty in the POST request body?

Can you try with fastlane 2.217 and see if the request has the same content? Thanks

from fastlane.

I am getting the same issue for iOS adhoc profiles with fastlane 2.216 when I don't have devices registered in my portal. Maybe the issue is that development profiles cannot be created without having device in the portal? I haven't tried doing it by hand.

from fastlane.

@Schlabbi can you confirm that the devices array is indeed empty in the POST request body?

Can you try with fastlane 2.217 and see if the request has the same content? Thanks

It works with 2.217. And yes, the devices array is indeed empty in the POST request. On 2.217 the array is not empty and it seems to work just fine.

from fastlane.

I suspect it is due to the integration of the Cache. @nekrich an idea?

@Schlabbi you can confirm if the cache is indeed the culprit by testing fastlane at the following commits

4eb636f before the cache
a3715d6 after

another thing that could be helpful would be to run your both 2.217 and 2.218 in verbose mode. and compare the queries. In particular I am interested in this code:

https://github.com/fastlane/fastlane/pull/21694/files#diff-a3f19787d89fdd5a42fc5c085d1273811c4ca0dc6f25623eb5907dcfdf43ba2fR113-R136

It should trigger a query of the existing devices, but then it filters them out. I wonder if that's what is causing the array to be empty afterwards.

from fastlane.

Ran into the same issue on 2.219, downgrading to 2.217 helped.

from fastlane.