Yes, this is a metadata problem at the provider level.
While waiting for a fix at the source, you can apply the workaround solution found here:
Yes, this is a metadata problem at the provider level.
While waiting for a fix at the source, you can apply the workaround solution found here: