`match` behaves differently in v2.220.0: `wrong final block length` about fastlane HOT 12 OPEN

I have the same issue as above. If locally somebody is encrypting a profile or a certificate using 2.220, and the CI is decrypting it with 2.219, it will fail. So it's on a file-by-file basis.

This must be mentioned as a breaking change in the release notes at least.

from fastlane.

+1

We have the same problem.

from fastlane.

I sloved the issue.

1. Downgrade fastlane version to 2.219.0
2. Go to the your match git repository and revert the commit created by fastlane 2.22.0
3. Run fastlane and check it is working.

from fastlane.

Same thing happened for us. Pretty sure this isn't intentional, maybe related to #21790?

from fastlane.

We're facing the same issue on another project

from fastlane.

+1

from fastlane.

+1

from fastlane.

This happens for me when I use 220 to write with Match. Rolling back to 219 and regenerating isn't enough, as that has the same issue - I need to roll the signing repo back to a known good state too.

from fastlane.

+1

from fastlane.

+1

from fastlane.

+1

from fastlane.

Just ran into this same issue. Had previously updated a project to 2.220.0 without issue and imported a new match certificate for an AppStore build. But now when I tried to build another project, I got this error. I tried updating to 2.220.0 which got rid of that error, but now it incorrectly selects the wrong certificate! It always choses the AppStore certificate for the first project even if I re-imported the certificate for this project (Adhoc).

I had to roll back the match git repo to before any commits made by 2.220.0 and roll the project back to 2.219.0 for it to work properly again.

Seems match in 2.220.0 is completely broken.

from fastlane.