InvalidApiVersionError: The version of this extension is not the same. Extension version 0.1.7, Api version: 0.1.6.

[Jonas-Sander]

After trying to setup the Extension we get the following error when making a subscription:

InvalidApiVersionError: The version of this extension is not the same. Extension version 0.1.7, Api version: 0.1.6. Please retry the request with the correct version
at Object.exports.validateApiVersion ( [/workspace/lib/validate-api-version.js:7](https://console.cloud.google.com/debug?referrer=fromlog&file=%2Fworkspace%2Flib%2Fvalidate-api-version.js&line=7&project=[project_name]) )
at undefined. ( [/workspace/lib/index.js:78](https://console.cloud.google.com/debug?referrer=fromlog&file=%2Fworkspace%2Flib%2Findex.js&line=78&project=[project_name]) )
at .processTicksAndRejections ( [internal/process/task_queues.js:77](https://console.cloud.google.com/debug?referrer=fromlog&file=internal%2Fprocess%2Ftask_queues.js&line=77&project=[project_name]) )

[vargajacint]

I've updated my perfectly running Firebase extension and got the same error in the RevenueCat Event Details.

{"code":2,"message":"The version of this extension is not the same. Extension version 0.1.7, Api version: 0.1.6. Please retry the request with the correct version","extension_version":"0.1.7"}

[mshmoustafa]

Hello! This error is typically fixed as part of an automatic upgrade process when installing the extension, and generally doesn't indicate there being an issue with your setup. Double check your Firebase integration page in RevenueCat, we may already be sending events successfully. Worst case you may have to reinstall the extension, we've seen reports of this error being fixed by doing that.

[Jonas-Sander]

Hello! This error is typically fixed as part of an automatic upgrade process when installing the extension, and generally doesn't indicate there being an issue with your setup. Double check your Firebase integration page in RevenueCat, we may already be sending events successfully. Worst case you may have to reinstall the extension, we've seen reports of this error being fixed by doing that.

Yes, sorry for not updating the issue, the events are now being sent successfully.
I have to say though that this edge-case could be handled a bit user-friendlier in my opinion. As this is now working, I'm gonna close this issue.

[kajensen]

I've just set up the Firebase extension. I'm getting the same 400 error. @mshmoustafa Are you saying these errors should eventually go away with no action?

[vargajacint]

@kajensen For me it's gone without any further action