Deprecations: 'unarchiveObjectWithData:' is deprecated: first deprecated in iOS 12.0 - Use +unarchivedObjectOfClass:fromData:error: instead

[KevinVladG]

[REQUIRED] Step 1: Describe your environment

• Xcode version: 12
• Firebase SDK version: 6.32.2
• Firebase Component: Database
• Component version: 6.6.0
• Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem

Warning for Deprecations shows up:

/Users/{$CURRENT_USER}/{$PROJECT_FOLDER}/Pods/FirebaseDatabase/FirebaseDatabase/Sources/Persistence/FLevelDBStorageEngine.m:169:50: 'unarchiveObjectWithData:' is deprecated: first deprecated in iOS 12.0 - Use +unarchivedObjectOfClass:fromData:error: instead

Steps to reproduce:

• Updated to Xcode version 12
• Install/Update pods in working project
• Update pods to Swift 5.0 framework
• Applications Builds and Runs on iOS version 14
• Warning for Deprecations shows up for FirebaseDatabase pod

Relevant Code:

• Path to file: /Users/{$CURRENT_USER}/{$PROJECT_FOLDER}/Pods/FirebaseDatabase/FirebaseDatabase/Sources/Persistence/FLevelDBStorageEngine.m

• File name: FLevelDBStorageEngine.m

• Line number of error: 169:50

id pendingPut = [NSKeyedUnarchiver unarchiveObjectWithData:data];

[KevinVladG]

Temp. fix would be to set the "Deprecated Functions" setting in Pods to 'No' this will ignore the error but it's still exists.

[paulb777]

@KevinVladG Thanks for the report. What's the reason for changing the pods build optoins to Swift 5 and how exactly are you doing that? Most of the Firebase pods are written in Objective C and support back to iOS 8 or 9.

We can potentially ifdef the code to address this, but I'm curious to get more context about the use case.

[KevinVladG]

@paulb777 I updated the Firebase pods using Xcode 12 Issues navigator. There was an option for my current project and for the pods and such. that would be great! I just wanted to be sure you guys were aware of it on this new release.

[KevinVladG]

@paulb777 Thank you Paul! I will keep checking for the merge.

[paulb777]

@KevinVladG Sorry, the fix was a bit more complicated than I initially thought and we haven't been able to prioritize yet

[KevinVladG]

@paulb777 no worries I have been following along. I've silenced the warning so no worries!