waitForCompletionWithTimeout: is deprecated: Use XCTestExpectation instead

[lefdilia]

Step 0: Are you in the right place?

• For issues or feature requests related to the code in this repository file a Github issue.
  • If this is a feature request please use the Feature Request template.
• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general (non-iOS) Firebase discussion, use the firebase-talk google group.
• For backend issues, console issues, and other non-SDK help that does not fall under one of the above categories, reach out to Firebase Support.
• Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

• Xcode version: _____
• Firebase SDK version: _____
• Installation method: CocoaPods | Carthage | Zip file | Swift Package Manager (select one)
• Firebase Component: _____ (Auth, Core, Database, Firestore, Messaging, Storage, etc)

[REQUIRED] Step 2: Describe the problem

Steps to reproduce:

What happened? How can we make the problem occur? This could be a description, log/console output, etc.

If you have a downloadable sample project that reproduces the bug you're reporting, you will likely receive a faster response on your issue.

Relevant Code:

// TODO(you): code here to reproduce the problem

Error on : FIRStorageDownloadTask.m

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

[rizafran]

Hi @lefdilia, please follow the template by including the Xcode and SDK version used, installation method, and steps to reproduce. Thanks.

[paulb777]

@lefdilia This issue is fixed in #8296 and will release in Firebase 8.3.0 that is due out later this week.

It's result of the recent GTMSessionFetcher 1.6.x release.

The warning should be safe to ignore or it could be disabled by downrevving to GTMSessionFetcher 1.5.x