Thanks for the PR!

See other usages of TARGET_OS_MACCATALYST in the repo for more typical usages of the Catalyst check and to fix the CI failure.

Thanks for your comment @paulb777!

I've found few usages of TARGET_OS_MACCATALYST in the project similar to the following

#if TARGET_OS_MACCATALYST
  // some code here
#elif
  // some code here
#endif

is this what you mean?

Yes

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot I fixed it.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot I consent.

Thanks @gevorgyanvahagn ! The change looks good to me and safe since it only changes code for the Catalyst community-supported distribution.

Assigning to the FirebaseAuth team for review and merge.