Uncaught Error: Class 'Google_Auth_AssertionCredentials' not found about flysystem-google-cloud-storage HOT 7 CLOSED

cc @cedricziel

I'm not quite sure of the smoothest way forward here.

I'm suggesting we:

1. Revert https://github.com/Superbalist/flysystem-google-storage/pull/6/files
2. Create a new release fixing existing implementations.
3. Create a new RC release allowing only RC2 to 2.0.0 and changing our code to support to the new credentials handling as per https://github.com/google/google-api-php-client/blob/master/UPGRADING.md#google_auth_assertioncredentials-has-been-removed

from flysystem-google-cloud-storage.

I'd say:

1.) Branch off 1.x, Remove the 2.0 constraint (or to cause less harm pin the last working RC) and release a new patch version as a fix for existing users
2.) on master, use a constraint on the final 2.0 client and tag a new major version

I'm pretty sure that's the way to go :)

from flysystem-google-cloud-storage.

So basically what you're saying, @matthewgoslett :D

from flysystem-google-cloud-storage.

I can't seem to find any RC version which still has the Google_Auth_AssertionCredentials class and old way of defining service credentials.
Can you confirm how you have it working your side, from when you requested the 2.0.0@RC be allowed?

from flysystem-google-cloud-storage.

Fixed in release 1.0.4 - https://github.com/Superbalist/flysystem-google-storage/releases/tag/1.0.4

I'm going to work on a new RC2 our side which uses the updated google/apiclient.
Apologies for the breakage here.

from flysystem-google-cloud-storage.

I've allowed for google/apiclient 2.0.0@RC in https://github.com/Superbalist/flysystem-google-storage/releases/tag/2.0.0-RC1

from flysystem-google-cloud-storage.

Thx Matthew - it's currently a bit out of scope, but I'll get back to testing and improving.

from flysystem-google-cloud-storage.