Use generative-ai-swift tests in Vertex AI

[andrewheard]

• Added an SPM test target and xcscheme named FirebaseVertexAIUnit
• Updated existing tests for Vertex AI
• Removed unused JSON payloads
• Updated CI workflow to run unit tests

#no-changelog

[paulb777]

Thanks!

Feel free to defer any of my comments to future PRs.

[paulb777]

What's preventing them from being added?

[andrewheard]

We'll just need to check those parameters (and requestOptions) when determining if it's the same instance in VertexAIComponent:

firebase-ios-sdk/FirebaseVertexAI/Sources/VertexAIComponent.swift

Lines 65 to 79 in aa474f5

	// MARK: - VertexAIProvider conformance
	func vertexAI(location: String, modelResourceName: String) -> VertexAI {
	os_unfair_lock_lock(&instancesLock)
	// Unlock before the function returns.
	defer { os_unfair_lock_unlock(&instancesLock) }
	if let instance = instances[modelResourceName] {
	return instance
	}
	let newInstance = VertexAI(app: app, location: location, modelResourceName: modelResourceName)
	instances[modelResourceName] = newInstance
	return newInstance
	}

Note: Those parameters are currently all structs so I can't use them with @objc in their current form (might be able to use the [String:Any] trick that Morgan mentioned).

[paulb777]

How can Vertex have an invalid API key? Shouldn't there be a message about a GoogleService-Info.plist?

[andrewheard]

This would only happen if the API key in the GoogleService-Info.plist is invalid (e.g., if the key was revoked after the app was shipped). The message/code/status checked here are the ones returned by the backend. I don't think we have specific error cases for revoked/invalid API keys in our other SDKs (everything would be broken in that scenario), which was why I removed the case that was in https://github.com/google/generative-ai-swift/blob/48a0c2f11935a17132492583d4aad51c5a407bcb/Sources/GoogleAI/GenerateContentError.swift#L32-L33 but we could bring it back.